...
The following tables show the most common feature settings for node locked and floating licenses, whether they are required or optional, and whether they are set by default.
Settings for both node-locked and floating licenses
Setting | Required for node-locked | Required for floating | Usage | Set by default |
Yes | Yes | License key set by the license generator, which should not be modified. | Yes | |
Yes | Yes | Your assigned vendor ID, which should not be modified. | Yes | |
Yes | Yes | The major version number of the feature. | Yes (Defaults to 1) | |
Yes | Yes | The minor version number of the feature. | Yes (Defaults to 0) | |
No | No | Specifies the license expiration date. | No | |
No | No | Specifies the customer name to which the license has been issued. | Yes | |
No | No | Enables/disables the system clock check performed by client application and license server. | Yes | |
No | No | Locks the license to a specific machine. | No | |
No | No | Specifies the percentage of HostIDs that must match for successful HostID verification. | Yes (Defaults to 100%) |
Using or changing one more of the above settings can change a licensing model. For instance:
To use this licensing model: | Modify the license file settings to: |
---|---|
Feature-limited demo license | Contain only the features you want to license. |
Temporary license | Set END to the date on which you want the temporary license to end. |
Permanent license | Do not set END. |
Time-limited | Set END to a specific date. |
Annual subscription | Set END to the current date + one year. |
Copy protection license | Use CLIENT_HOSTID. |
Shared license | Use SHARED=USER|HOST|CUSTOM. |
Settings for floating licenses only
Setting | Required | Usage | Set by Default |
See "KEYTYPE" on page (see See "KEYTYPE" on page ) | Yes | Specifies whether a network license is exclusive, additive or token-based. | Yes (Defaults to exclusive) |
See "COUNT" on page (see See "COUNT" on page ) | Yes | Specifies the number of licenses that can be issued simultaneously for the particular feature floating on the network. | No |
SERVER_HOSTID (see See "Locking" on page ) | No (highly recommended) | Locks the license to a license server machine. | No |
See "BORROW" on page (see See "BORROW" on page ) | No | Enables leasing of licenses to computers that can be disconnected from the network. | Yes |
See "GRACE" on page (see See "GRACE" on page ) | No | Enables leasing of licenses to computers that are disconnected from the network unexpectedly. | Yes |
...
License option | Node-locked | Floating | Usage | Default behavior |
See "Trial licenses" on page (see See "Trial licenses" on page ) | Yes | Yes | Lets end users use an application for a predetermined length of time without requiring a license. | Disabled by default. When enabled, trial licenses are not allowed on virtual machines or terminal servers by default. |
See "Licensing for virtual machines and cloud computing" on page (see See "Licensing for virtual machines and cloud computing" on page ) | Yes | Yes | Lets you explicitly allow trusted and enterprise customers to use your application in a virtual environment. | By default, LM-X denies all checkouts for local licenses in virtual environments, such as VMware or Virtual Server, and refuses to load licenses on license servers to prevent potential license overuse. |
See "Automatic server discovery" on page (see See "Automatic server discovery" on page ) | No | Yes | Allows a client application to find license servers on the network automatically. | By default, automatic server discovery is disabled on the client side. |
...