...
As you can see from the two different scenarios below, a pool of token-based licenses gives customers significantly more flexibility than purchasing a specific number of licenses for each feature. The users can check out any combination of the features, up to the maximum 20-license limit.
Example Scenario 1
Feature | # of licenses consumed per checkout | # of checkout requests | Total licenses consumed |
MyDraw | 5 | 2 | 10 |
MyWrite | 2 | 3 | 6 |
MySpreadsheet | 1 | 3 | 3 |
Totals |
| 8 | 19 |
Number of licenses remaining |
|
| 1 |
Example Scenario 2
Feature | # of licenses consumed per checkout | # of checkout requests | Licenses consumed |
MyDraw | 5 | 1 | 5 |
MyWrite | 2 | 4 | 8 |
MySpreadsheet | 1 | 7 | 7 |
Totals |
| 11 | 20 |
Number of licenses remaining |
|
| 0 |
Example
The following example shows a token-based license for the license pool scenario described above, where MySolutions is a license pool that is drawn upon to fulfill license requests for MyDraw, MyWrite and MySpreadsheet.
...
For example, MyDraw may be composed of two modules: Sketcher and Printer. A token-based license can specify that in order to use MyDraw, you must have 1 license of each of the two modules.
Example
The following example shows a token-based license for the product suite license scenario described above.
...
The order of the token-based licenses in the license file determines the order that alternate checkouts are attempted. For example, if the MyDraw features's Lower_Priced_License token-based license precedes the Higher_Priced_License token-based license, then Lower_Priced_License will be preferred for filling checkout requests. Higher_Priced_License will be used only if Lower_Priced_License is unavailable. End users can change the license order if they desire.
Example
The following example shows a license for the alternate license scenario described above. Note that the first MyDraw token-based license refers to Lower_Priced_License, so this will be the preferred license for MyDraw checkout requests.
...
The maximum number of recursive dependencies you may define for a token-based license is 256. (However, there is no limit on the number of token-based licenses you may define.)
Example
The following example shows a token-based license for the cascading license scenario described above.
...