Page History

The KEYTYPE directive specifies whether a network license is exclusive, additive, upgrade or token-based.

• By default, all network licenses are exclusive. Exclusive licenses are taken into account before other license types. If two exclusive licenses of the same feature name are present, the first is used and the second is discarded.
• Additive licenses

...

• coexist with exclusive licenses and other additive network licenses of the same feature name, and are seen as a separate license pool of the same feature.
• Upgrade licensesare similar to additive licenses, but rather than co-existing with exclusive license of the same feature name, they are applied to the corresponding exclusive license during license server startup, transparent to the client. Upgrade licenses increase the license count so that only one feature exists.  
• Token-based licensing is always additive, and lets you specify that a particular feature should use one or more other licenses to fulfill checkout requests. 

Usage and recommendations

The KEYTYPE This directive can be used only with network licenses; accordingly, the COUNT directive directive or TOKEN_DEPENDENCY directive must be set if KEYTYPE is set. The

• To prepare an upgrade license, create a feature with the same name as the original license, set the number of licenses using the COUNT directive, and set KEYTYPE="UPGRADE" in the XML license template file. (See Upgrade licensing for more information about how to define an upgrade license.)
• To prepare an additive license, set KEYTPE="ADDITIVE" in the XML license template file.
• To prepare a token-based license, the "KEYTYPE=TOKEN" directive must be used together with

...

• the TOKEN_DEPENDENCY directive. Token-based licenses are always additive. (See Token-based licensing for more information about how to define a token-based license.)

...

Anchor
additive-upgrade additive-upgrade

Additive and upgrade licenses

To add

Usage and recommendations

Adding licenses for software features that a customer buys later than after the initial purchase of a license can be easily accomplished by using multiple additive licenses, which don’t require that you change the original license. To prepare an additive license, you need to create a feature with the same name as the original license, set the proper version and count numbers, and add the line <SETTING KEYTYPE=”ADDITIVE”> to the XML license template file.without changing the original license, you can use either additive or upgrade licenses. 

While upgrade licenses increase the license count for an existing feature, additive licenses are treated By default, all network licenses are exclusive, which means that they are taken into account first. During checkout, additive licenses are seen as a separate license pool of the same feature. You should ensure all needed features are checked out at one time, because a client cannot check out licenses from two different license pools; therefore, you must checkout licenses in the proper order when using additive licenses.

It is important to understand that multiple additive licenses (even when combined with an exclusive license) do not behave exactly the same as one license with the a combined license count (as opposed toupgrade licenses).

If a client tries to acquire multiple additive licenses, the maximum number of licenses that can be acquired perLMX_Checkout call will be equal to what one license holds. The license server will not perform checkouts across multiple additive licenses.

For example: One A license server has one exclusive and two additive licenses of feature "ABC" are available on a license server , with the license counts 1, 2 and 3. If When a client tries to acquire requests one "ABC" license, the first exclusive license with count 1 will be used. If this same client later attempts to acquire another three more "ABC" license, there will not be enough licenses in the first license; thus, the client will be denied. However, if another client requests one or two licenses, the checkout will succeed, because it will take a license from the other license pool.licenses, only the additive license with the license count of 3 will be used rather than using one license from the first additive license and two from the third additive license.

To avoid To minimize problems, you should checkout all needed additive licenses at one time. , or preferably, useupgrade licenses instead, which eliminates such potential problems completely.