Products

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

When set to Yes, enables Sentinel EMS to initiate provisioning requests for the product. When you apply provisioning, you must associate a provisioning method and plan with the product.

For more information, see Provisioning.

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

Reference identifier that identifies the product in an external system.

Reference identifier that identifies the product in an external system.

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 may 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.

Note: Defining a product as unlocked from a device is permanent and cannot be reverted after the product is marked as Completed.

The level of protection for a product according to the type of Sentinel protection key supplied with the product. You set the locking type when defining a product. Locking types can be hardware-based (Sentinel HL keys) or software-based (Sentinel SL keys). When using the Cloud Licensing service (CL keys), you must select one of the SL AdminMode options, such as the default HL or SL AdminMode or SL UserMode option.

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 in or excluded from the entitlement.

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.

Specifies how to apply the license model attributes to the feature. Only one license model may be associated with a feature.

Which option is best?

You select an option based on what you are trying to achieve.

For new products, although you can select any of the options, for the most flexibility when updating the expiration date, number of days, or execution count license terms, we recommend selecting System-specified.

System-specified enables you to resell the product to the same customer without changing the product properties. For example, suppose you sell a product with a one-year subscription. At the end of the year, you can renew the subscription by setting the new expiration date in the entitlement, without changing the product properties in Sentinel EMS.

If you need to update the concurrency or change the license model for the same customer's existing product, select Add or Overwrite instead.

Note: If you receive an error message related to applying a license, you may need to select another Apply License option.

Buttons used to open the Configure License Model dialog box.

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.