Flexible License Model

Specifies deployment type as:

>Cloud Served - Cloud LM: Generate connected licenses enforced in cloud and that can be consumed from anywhere.

>Cloud Served - Lease: Generate lease-based licenses enforced in cloud.

>On-premise Served: Generate licenses on-premises where they are consumed.

Allow Overwrite

(for Deployment Type)

>Specifies license is of type Network or Standalone for Cloud Served - Lease and On-premise Served deployment types.

>Specifies license is of type Cloud for Cloud Served - Cloud LM deployment type.

NOTE   It is suggested that you specify the license type of a license model when you copy or edit the license model. This will improve the performance during entitlement creation by reducing calls to the license generator.

>Network (for Cloud Served - Lease and On-premise Served)

>Cloud (for Cloud Served - Cloud LM)

Allow Overwrite

(for License Type)

The date (day, month, and year) before which the licensed software cannot be run.

A No start date checkbox can be used to exclude the start date. This option can be selected for licenses so that embedded devices that do not have system clock can be supported.

The date (day, month, and year) beyond which the licensed software cannot be run.

A Never expires checkbox can be used to indefinitely extend the end date.

Limit that sets the maximum number of users that can run the licensed software.

Maximum Value: 4294967294 if license version is 20 and 10000000 for license version 19.

Cloud Served

(This attribute group is available if Deployment Type is Cloud Served - Lease)

<5.5Preview> and <10.1Preview>

Lease Duration (hours)

(The field was named as Duration previously)

Duration of the lease.

When a license is distrbuted in chunks, each having the same duration.

Apply Full Duration

(The default setting is changed starting EMS 5.5)

Apply Full Duration

(The field was named as Unlimited previously)

The default setting of Lease Duration is full duration, which means that the feature end date would go into the license.

If you specify any setting other than full duration, then a license would be generated for that much duration. However, if the feature end date falls earlier than the lease duration, then the license is valid only up to the date that is earlier.

The default setting of full duration is useful in scenarios such as the one described here:

Example Use Case: Upfront Payment with Updates

You sell your application with a license valid for a year with full payment in advance. So, keep this check box selected. During the year, you may need to provide entitlement updates if the need arises, so review the automatic detection settings. These default settings ensure that entitlement updates are received exclusively and seamlessly.

If your application does not require Internet connectivity, but you want to force the application to connect to the backend frequently. In that case, you may clear this check box and issue a license in slices.

Selected

Lease Renewal Frequency (hours)

The time period to issue the next lease. By default, lease renewals are turned off—in coordination with the default setting of full duration. So, if the customer already has the full-term license, there is no need to obtain lease.

If you want to specify a value, set it around 75% to 80% of the lease duration value in order to give uninterrupted experience so that lease gets renewed before the lease is expired.

However, you must assess your use case in detail to see the overall impact of these values. A few example use cases are described here:

Example Use Case: Software Subscription Requiring Connectivity

Your application is available with subscription licenses on a monthly or quarterly basis and is billed accordingly. You also do not want customers to continue the use of the product in case the payment fails. So, your lease duration can be the subscription duration. Because of the connectivity requirement, you can dynamically control the software access by disabling the line item or entitlement.

Example Use Case: Software Subscription Without Connectivity

Your application is available with subscription licenses on a monthly or quarterly basis and is billed accordingly. You also do not want customers to continue the use of the product in case the payment fails. So, your lease duration can be the subscription duration. However, in this case, whenever you disable the line item or entitlement, the overuse cannot exceed the lease duration as it may so have happened that the licensed application took the last lease just before you disabled the line item or entitlement.

Do Not Renew Automatically (Exception: Entitlement Updates)

(The default setting is changed starting EMS 5.5)

Do Not Renew Automatically (Exception: Entitlement Updates)

By  default, lease renewals are stopped without any impact on the entitlement updates. Entitlement updates will be delivered as per the automatic detection settings.

See Also: Examples: Lease Renewals and Entitlement Updates <5.5Preview> and <10.1Preview>

Selected

(438000 hours is the maximum value allowed)

1 hour

Usage

(This attribute group is available if Deployment Type is On-premise Served or Cloud Served - Cloud LM)

Specifies whether usage will be collected for the on-premises served licenses.

NOTE   The Collect Usage flag is available for License Version 21 and above.

Specifies whether license can be held or not.

-No Hold Time

-Application Specified

-License Specified

Specifies the license version.

While creating a redundant licenses it is required that its redundant License Managers use majority rule. This field, when selected dictates that a majority (over half) of the redundant License Managers must be up and running for a request for that active license to be serviced. For example, if you have defined five redundant License Managers and majority rule is in effect, at least three of them must be up and running or a request for that license will fail. If majority rule is not in effect, your customer could set up the redundant License Managers and then separate them on different networks. Each redundant License Manager, not being able to see any of the others, would then allow your customer to double, triple, quadruple, etc., the total license count without purchasing that many license tokens. So, although you can turn majority rule off, you incur a huge security risk in doing so. If majority rule is in effect for a particular license and the majority of License Managers for redundant licenses go down then requests for licenses for that feature or version are no longer serviced until the majority of License Managers are up and running again. However, requests for non-redundant licenses or redundant license codes not using majority rule will continue to be serviced. We recommend that you always enable majority rule while generating licenses.

This attribute is visible only if the Redundancy attribute is selected.

Yes

Number of license servers available to support redundancy.

This attribute is visible only if the Redundancy attribute is selected under Policy.