Server Licensing

The Server licensing model has three different scenarios. Once you have added the licensing calls to your application, as explained in the next section, you need to follow additional steps. Depending on the licensing scenario you choose, refer to one of the following sections for further information:

The Server Licensing Utility (SLU) Process
The SLU process is ideal for limited licensing (for example, an internally deployed server application). Less coding is required up-front, but there is manual intervention required.
The Automatic Scenario
The Automatic process requires that your end users have an Internet connection. The process is automatic, which means that there is less intervention, but also less control.
The Manual Scenario
The Manual process is more complex, but allows you to have more control over licensing.

The manual and automatic scenarios achieve the same end result, and can be mixed among your end users, since the License Key is generated by the same Deployment Licensing Service for either scenario. The automatic scenario is the recommended method, but if an Internet connection is not available, then the manual scenario can be used.

Errors can occur during licensing with either scenario, e.g: Internet connection problems (in automatic mode), registry permission problems, invalid access keys, etc. To guarantee that your application runs after installation, the Licensing Component automatically activates the grace period when any error occurs during licensing. The default grace period is 14 days, but this can be customized for each deployment pool by request to Accusoft. The licensing process can be repeated during the grace period, and once the application is licensed successfully, the grace period is cleared.

With either scenario, your application only needs to be licensed once, after which it will work indefinitely. In the event that your end user recovers from a backup onto different hardware, the license needs to be transferred as described in the below and then bound to the new hardware.

Accusoft provides the Licensing Component, which facilitates the licensing process on the end user's system for the Server model.

The Server License model provides the following benefits:

You can integrate the Vendor Licensing Utility functionality into your own system (e.g., order processing system).
You can set up the Deployment Proxy Service on your site and program the Licensing Component to communicate with the Deployment Proxy Service instead of the Deployment Licensing Service.
You can set up custom End User licensing scenarios. For example, directing end users to come to a Web application hosted on your Web site to get a License Key.

The following tools and utilities are provided by Accusoft to prepare your application for deployment:

The Vendor Licensing Utility
A License Deployment Kit (LDK) that includes:
- Licensing Component
- Sample VB-script (see Licensing Component Wrapper)
- Sample MSI-package (see Licensing Component Wrapper)
- Deployment Proxy Service
- Deployment Packaging Wizard (see Deploying Your Product)
A Configuration file to be used with the Licensing Component

Code Samples for Server Model

VB:

	Copy Code
'Licensing Functions Definitions Declare Function IG_lic_solution_name_set Lib "igcore15d.dll" (ByVal SolutionName As String) As Long Declare Function IG_lic_solution_key_set Lib "igcore15d.dll" (ByVal Key1 As Long, ByVal key2 As Long, ByVal key3 As Long, ByVal key4 As Long) As Long Dim IGErr As Long IGErr = IG_lic_solution_name_set("AccuSoft 1-100-17") IGErr = IG_lic_solution_key_set(&H473F47EC, &HDEDCEDC4, &HAFFBB23E, &HFBFBDE4A)

Copy Code

'Licensing Functions Definitions
Declare Function IG_lic_solution_name_set Lib "igcore15d.dll" (ByVal SolutionName As
String) As Long
Declare Function IG_lic_solution_key_set Lib "igcore15d.dll" (ByVal Key1 As Long,
ByVal key2 As Long, ByVal key3 As Long, ByVal key4 As Long) As Long
Dim IGErr As Long
IGErr = IG_lic_solution_name_set("AccuSoft 1-100-17")
IGErr = IG_lic_solution_key_set(&H473F47EC, &HDEDCEDC4, &HAFFBB23E, &HFBFBDE4A)

C#:

The names of the ImageGear functions may change depending on how you wrap the DLL for use in C#. For an example on wrapping the ImageGear Libraries, please refer to the DLL "C#.net Demo" program and source.

	Copy Code
ASCIIEncoding encoding = new ASCIIEncoding(); byte[] SolutionName = encoding.GetBytes("AccuSoft 1-100-17"); fixed (byte* pszBuffer = SolutionName) { IGLib.IG_lic_solution_name_set( pszBuffer ); } IGLib.IG_lic_solution_key_set (0x473F47EC, 0xDEDCEDC4, 0xAFFBB23E, 0xFBFBDE4A);

Copy Code

ASCIIEncoding encoding = new ASCIIEncoding();
byte[] SolutionName = encoding.GetBytes("AccuSoft 1-100-17");
fixed (byte* pszBuffer = SolutionName)
{
        IGLib.IG_lic_solution_name_set( pszBuffer );
}
IGLib.IG_lic_solution_key_set (0x473F47EC, 0xDEDCEDC4, 0xAFFBB23E, 0xFBFBDE4A);

C++:

	Copy Code
IG_lic_solution_name_set( "AccuSoft 1-100-17" ); IG_lic_solution_key_set(0x473F47EC, 0xDEDCEDC4, 0xAFFBB23E, 0xFBFBDE4A );

ImageGear Professional DLL v17.1 for Windows
Server Licensing
Send Feedback

Code Samples for Server Model

VB:

C#:

C++:

See Also: