Token Structure When Using FlexNet Operations

Note:This section complements the information described in section Tokens.

A token is not a built-in concept in FlexNet Operations. Therefore, it must be represented in FlexNet Operations using a compound structure with three parts: a product with a single feature, and a dedicated license model.

Note:The product must contain a feature for historical reasons. The feature as such does not provide any functionality in the context of Elastic Access.

Producers create:

•

a license model of type “Dynamic Monetization | Elastic Access”,

•

a product (which, for clarity, could simply be named “Elastic Token”),

•

a feature (which, for clarity, could also be named “Elastic Token”),

and then add the feature to the product and associate the license model.

The following diagram depicts the token structure:

A token is modeled by defining a product and giving it a single feature and associating it with a license model.

Note:The name "Elastic Token" is suggested here for clarity of illustration. You may call the product/feature combination anything you like, according to your own preference.

For step-by-step instructions about creating an entitlement line item for tokens, see section Preparing Your Dynamic Monetization Instance: Information for Producers Using FlexNet Operations.