Products

>Contains features that are specific to customer requirements.

>You modify the the product definition every time a feature is added or removed from the product.

>You cannot remove a feature from a deployed product.

>Contains features that are specific to customer requirements.

>Acts as a template for creating variants.

>Flexible product definition enables you to associate new features with the versionless product when defining variants.

>Versionless products do not have versions.

>The activation method is Define in Entitlement.

Enforcement Type

The Sentinel enforcement to use for protecting and licensing the product features. The options shown depend on the available enforcements.

>Sentinel LDK

>Sentinel RMS (Shown if only Sentinel RMS is available in addition to Sentinel LDK)

>Sentinel Fit (Shown if only Sentinel Fit is available in addition to Sentinel LDK)

>Other Enforcements. Select this option for Sentinel RMS or Sentinel Fit. (Shown if both Sentinel RMS and Sentinel Fit are available in addition to Sentinel LDK)

Namespace

(Visible only if more than one namespace is available)

The namespace in which the product is stored.

The type of product: Versionless* Applicable only for Sentinel RMS and third-party entitlements or Default

(Available only for Default products)

Version of the product.

Example: aaa.bbbb.cccc.dddd, for example, 5.0.0.100.

Required

Numeric identifier for the product.

Optional

The fixed number of licenses to consume in each activation.

The Fixed Quantity must be a divisor of the total quantity, where:
Fixed Quantity x Number of Activations = Total Quantity

Note: This field appears only when the Fixed activation method is selected in the Additional Attributes section.

Additional information about the product. For example, you may want to highlight product features, differentiate between similar products, and so on.

For variants, you may want to provide information about each variant flavor.

Reference identifier that identifies the feature in an external system.

Reference identifier that identifies the feature in an external system.

Reference identifier that identifies the feature in an external system.

The method of defining and allocating the quantity of licenses available for the product in an entitlement.

Activation methods:

>Define in Entitlement: The quantity of licenses to activate is set during entitlement creation using one of the following activation methods.

>Fixed: The total number of licenses can be divided equally for consumption in multiple activations.

When you select Fixed, the Fixed Quantity field is added to the Define Attributes pane enabling you to specify the fixed amount to be consumed in each activation.

>Partial: The provided quantity can be consumed in multiple activations. Each activation reduces the total number of available activations by the quantity activated.

>Full: The user must activate the entire quantity provided in one activation.

> Unlimited: The user can perform an unlimited number of activations for the product.

Enforcement Type

The Sentinel enforcement to use for protecting and licensing the product features. The options shown depend on the available enforcements.

>Sentinel LDK

>Sentinel RMS (Shown if only Sentinel RMS is available in addition to Sentinel LDK)

>Sentinel Fit (Shown if only Sentinel Fit is available in addition to Sentinel LDK)

>Other Enforcements (Shown if both Sentinel RMS and Sentinel Fit are available in addition to Sentinel LDK)

Namespace

(Visible only if more than one namespace is available.)

The namespace (also known as batch code) that represents your company's unique vendor code.

Numeric identifier for the product.

You can apply the same Product ID to multiple products. This lets you replace one product with another. For example, you might want to create an "upgrade" product for a salable item to enable customers to pay the price difference and upgrade from a subscription license to a perpetual license. In this case, both the original and upgrade products would need the same product ID.

Required

Additional information about the product. For example, you may want to highlight product features, differentiate between similar products, and so on.

A product that is distributed with a license that is not locked to a specific device and can therefore be installed freely by any user on any device.

Typical uses include:

>Trial licenses (free for up to 90 days), which can start from the date of license generation or first use, depending on the License Model. (The Execution Count license model is not relevant for products that are not locked to a device.)

>"Unlimited" products that or may not have licensing restrictions. For example, you might apply a Perpetual license, you may decide to limit the time period, you may use a different mechanism to license the application, or you may decide not to impose any licensing restrictions at all.

For more details, see the section on unlocked products in the Sentinel LDK Software Protection and Licensing Guide.

The locking type for the product based on the type of protection key to be distributed and the required level of security and functionality.

About Sentinel Protection Keys:

>Sentinel HL keys provide hardware-based protection by connecting a physical unit, such as a USB device, Express Card, or chip, to the customer's machine.

>Sentinel SL keys are virtual, software-based keys that reside in the secure storage of the customer's machine.

Although SL keys provide a high level of protection, HL key security is superior. If the locking type allows for both HL and SL keys, then HL key-level protection is provided if the Product is shipped only with HL keys (that is, the Product is never shipped with SL keys). If the Product is shipped with SL keys, then the overall level of security should be considered to be that provided by SL keys. This is because there is always the possibility that an attacker might have access to a deployed SL key.

