A project template can contain any number of modules / features.
To be compatible with the windows version of Licence Protector, the template is identical with the windows version license file template although a lot of options are not required for the MAC version.
You find the template which is used in the trial version on the folder ....template/Activation Server/ALG - demo-easygo-mac.xml
After you have done the testing just make, a copy of the demo-easygo-mac.xm file and modify the following settings marked in green. If you do not need a module, delete it or add new modules in case you need more.
<?xml version="1.0" encoding="utf-8"?>
<LicenceProtector>
<Default>
<OSVersion>1</OSVersion> <ProjectSecureKey>r1lkYAp1xGQN81fBrcZ1dfXtw1doy3Z1l4KHy0N2yvL0ZBDcX274DHV1BfV7s0RFpjZ1NOmMf1qXGsu1MqTXK1t4Tsq1c7jQq1iP3VM1NNx6j1s64YK299TY71YSrbK0NdSom29inxM29bPTJ1mmLNV0SNdC41xCbdT2adSqt2aazQL1dslWy1fGXFi11YWOv1fFhLt2acufE1hRGXY1VxH0R0ViybX0XmcNz1lm76W1gQqQe21grLU1VAc401UqH8l0YHwOD1S46cC20hVpD1cfAYk299ixt</ProjectSecureKey>
<ProjectName>demo-easygo-mac</ProjectName>
<CustomerName>Evaluation Version</CustomerName>
<AppVersion>2014</AppVersion>
<MainModuleID>QHD001</MainModuleID>
</Default>
<LicenceModules>
<Module>
<ModuleID>QHD001</ModuleID>
<ModuleName>E-Learning Made Easy</ModuleName>
<ModuleType>YesNo</ModuleType>
<WebActivation>none</WebActivation>
<Value>Yes</Value>
<Days>30</Days>
<ValidUntilDay />
<Demoversion>true</Demoversion>
<IsSerial>yes</IsSerial>
<ModuleVerification>on</ModuleVerification>
<SubGraceDays>10</SubGraceDays>
</Module>
<Module>
<ModuleID>QHD002</ModuleID>
<ModuleName>Additional Module 2</ModuleName>
<ModuleType>YesNo</ModuleType>
<WebActivation>none</WebActivation>
<Value>Yes</Value>
<Days></Days>
<ValidUntilDay>1900-01-01</ValidUntilDay> This module does not have a trial version
<Demoversion>false</Demoversion>
<IsSerial>yes</IsSerial>
</Module>
<Module>
<ModuleID>QHD003</ModuleID>
<ModuleName>Additional Module 3</ModuleName>
<ModuleType>YesNo</ModuleType>
<WebActivation>none</WebActivation>
<Value>Yes</Value>
<Days>30</Days>
<ValidUntilDay>2013-01-01</ValidUntilDay> This module will either expire after 30 days or on January, first 2014 depending which event happens first
<Demoversion>false</Demoversion>
<IsSerial>yes</IsSerial>
</Module>
<Module>
<ModuleID>QHD004</ModuleID>
<ModuleName>Additional Module 4</ModuleName>
<ModuleType>YesNo</ModuleType>
<WebActivation>none</WebActivation>
<Value>Yes</Value>
<Days>30</Days>
<ValidUntilDay />
<Demoversion>true</Demoversion>
<IsSerial>yes</IsSerial>
</Module>
<Module>
<ModuleID>QHD005</ModuleID>
<ModuleName>Additional Module 5</ModuleName>
<ModuleType>YesNo</ModuleType>
<WebActivation>none</WebActivation>
<Value>Yes</Value>
<Days>30</Days>
<ValidUntilDay />
<Demoversion>true</Demoversion>
<IsSerial>yes</IsSerial>
</Module>
</LicenceModules>
<Configs>
<Config name="Data-1" visible="yes">You can store any data here</Config>
</Configs>
</LicenceProtector>
A key which is used to encrypt the file. The key should have at least 50 characters and numbers. The ProjectSecureKey is used in the prepareInit command.
Short name of your application. It should contain no spaces and is case sensitive
For each module / function you want to license you change
The ModuleID is the reference in the API call to address a module. It must be unique per project. The format of the ModuleID is up to 6 characters containing only capital letters A-Z and digits 0 to 9.
Do not use a ModuleID with value 000000
See also Main Module
Full text - Name of the module
• | Number of days for the trial version. The days count starts when the command validate is used. Each module can have a different number of days for the trial version. |
• | If days is set to 0, then the product is a freeware version |
• | If you set a date in the future, the trial version would expire at this date. |
• | If there should be no trial version (serial number needed to start the application) use: 1900-01-01 |
If Days AND ValidUntilDay is specified, the event, which happens first, is used
Example
Days = 30
ValidUntilDay = 2013-10-01
The user starts the trial on 20th July, 2013 - the trial expires 30 days later
The user starts the trial on September, 29th 2013 - the trial will expire on October, 1st 2013
True / False
If set to false, the evaluation version is a full version.
If set to true, the evaluation version has limitations (e.g. no print, no save, nag screen). The validate command gives return code 1.
Version number of the application as text information - e.g. 3.1 or 2014. This
The version number can be changed with setAppVersion and retrieved with getAppVersion. This information is sent to the Activation Server 4 and can be viewed per transaction.
Default values for the data area are stored in the <Configs> section.