FNP - 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 fulfillment’s. For more information, see Fulfillments.

Fulfillments

Each time a license key is activated, a fulfillment is generated. The fulfillment contains information on the product, the hosts and the date when it was created. It is identified by a unique Fulfillment ID.

Hosts

In order to activate licenses, information on the hosts/licensed devices has to be entered:

  • Machine named license: a MAC address has to be provided.

  • User named license: a server host or server triad as well as a user name have to be provided.

  • Concurrent license: a server host or server triad has to be provided.

If this data changes (e.g. due to a change in hardware or users), the license needs to be rehosted.

For more information, see Rehost.

License Keys

The license determines how, when, and where you can use a licensed product such as ASCET Rapid Prototyping. To ensure the correct usage of the license product, these information are stored in digitally-signed, human-readable text files. This is called certificate-based licensing.

License Models

Machine named (PC Based)

  • License needs to be managed by each user on their own.

  • License can be carried with the PC.

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

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.

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.

Consolidating Licenses

Consolidating licenses will make it easier for you to manage your license files. Possible use cases are:

  • A user has licenses both for the main product and the add-on.

  • A lot of users have User named licenses which refer to the same server.

  • Consolidated licenses can be rehosted in one step instead of several separate steps.

  • You can only consolidate licenses if they have the same MAC address.