Token Based Licensing

Token Based Licensing

Vendor-defined is an optional modifier which is Used for publisher-defined entitlement such as token based. LM_A_CHECKOUT_DATA is a crucial part to make this work.

Token-based licensed vendor daemons, the checkouts/checkins are based on tokens instead of features. For example, a customer purchases some number of tokens from you in order to run the application "A1", the client needs to check out x number of tokens "t1".
In license files, the tokens are defined in the FEATURE/INCREMENT lines. The clients check out the tokens in order to run the applications. In report logs, the checkout/checkin events are based on tokens as well.

 

An example for Token-Based Licensing:

 

1. The tokens "t1" and "t2" are defined in the license file.

FEATURE t1 lmd 1.0 1-Jun-2011 1000 SIGN=123456789
FEATURE t2 lmd 1.0 1-Jun-2011 2000 SIGN=987654321

2 A client checks out six tokens of "t1" in order to run the product "Product1" containing the feature "F1".

In debug log, it shows

10:58:45 (lmd) OUT: "t1" alee@supreme [F1] (6 licenses)

3. A client checks out two tokens of "t1" in order to run the product "Product2" containing the feature "F2".
In debug log, it shows

10:58:53 (lmd) OUT: "t1" alee@supreme [F2] (2 licenses)

4. In the report log, the usage events may look like:

6/8/2010 10:58:45: CHECKOUT t1 (in use: 6 of 1000) (alee / supreme) vdef: F1
6/8/2010 10:58:53: CHECKOUT t1 (in use: 2 of 2000) (alee / supreme) vdef: F2

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Nov 26, 2021 02:04 AM
Updated by:
Contributors