A typical workflow would be:

 

 

•After your product is installed, you open the license file using prepare

•If there is no license file on the local hard disk, the initial license file with the default values for an evaluation version is downloaded from the Activation Server 4. The first program start  requires a mandatory online connection

•The license file stores all values and activities regarding the license in an encrypted format

•During the evaluation period, you retrieve the number of seconds when the version will expire or the final expiry date

•Use validate to validate the module. If the trial version expired (error code = 16 or 17) then proceed with the product activation screen

•Check the demo version state using getDemoState

 

Product Activation

•When a user buys the product, he gets a Serial Number Key. You can either use own Serial Number Keys or let the Activation Server 4 create a Serial Number Key list. The Serial Number Key must be stored in the Activation Server 4 before it can be used

•The user types in the Serial Number Key, his name / company name and e-mail address (your application has to provide this screen)

•The Serial Number Key, name / company name and e-mail address is sent to the Activation Server 4 including the System ID of the MAC computer. The command activateModule sends the information to the Activation Server 4, the Activation Server 4 checks how often the Serial Number Key was used and if it is a valid Serial Number Key and sends back a status code. The test is done per module - e.g. if an application has 3 modules each module needs to be activated with a Serial Number Key

•The license file is linked to the system ID of the MAC. If this license file would be used on an other computer it would result in a copy protection error