|
||
To deliver a license file via download, the following steps are necessary:
•Create a license file with the License Generator and upload this file to the Activation Server
•User gets a Serial Number which he can use to download his license
•The product activation downloads the license file
•When additional modules or licenses are bought, the license is manually updated on the Activation Server
•User downloads updated license information
Load your project and configure all the license options the customer ordered. You can either create the license file with the License Generator or just copy an existing license file on the Activation Server.
Create a default license file, upload it with the Generator and then always copy this default license file on the Activation Server.
Fill in the customer details. The following settings are important.
•Type in the customer name •Copy Protection = none •Set all modules to the values the customer has bought •Define time limitations only if the full version should expire after x days or if a module should expire at a specific date (example below - update subscription) •For the main module set Status of Activation to done
Save the license file on a temporary folder (this step is mandatory).
•Create a Serial Number. You could alternatively use any ID which must just be a unique ID like order number or customer number (see use own IDs for product activation) . A Serial Number ensures, that the ID is unique. The users gets this ID to identify his license on the server
Select the TAB Activation Server and click on the Upload Server option.
This opens a new window, where you can fill out additional license file details.
•The field Encryption Code is like a password. It ensure that nobody else with knowledge of your Activation Server structure can download a file. We strongly recommend using it •File description is the name of the license file on the Activation Server. If this file description is empty, the name is default. •You have to use the module ID of the main module •Use the Serial Number or ID to identify the license •The Send Customer Info option creates a record in the address table and assigns the address to this license
|
To copy an existing license file, select a license file from another customer or your default file and then click on the option: Copy License File
You then specify the Serial Number / ID, which will be used to download the license file.
|
Use the EasyGo commands (function reference EasyGo). You must use SetRegisterLictransfer with the following options:
•TransferLicence = true - this option activates the license file download
•File Description must have the same value like used in the screen to upload the license file
•Encryption Code must have the same value like used in the screen to upload the license file
The activation option should be restricted to online - SetRegisterSettings
•As the license file is modified after the download (e.g. copy protection is turned on), a good idea is to upload it. The command GetActionsOfLastPrepareAndCheck provides the 'event', when the activation was done. Use UploadLic to upload the file
If a Serial Number / ID is used, which was not previously uploaded to the Activation Server and assigned to a license file, the default (=demo license) file is activated but all the customer specific modules would not be available
If the user buys additional modules or more network licenses, you change the license information on the Activation Server.
•Select TAB, Manage Activations and then Key List •Click on the ID you uploaded
You get a new window
Now select your license file and edit the values. |
Provide a menu option: Update my license
Use the following code sequence:
•Read the Serial Number using GetSerial
•Now update the license information using DownloadLic
This will download the latest license file information from the Activation Server
You can also offer an option to upload the license file using UploadLic.
The following values in the project.config file on the Activation Server are important for the license file upload:
•LvsDefaultName
•LvsOverwriteServerChanges
•MultipleLVS