...
- The upgrade license's expiration dates must be within the exclusive license's expiration dates.
- Neither the upgrade nor exclusive license can beunlimited.
- ClientHostIDs are not supported for upgrade licenses, andLMX_GetLicenseInfo will not report upgrade licenses in network or local paths. These limitations exist because the upgrade licenses are designed to be transparent to the client. However, exclusive licenses report their upgraded license count in bothLMX_GetFeatureInfo and LMX_GetLicenseInfo.
License template
To maintain maximum compatibility with the corresponding exclusive license, the settings allowed in the upgrade license template are limited. All of the settings behave the same as for exclusive licenses, except thatcreate an upgrade license, create a feature with the same feature name as the original license, set the number of licenses using the COUNT directive, and set KEYTYPE="UPGRADE" in the XML license template file.
SHARE is limited toVIRTUAL only.Some settings, likeIn addition to the feature name, COUNT and KEYTYPE, settings that are required by the license generator to create an upgrade license. Optional , the optional settings that may be used with upgrade licenses are START, END, SHARE, HOSTID_MATCH_RATE, HAL_SERVERS and server HostIDs.
To maintain maximum compatibility with the corresponding exclusive license, the settings allowed in the upgrade license template are limited. All of the settings behave the same as for exclusive licenses, except thatSHARE is limited toVIRTUAL only.
Example
The following license template would result in an upgrade license that increases the feature "f1" license count by one, and is valid from the license server startup to 2030-01-01.
...