...
| 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.
| Anchor |
|---|
| License pools |
|---|
| License pools |
|---|
|
License pools
One primary use for token-based licensing is to let users purchase a number of pseudo-features that each require one or more real licenses. This gives users a "pool" of licenses they can draw upon for license checkout requests, providing the flexibility to use various combinations of features as their needs require.
...
| Code Block |
|---|
|
FEATURE MySolutions
{
VENDOR=ABC_Software COUNT=20 KEYTYPE=EXCLUSIVE VERSION=1.0
KEY=bhq3ed873qcrKHG6783rhJgvkhvTUtxcuBiouVtyCuyVy78Gftq...
}
FEATURE MyDraw
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=1.0
TOKEN_DEPENDENCY="FEATURE=MySolutions VERSION=1.0 COUNT=5"
KEY=b978bv5ybui7Noyg6c3Vd57fngN987NGSC54sDiugU6v5eio8g...
}
FEATURE MyWrite
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=1.0
TOKEN_DEPENDENCY="FEATURE=MySolutions VERSION=1.0 COUNT=2"
KEY=yig*bv7tu6r879yu09yut75evbGJvHGHdrCHJVJGCt79g78gvv...
}
FEATURE MySpreadsheet
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=1.0
TOKEN_DEPENDENCY="FEATURE=MySolutions VERSION=1.0 COUNT=1"
KEY=hygvCTYGg6r67fg890hbyvGTCVKJBjhc5r7y9joiVGckjlnut8...
} |
| Anchor |
|---|
| Product suite licenses |
|---|
| Product suite licenses |
|---|
|
Product suite licenses
Product suite licenses specify that one token-based license depends on multiple real licenses. Product suite licenses enforce a logical AND rule, requiring all licenses to be valid in order to perform a checkout. This is essentially the opposite of license pools, which specify that multiple features depend on a single real license.
...
| Code Block |
|---|
|
FEATURE Lower_Priced_License
{
VENDOR=ABC_Software COUNT=5 KEYTYPE=EXCLUSIVE VERSION=1.0
KEY=mBpIAWB9Uuzl2b2B3v]8GJqW300arlnWmnT01nZXSOIYdF...
}
FEATURE Higher_Priced_License
{
VENDOR=ABC_Software COUNT=10 KEYTYPE=EXCLUSIVE VERSION=1.0
KEY=mBpIAWB9Uuzl2b2B3v]vcsFBx7qEQG1SwXCz8A9d6U3vSKT...
}
FEATURE MyDraw
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=1.0
TOKEN_DEPENDENCY="FEATURE=Lower_Priced_License VERSION=1.0 COUNT=5"
KEY=mYsfn30C6ShBYszCq2WVicpTZXQwkfKJTohkzg1wNkle163...
}
FEATURE MyDraw
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=1.0
TOKEN_DEPENDENCY="FEATURE=Higher_Priced_License VERSION=1.0 COUNT=10"
KEY=2w66Ng3wVSVp6ttmWCc8GyJqW300arlnWmnT01nZXSOIYdF...
} |
| Anchor |
|---|
| Cascading licenses |
|---|
| Cascading licenses |
|---|
|
Cascading (recursive) licenses
Cascading licenses let you specify a recursive list of token-based licenses, all of which must be available in order to fulfill a checkout request.
...
| Code Block |
|---|
FEATURE Sketcher
{
VENDOR=ABC_Software COUNT=10 KEYTYPE=EXCLUSIVE VERSION=1.0
KEY=2w66Ng3wVSVp6ttmWCc8GyJqW300arlnWmnT01nZXSOIYdF...
}
FEATURE MyDraw
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=2.0
TOKEN_DEPENDENCY="FEATURE=Sketcher VERSION=1.0 COUNT=2"
KEY=4i]mYsfn30C6ShBYszCq2WVicpTZXQwkfKJTohkzg1wNkle...
}
FEATURE MyWrite
{
VENDOR=ABC_Software KEYTYPE=TOKEN VERSION=2.0
TOKEN_DEPENDENCY="FEATURE=MyDraw VERSION=2.0 COUNT=1"
KEY=mBpIAWB9Uuzl2b2B3v]vcsFBx7qEQG1SwXCz8A9d6U3vSKT...
} |
| Anchor |
|---|
| Token sharing |
|---|
| Token sharing |
|---|
|
Token sharing and token dependency sharing
Token-based licenses are always unlimited; therefore, sharing tokens is unnecessary. However, sharing token dependencies may be useful in some cases.
...
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.
...