cancel
Showing results for 
Search instead for 
Did you mean: 

License Pooling and FEATURE Lines

License Pooling and FEATURE Lines

Summary

When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different .

Synopsis

When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different .

Discussion

When attempting to ensure that two 'license' lines differ in some way to ensure that the total count is pooled rather than just the last element count been used, it is necessary, according to the documentation, to ensure that one of the following elements are different -
INCREMENT lines form license groups, called license pools, based on the following fields and keywords:

?
Feature name
?
Version
?
BORROW
?
DUP_GROUP
?
FLOAT_OK
?
HOST_BASED
?
HOSTID
?
PLATFORMS
?
TZ
?
USER_BASED
?
VENDOR_STRING (if configured by the vendor as a pooling component)
?
VM_PLATFORMS
It should also be noted that this applies to INCREMENT lines only, the following sequence involving a FEATURE line will not work (with the VENDOR_STRING pooling enabled) -
FEATURE f1 flexera 1.0 permanent 3 VENDOR_STRING=Type_1 SIGN=....
INCREMENT f1 flexera 1.0 permanent 1 VENDOR_STRING=Type_2 SIGN=....
Two INCREMENT lines are needed
Labels (1)
Was this article helpful? Yes No
No ratings