For more information, see the section on choosing the protection level for your products in the Sentinel LDK Software Protection and Licensing Guide.

Relevant for: HL locking type

Enables you to upgrade any Sentinel HL (HASP configuration) keys in the field to Sentinel HL (Driverless configuration) keys.

Advantages over Sentinel HL (HASP configuration) keys:

>On Microsoft Windows:

• Uses HID drivers, which are an integral part of the Windows operating system. Customers can often use these keys without installing any additional support software.

•Does not require the Run-time Environment to protect an application.

>Supports a higher number of features.

>Provides larger on-key memory space.

Lets you manage time-based licenses for Sentinel HL (Driverless Configuration) keys using a virtual clock when no real-time clock is available.

NOTE   For Sentinel SL keys, the virtual clock is always available and does not require configuration.

How does Virtual Clock work?

The expiration period or date for a time-based license is initially calculated according to the system clock of the end user's machine. Sentinel License Manager reads the system time at startup (by default, part of the machine startup) and then uses its internal running time to calculate the time. When an application that is protected with Virtual Clock runs for the first time, Sentinel License Manager queries its internal clock to determine the start time of the software’s license duration.

>If the license duration is a fixed period (for example, 30 days or 1 year), Sentinel License Manager calculates the actual date on which the license must stop working and stores this information in the secure storage area of the Sentinel key. The secure storage for a Sentinel SL key is on the hard drive of the end user's computer. The secure storage for a Sentinel HL key is in the HL key.

>If the license is set to expire on a specific date, Sentinel License Manager records that date. The expiration time is determined using the formula:

[current Sentinel License Manager time] + [number of seconds to expiration]

For more information, see the Sentinel LDK Software Protection and Licensing Guide.

Rehost

(Visible only if an SL Locking Type is selected)

Relevant for: Any SL locking type

Allows the end user to transfer a Sentinel SL protection key from one computer to another.

The rehosting process is performed entirely by the end user, with no interaction from the vendor.

If no product is set to Disable, but one or more products are set to Enable, then rehosting is enabled for the Sentinel protection key.

Use to select one or more features if you want to open the Configure License Model dialog box.

When you select at least one check box, the Configure License Model button is enabled.

You can select the Feature Name check box to configure the license model for all features simultaneously.

Specifies if an associated feature will be included or excluded in the entitlement.

<5.5Preview>

Note: Although this option is visible for Sentinel Fit, it is not supported and should not be used. For best results, leave Included (Optional) as is.

Default License Model

The default license model for the associated feature.

Fixed

Multiplier

Displayed if the Component Multiplier Visible property is selected in the Administration Console.

For each feature, enter a value for Multiplier. This quantity is the multiplying factor at product-feature relationship level. This value is multiplied with the line item quantity to get the total quantity for the product-feature license.

Another property, User Limit Configuration, also available in the Administration Console, regulates the usage of the Component Multiplier and the license model user limit.

For more information on Component Multiplier Visible and User Limit Configuration refer to the Administration Console.

Buttons used to open the Configure License Model dialog box.

Enables you to configure the license model associated with the selected feature or features.

Enables you to associate and configure a license model for a feature. A feature can be associated with one license model.

To start configuring a license model, do one of the following:

>In the Associated Features pane, select the check box for one or more features and click the Configure License Model button.

Note: If you select multiple features, they must all be associated with the same license model.

>In the Actions column, click the Configure License Model button for the specified feature.

Integer that identifies the memory file and is used by your application to refer to that file.

Size of the memory file in bytes.

For user-created memory files, the size is automatically determined based on the text length and offset.

Optional

Although this attribute is optional, you must set either the memory file size or text value (or both).

Text

Allow Overwrite

The memory data in text format. You can add or edit text if needed.

To enable the value to be changed when creating an entitlement, select the Allow Overwrite check box.

Optional

Although this attribute is optional, you must set either the memory file size or text value (or both).

Specifies how to attach the memory file to the product.

Sentinel EMS applies memory files in the order in which they are added to the product.

To modify a deployed, default memory file:

1.Select a memory file with the same File ID that is already associated with product's Product ID.

2.Select Add.

To modify a deployed, user-created memory file:

1.Select a memory file with the same File ID that is already associated with product's Product ID.

NOTE   If you plan to replace only some of the text, then, in the memory file on the Memory page, make sure that the Offset and Size (Bytes) are defined to insert the text at the required location.

2.Do one of the following:

•To replace all of the text, select Overwrite.

•To replace some of the text, select Add. The original text is overwritten only where the offset and size overlap the original settings.