Defining License Terms for a Cloud Product
In Sentinel EMS, you can specify the licensing details for each Feature in the Product that you are defining. You can select two or more Features that require the same licensing details and specify the licensing terms only once.
NOTE Licensing terms for a Feature can be defined when the Product is being created, or during Entitlement generation if this option has been enabled.
Cloud License Types
You can choose from one of the following license types:
>Concurrent: A subscription-based license model in which there is a limit on the concurrent use of a Feature. You can specify the number of concurrent instances allowed for a feature, and select how concurrent instances are counted.
Concurrent license model attributes: Start Date, End Date, Concurrent Limit, Instance Counting, Usage Type, and Vendor Attribute.
>Prepaid: Specifies a limit on the maximum number of times a license can be used, in addition to license validity.
You can define a grace limit that allows use of a prepaid feature even after the maximum usage count has exhausted. The grace limit provides additional time to an end user to get the license renewed. You can use the Run-time API, getInfo, to send notifications to end users about the grace limit. For details of the getinfo API, see the Cloud Run-time Guide.
Prepaid license model attributes: Start Date, End Date, Grace Limit, Measurement Unit, Maximum Usage Limit, and Vendor Attribute.
Usage model: Count-based, but usage data is not used for billing.
>Subscription: Specifies the duration in which the license to use the product is valid (for example, 3 months, 6 months, or 1 year). The product can be used an unlimited number of times during the specified duration.
You can also define a grace period during which the end user can use an expired or exhausted license. The grace period provides additional time for a user to get the license renewed. You can use the Run-time API, getInfo, to send notifications to end users about the grace period. For details, see the Sentinel Cloud Run-time Guide.
>Postpaid: Specifies that the license to use the product is valid for the length of usage according to the usage model, which can be:
•Time-based: Billing can be done based on the duration for which the product is used.
•Count-based: Billing can be done based on the number of times the product is used within the specified period.
When you select the license type, you can also specify the values for the license terms. These license values will apply to all orders for this Product. For maximum flexibility, you can choose to leave the values to be specified at the time when each individual order is processed.
Alternatively, you can select Specify at Entitlement time from the License Type box, to specify the type of license only when generating an Entitlement.
License Attributes
| Attribute | Description | Default |
|---|---|---|
| Execution Count | ||
| Executions or Maximum Usage Limit |
The maximum number of times a Feature can be used. Supported values: 1–2147483647 |
100 |
| Date and Time | ||
| Start Date (and Time) | The license start date and time. If the start date and time are specified for a license, the associated Feature cannot be used before this date and time. | Current Date, 12:00 AM |
| End Date (and Time) |
The license expiration date and time. If the end date and time are specified for a license, the associated Feature cannot be used after this date and time. You can also set the end date to No Limit (never expires). |
— |
| Concurrency | ||
| Concurrent Limit |
The maximum number of concurrent instances allowed for a feature. Supported values: 1–32752 |
10 |
| Instance Counting |
Criteria for counting concurrent instances: >Per Login: Counts each login request as an instance. If the same user logs in to a feature multiple times, each login consumes one concurrency instance. >Per Identity: Counts each user as an instance. All login requests by the same user ID are counted as one instance, and consume only one concurrency limit. >Per Identity Per Station: Counts each user-machine pair as one session. All login requests by the same user from the same machine are counted as one session and consume only one concurrency limit. Concurrency is counted as follows: •A user accessing a single application instance on the same machine is counted as ONE. •A user accessing multiple instances of an application on the same machine is counted as ONE. •The same user accessing the multiple instances of the application on multiple machines is counted as N usage, where N is the number of machines. –For on-premises applications using entitlement-level caching mode, only Per Login option is supported. –For on-premises applications using feature-level caching mode, only Per Identity Per Station option is supported. |
Per Login |
| Grace | ||
| Grace Limit |
The additional number of days for which the Feature can be used after its license has expired. Supported values: 0–365 Applies to: Prepaid and Subscription licenses |
0 |
| Usage Type | ||
| Usage Type |
Required for data aggregation and tracking. >Time: Counts the duration of each login session. >Count: Counts each login-logout pair as one execution. Applies to: Concurrent and Postpaid licenses |
Time |
| Vendor Attribute | ||
| Vendor Attribute |
Stores a vendor-defined value, for example, employee role or data download speed. In your protected application, you can query the vendor attribute values and define application logic based on it. You can enter up to 255 alphanumeric characters in this field. A vendor attribute is not used by Cloud Connect in license enforcement. Applies to: Concurrent and Prepaid licenses |
Null |
NOTE While configuring license terms for Features in a Product, you can set a license attribute to Specify at Entitlement time to allow its value to be changed during Entitlement generation.
To define the license terms for a Feature:
1.In License Type, select the license type for the Feature.
NOTE To enable the license type to be specified when each individual Entitlement is processed, select the Specify at Entitlement time option instead of defining the value.
2.Modify the license attributes, as needed. This value is applied to all Entitlements for this Product.
•Concurrent: The Feature can be used concurrently by a specified number of users.
•Prepaid: The license to use the Product will be valid for a specified number of times.
•Subscription: The license to use the Product will be valid for a specified duration.
•Postpaid: The license to use the Product is valid for a specified duration, but the billing can be done based on the usage model (time or count based).
NOTE While configuring license terms for Features in a Product, you can set a license attribute to Specify at Entitlement time to allow its value to be changed during Entitlement generation. When this option is selected, you can specify a default value.
3.Click Save.