Find the scenario(s) you are most interested in below, and use the example to help you create your own XML license template.

Trial license XML template scenario

For this trial license scenario, let's assume you want your application to be:

• An evaluation for selected features that will work for a specified number of days or specified number of uses, whichever occurs first.
• Widely available, with no need for a license. (Trials do not require a license file and can be enabled by default when there is no license file found.)
• Easily converted to a licensed version by delivering a license file to the user.
• Prevented from being used after the trial period expires (user is able to evaluate only once, and must then purchase a license to continue running the product).
• Available for re-evaluation when a new version of the software is released.
• Forbidden to run on virtual machines (by default).
• Protected against clock tampering (by default).

No XML license template is needed for trial licenses. You need only specify the length of the trial, as described in Example license scenarios.

Node-locked license XML template scenario

For this node-locked license scenario, let's assume you want your application to be:

• Subscription-based, paid annually.
• Locked to a particular machine (that is, a specific hostid).
• Forbidden to run on virtual machines (by default).
• Protected against clock tampering (by default).

<LICENSEFILE>
<FEATURE NAME="MyFeatureName"> 
<SETTING MAJOR_VERSION="1"/>
<SETTING MINOR_VERSION="0"/>
<!-- Applies to version 1.0 --> <SETTING END="2012-02-01"/>
<!-- We assume the license will be issued on February 1, 2011. The application will expire on February 1, 2012. This is a fixed date, because we assume the subscription starts on the day payment is received. -->
<CLIENT_HOSTID> <SETTING ETHERNET="0018DEBC98A8"/>
</CLIENT_HOSTID>
<!-- The HOSTID setting locks the license to a particular machine. For information about obtaining the HostID code from the end user, see "See "Step 5: Distribute your LM-X licensed software to end users" on page ." For now, you can get the HostID value for your computer using lmxconfigtool.exe or lmxendutil. -->
</FEATURE>
</LICENSEFILE>

Floating license XML template scenario

For this floating license scenario, let's assume you want your application (or particular application features) to be:

• Protected with floating licenses. With this type of license, application usage is authorized for end users on a network. The number of concurrent users is counted, with the licensed application use limited to only a specified number of users at any time.
• Subscription-based, paid annually.
• Forbidden to run on virtual machines (by default).
• Protected against clock tampering (by default).

<LICENSEFILE>
<FEATURE NAME="MyFeatureName">
<!-- In this simple example, your application consists of only one feature -->
<SETTING MAJOR_VERSION="1"/>
<SETTING MINOR_VERSION="0"/>
<!-- Applies to version 1.0 --> <SETTING COUNT="5"/>
<!-- The COUNT setting is essential. It defines the number of concurrent licenses available to the end user. -->
<SETTING END="2012-02-01"/>
<!-- We assume the license will be issued on February 1, 2011. The application will expire on February 1, 2012. This is a fixed date, because we assume the subscription starts on the day payment is received. -->
<SERVER_HOSTID> <SETTING ETHERNET="0018DEBC98A8"/>
</SERVER_HOSTID>
<!-- The HOSTID setting locks the license to a particular machine. For information about obtaining the HostID code from the end user, see "See "Step 5: Distribute your LM-X licensed software to end users" on page ." For now, you can get the HostID value for your computer using lmxconfigtool.exe. -->
</FEATURE> </LICENSEFILE>