...
| The information on this page refers to v5.0 1 and laternewer, which introduced the ability to share token-based licensesbanned sharing both tokens and their dependencies at the same time. For documentation applicable to earlier versions, see documentation for previous versions. |
There are many different ways you can use token-based licensing, as described in the following examples.
...
Token dependency sharing allows the features and their instances to share their available licenses and thereby use the licenses more efficiently in cases where you do not want to count features' licenses independently. Dependency sharing can be implemented using multiple token-based licenses that share a common dependency.
| Note | ||
|---|---|---|
| ||
Sharing both tokens Tokens and token dependencies has the same effect as sharing just token dependencies, so although possible, this usage has no additional benefit. The total number of token dependency licenses in use will remain the same. Although the number of token-based licenses in use will be different, token-based licenses are unlimited, so combining the two sharing methods will have no effecttheir dependencies cannot both be shared at the same time. |
Example Scenario
For example, say you have two token-based features, "ModuleA" and "ModuleB," with a common token dependency, "Product." ModuleA requires three Product licenses and ModuleB requires two Product licenses, and there are a total of 10 Product licenses.
...