...
When the license server gets a request for a token-based license, it uses one or more other licenses (as specified in the license file) to fill the request, rather than directly using a license for the originally requested feature. The feature that is used to allow the checkout is referred to as a token dependency.
When a normal network license is checked out, the license appears in the license file with a count. For example:
| Code Block | ||
|---|---|---|
| ||
FEATURE MyFeatureA |
...
{ |
...
VENDOR = MyCompany |
...
COUNT = 5 |
...
KEYTYPE = EXCLUSIVE |
...
MAJOR_VERSION = 1 |
...
MINOR_VERSION = 0 |
...
... |
...
} |
However, when a token-based license is checked out, it appears in the license file without a count, and instead includes a dependency on one or more other features that are used to allow the checkout. For example:
| Code Block | ||
|---|---|---|
| ||
FEATURE MyFeatureB |
...
{ |
...
VENDOR = MyCompany |
...
KEYTYPE = TOKEN |
...
MAJOR_VERSION = 1 |
...
MINOR_VERSION = 5 |
...
TOKEN_DEPENDENCY = "FEATURE=MyFeatureA VERSION=1.0 COUNT=5" |
...
... |
...
} |