...
The following shows an example of the XML file content for a node-locked license with a single feature (sample file nodelocked.xml). Note that the CONFIGFILE and OUTPUTFILE settings can be specified either within the file or at the command line (see Generating licenses).
| Code Block | ||
|---|---|---|
| ||
<LICENSEFILE CONFIGFILE="myprogram.lmx" OUTPUTFILE="nodelocked.lic"> |
...
<FEATURE NAME="f1"> |
...
<SETTING MAJOR_VERSION="1"/> |
...
<SETTING MINOR_VERSION="5"/> |
...
<!-- Note that settings below optional and can be enabled or disabled e.g. for unlimited or demo licenses --> |
...
<SETTING END="2008-01-01"/> |
...
<CLIENT_HOSTID> |
...
<SETTING ETHERNET="C8A516AD01AFC9FA"/> |
...
</CLIENT_HOSTID> |
...
</FEATURE> |
...
</LICENSEFILE> |
Floating network license example
The following shows an example of the XML file content for a floating license with a single feature (sample file floating.xml).
| Code Block | ||
|---|---|---|
| ||
<LICENSEFILE CONFIGFILE="myprogram.lmx" OUTPUTFILE="floating.lic"> |
...
<FEATURE NAME="f1"> |
...
<SETTING END="2008-01-01"/> |
...
<SETTING COUNT="5"/> |
...
<SERVER_HOSTID> |
...
<SETTING ETHERNET="C8A516AD01AFC9FA"/> |
...
</SERVER_HOSTID> |
...
</FEATURE> |
...
</LICENSEFILE> |
Note that:
- The COUNT setting is included, which identifies this as a floating license.
- The CONFIGFILE and OUTPUTFILE settings can be specified either within the file or at the command line (see Generating licenses).
- The feature's version number is not specified, so it will default to 1.0.
...
The following shows an example of the XML file content for a floating license with multiple features, plus many of the optional settings such as license sharing, borrowing, etc. (sample file detailed.xml).
| Code Block | ||
|---|---|---|
| ||
<LICENSEFILE CONFIGFILE="myprogram.lmx" OUTPUTFILE="detailed.lic"> |
...
<!-- You can put comments into the header of the license if needed --> |
...
<LICENSEFILE COMMENT="This license was created by the xml based license generator."/> |
...
<LICENSEFILE COMMENT="You could use this space to explain the type of license you are providing."/> |
...
<FEATURE NAME= "f2"> |
...
<SETTING START="2004-12-24"/> |
...
<SETTING END="2012-12-25"/> |
...
<SETTING MAJOR_VERSION="1"/> |
...
<SETTING MINOR_VERSION="3"/> |
...
<SETTING LICENSEE="our_user"/> |
...
<SETTING COMMENT="Our_product_setting_values"/> |
...
<SETTING KEYCOMMENT="hidden text retrieved from API"/> |
...
<SETTING SHARE="TERMINALSERVER"/> |
...
<CLIENT_HOSTID> |
...
<SETTING ETHERNET="C8A516AD01AFC9FA"/> |
...
</CLIENT_HOSTID> |
...
<CLIENT_HOSTID> |
...
<SETTING CUSTOM="C8A516AD01AFC9FB"/> |
...
</CLIENT_HOSTID> |
...
</FEATURE> |
...
<FEATURE NAME= "f1"> |
...
<SETTING END="2016-01-01"/> |
...
<SETTING MAJOR_VERSION="1"/> |
...
<SETTING MINOR_VERSION="5"/> |
...
<SETTING LICENSEE="Our_valued_customer"/> |
...
<SETTING COUNT="10"/> |
...
<SETTING SHARE="HOST"/> |
...
<SETTING SHARE="USER"/> |
...
<SETTING BORROW="100"/> |
...
<SERVER_HOSTID> |
...
<SETTING ETHERNET="C8A516AD01AFC9FA"/> |
...
<SETTING CUSTOM="C8A516AD01AFC9FB"/> |
...
</SERVER_HOSTID> |
...
</FEATURE> |
...
</LICENSEFILE> |
Note that the CONFIGFILE and OUTPUTFILE settings can be specified either within the file or at the command line (see Generating licenses).