The upgrade license type, which applies only to network licenses, resolves issues associated with and is intended to replace additive licenses. Rather than creating a new license pool alongside an exclusive license as additive licenses do, upgrade licenses increase the exclusive license count Upgrade licenses let you add licenses for software features that a customer buys after the initial purchase of a license, without changing the original license. Upgrade licenses increase the license count of exclusive licenses by a particular number of licenses, while simultaneously being completely transparent to the client. This approach allows for more flexibility in handling license add-ons than additive licenses do, because additive licenses are seen as a separate license pool of the same feature.
The upgrade license lifetime license server automatically activates or deactivates upgrade licenses at midnight, and may be limited by using the START and END directives in the same way as for other license types. The license server automatically activates or deactivates upgrade licenses at midnight; however, it is possible to create an upgrade license that does not expire You can also create a perpetual (non-expiring) upgrade license, as long as the exclusive license it is based on is perpetual. Also note that existing sessions remain unaffected when an upgrade license expires.
You can upgrade a particular exclusive license as many times as necessary, as long asCOUNT is within its range. It will sum up all of the license upgrades, allowing for a different expiration date for each upgrade.
There are restrictions on applying an upgrade license to an exclusive license. The upgrade license's lifespan expiration dates must be within the exclusive license's lifespanexpiration dates. In addition, and neither the upgrade nor exclusive license can beunlimited.
An upgrade license can be locked to the license serverHostIDs to prevent using the same upgrade license on more than one machine. Duplicated instances of an upgrade license within one license server will be discarded.
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 upgrade upgraded license count in bothLMX_GetFeatureInfo and 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 thatSHARE is limited toVIRTUAL only.
Some settings, likefeature name,COUNT andKEYTYPE, are required by thelicense generator to create an upgrade license. Optional settings that may be used with upgrade licenses areSTART,END,SHARE,HOSTID_MATCH_RATE and , HAL_SERVERS and server HostIDs.
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.
...