Page tree
Skip to end of metadata
Go to start of metadata

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.
  • 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 (the 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, and you only need to specify the length of the trial.

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).

In the following example we assume the license will expire on January 1, 2018. This type of license may require that the user's HostID(s) be defined as shown below.

<LICENSEFILE>
	<FEATURE NAME="MyFeatureName"> 
		<SETTING MAJOR_VERSION="1"/>
		<SETTING MINOR_VERSION="0"/>
		<SETTING END="2018-01-01"/>
		<CLIENT_HOSTID>
			<SETTING IPADDRESS="123.123.123.123"/>
			<SETTING USERNAME="john"/>
		</CLIENT_HOSTID>
	</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:

  • Used only by authorized end users on a network. The number of concurrent users is counted.
  • Subscription-based, paid annually.
  • Forbidden to run on virtual machines (by default).
  • Protected against clock tampering (by default).

In the following example we assume the license will expire on January 1, 2018. This type of license limits the number of concurrent users of the license to five.

<LICENSEFILE>
	<FEATURE NAME="MyFeatureName">
		<SETTING MAJOR_VERSION="1"/>
		<SETTING MINOR_VERSION="0"/>
		<SETTING COUNT="5"/>
		<SETTING END="2018-01-01"/>
	</FEATURE> 
</LICENSEFILE>