Automatically Reported Runtime licenses use a mechanism similar to Toolkit licensing to activate a license for a particular system. In this case, each installation has a unique license that is pulled from the pool of licenses purchased by the customer. When the license key is generated, it contains hardware information that identifies the system on which the license is to be installed. 

The Licensing Development Kit (LDK) component, which interacts with the licensing web service and installs the newly generated license key, may be used directly by the application or it may be used through a simple tool known as the Server Licensing Utility (SLU). 

• The LDK requires integration with the application or installation utility to perform license activation. 
• The SLU is a stand-alone application that integrates the Licensing Development Kit to perform the registration.

License Pools

When Automatically Reported Runtime licenses are purchased, they are organized into pools of a specific version and platform for a particular toolkit.  For example, if a customer developed two applications using Barcode Xpress, one using 32-bit ActiveX and the other using .NET, they would purchase two pools of Runtime licenses, one for the ActiveX platform and one for the .NET platform.

At installation, a new license would be pulled from the appropriate pool, depending upon which platform the application is using.

License Configuration Files

When an Automatically Reported Runtime license is purchased, a License Configuration file is created and distributed to the customer along with their assigned Solution Name and Solution Key.

The License Configuration file contains information about the Runtime licenses for a particular platform and version of a toolkit. It is used by the Server Licensing Utility or License Development Kit to activate licenses when the customer’s application is installed on their users' systems.

Licensing API

The Licensing API is used in the developer’s code to specify Runtime Licensing deployment information. This is used to unlock the Accusoft products and enable all licensed features at runtime. Both the "Solution Name" and "Solution Key" values used in the API described below are provided by Accusoft, along with the License Configuration file, at the time of purchase of a Runtime license.

Solution Name

The Solution Name is the name assigned by Accusoft to the licenses purchased for runtime deployment. It is a character string that is set for a component prior to use in a deployment environment and is typically the name of the organization that purchased the Runtime licenses. It is set via the SetSolutionName method. For example:

BarcodeXpress1.SetSolutionName("ACMEImaging");

The Solution Name must be set in order to use runtime licensing.

Solution Key

The Solution Key is a set of four numbers assigned when the licenses are purchased for runtime deployment; the Solution Key also identifies the organization that purchased the Runtime licenses. The Solution Key is set via the SetSolutionKey method. For example: 

BarcodeXpress1.SetSolutionName("ACMEImaging");
BarcodeXpress1.SetSolutionKey(0x1C3A023F, 0xA018F260, 0x37AF0E51, 0x557F2389);

The Solution Key must be set in order to use runtime licensing. 

SLU vs. LDK

Both the SLU and the LDK perform the same function of registering the Runtime license for the system on which it will be run. The SLU is a user interface for the LDK. Both are provided in order to give you some options.

• The use of an Accusoft branded SLU may meet your needs if you are deploying to your own systems (e.g., for enterprise IT staff) or if you handle the deployment onto end users systems. 
• Choose the LDK if you wish to hide this licensing registration from your end users. The LDK allows you to integrate the registration process into your application. It also allows for the optional assignment of Access Keys to specific users, which lets you manage your licenses more directly and limits the distribution of licenses.