Activation Transaction Types

FlexNet Publisher supports two transaction types:

•

Composite Transactions—From FlexNet Publisher 11.14.0, composite transactions are fully supported for all servers. From this version onwards, it is best practice to use composite transactions for all interactions with servers.

•

Single-Action Transactions—Single-action transactions perform one activation action per transaction. For example, using single-action transactions to activate two fulfillment records from a license server to a FlexEnabled client involves issuing two separate transactions.

From FlexNet Publisher version 11.14.0, single-action transactions have been deprecated.

Composite Transactions

Composite transactions are supported for life-cycle operations between the publisher’s activation server and the license server, as well as between the license server and FlexEnabled clients. A single composite transaction between the publisher’s activation server and the license server uses one request from the license server and one response from the publisher’s activation server to perform any number of activations, repairs, returns, and upgrades on the license. For example, a composite transaction can perform any of the following licensing life-cycle operations, providing greater flexibility in managing trusted-storage license rights:

•

Return one or more fulfillment records

•

Activate one or more fulfillment records

•

Modify one or more fulfillment records (for example, to change the license count)

•

Combinations of these actions to perform partial or full returns or upgrades

Additionally, composite transactions store more details about the activation than single-action transactions do, allowing a better chance to fully recover a trusted storage on the license server should errors occur.