FNE - Basic Concepts

Entitlements

An entitlement represents what you, the customer, have the legal right to use; it is the right to obtain one or more licenses for a product. Think of an entitlement as an account, or a store of rights to use software, from which you can redeem licenses as needed. For example, let’s assume you order 10 concurrent licenses of ETAS’ Software’s product, ASCET Rapid Prototyping Version 6.0.0 You will be issued an entitlement for those 10 copies, specifying the duration of validity. Each entitlement is identified by a unique Entitlement ID, and contains one or more entitlement line items. For more information, see Activations.

Activations

Each Entitlement contains a number of Entitlement line items that can be activated, i.e. a license can be generated for them. The Activation maps to a single product, its license terms, the number of copies entitled, and other details needed to generate a license. Activations are uniquely identified by Activation IDs. If an Entitlement line item has been activated, the license key for it has been created.

The ETAS License & Download Portal will show activated licenses as fulfillments. For more information, seeFulfillments.

Trusted Storage

Trusted storage is a secure location bound to a particular device. In addition to its contents being encrypted, security features of trusted storage include:

  • Binding, which detects if trusted storage has been copied to another device by using producer-defined system identity characteristics. When license rights are placed in trusted storage, a „fingerprint“ made of system characteristics is placed in trusted storage; when license rights are acquired, the stored fingerprint is compared to the current system‘s fingerprint to detect changes.

  • Anchoring, which provides trust that trusted storage has not been deleted or rolled back to an earlier state on the same device. This prevents a device from restarting a trial license if trusted storage is deleted, for example. To achieve this, another stores a small amount of data in a location that is difficult to observe or access.

License Models

Machine named (PC Based)

  • License needs to be managed by each user on his/her own.

  • License can be carried with the PC.

  • Exchanging the PC will require you to generate a new license first.

User named (Server Based)

  • Easy and transparent license management by one server responsible.

  • License can be borrowed and carried with the PC.

  • License is available on each PC in the network.

  • 100% availability for one specific user.

Concurrent (Server Based)

  • Easy and transparent license management by one server responsible.

  • License can be borrowed and carried with the PC if enabled.

  • License is available on each PC in the network.

  • Several users share a fix amount of licenses; availability of a sufficient amount of free licenses is not granted.

See also

Requesting, Installing, and Uninstalling Machine-Based License of Type FlexNet Publisher (FNP)

Activating and Returning Machine-Based License of Type FlexNet Embedded (FNE)

Migrating FlexNet Publisher Licenses to FlexNet Embedded

Borrowing and Returning a License

Checking the License Status

Setting User Options