Glossary

Activation

Refers to the generation of a license code or file for a product or product suite* Product suites are available for Sentinel RMS and third-party entitlements.

<5.5Preview>

Batch Code

Also known as Namespace

In Sentinel EMS, a Sentinel LDK batch code is known as a namespace.

A batch code (or namespace) represents your company's unique vendor code. When you order Sentinel protection keys from Thales, you specify your batch code, which is both written to the keys before dispatch and printed on the outside of each Sentinel HL key. Your company can have one or more batch codes. The batch code for Sentinel protection keys with a demo vendor code is DEMOMA.

A Sentinel RMS license model. Useful when a user needs to travel and wants to take along the licensed application. A network license can be used as a commuter license.

Commuter licenses differ from Auto-checkout, because commuter licenses must always be manually checked out from the network before use.

Specifies whether your licensed application will be hosted on the cloud or will be installed locally.

>Cloud: Your licensed application will be hosted on a Cloud Server and the customers will access the application from cloud.

>On-premises: Your licensed application will be installed on the customer's machine.

For more information, see the section on deployment modes in Sentinel RMS Developer Guide.

Software licensing may break down if the customer sets back the system time inadvertently, such as, to prevent the license expiration.

This term is provided as a check box option in the Sentinel EMS portal. Selecting or clearing this check box specifies if the software vendor wants to deny or allow the use of the licensed application in case of system clock tampering.

An additive license code appends changes to an existing additive license.

Whereas, an exclusive license code completely replaces the old license with a new license.

After an application obtains a license, it also faces the task of maintaining the license. A license must be renewed by the application on a regular schedule or the license will be reclaimed (keeping it booked so that new clients do not obtain it). This is managed by sending an update call to the license server that issued the license.

So, lifetime in minutes refers to the time interval specified for the license (key) to send updates to the license server.

The fixed calendar dates beyond which the licensed application cannot be used.

A license version is always associated with Sentinel RMS licenses. It maps to the SDK version in which the license was introduced. If a new feature or license property is introduced in the SDK, then the license version will be upgraded as the new feature would not be available with the earlier SDKs. For example, grace licenses were introduced in SDK v8.0.x and cannot be generated with the previous version RMS SDKs.

Namespace

(for all enforcements except for Sentinel LDK )

A namespace acts as a logical partition for your Sentinel EMS workspace, providing unique storage locations within Sentinel EMS.

If you have multiple product lines, you can maintain different namespaces for them. The features, products, and product suites defined in a namespace are available only to those users who have permissions for that namespace. Users with roles that have entitlement-related permissions (such as order takers) can access these items from all namespaces.

Namespace

(for Sentinel LDK)

Also known as Batch Code

A Sentinel EMS namespace is known as a batch code in Sentinel LDK.

A namespace (batch code) represents your company's unique vendor code. When you order Sentinel protection keys from Thales, you specify your namespace, which is both written to the keys before dispatch and printed on the outside of each Sentinel HL key. Your company can have one or more namespaces. The namespace for Sentinel protection keys with a demo vendor code is DEMOMA.

In Sentinel EMS, a namespace also acts as a workspace, differentiating between separate storage locations, similar to those that are designated for use with Sentinel RMS. If you have multiple namespaces, the features, memory files, and products in each namespace are available only to those users who have permissions for that namespace. Users with roles that have entitlement-related permissions (such as order takers) can access these items from all namespaces.

The maximum number of users a network license can support concurrently.

Refers to the format of generated RMS licenses, such as, encrypted and readable.

For server-locked licenses, you can specify two sets of locking criteria known as primary and secondary locking criteria. The licensed application will run if any of the locking criteria is matched.

Group of products derived from a common product platform. These goods or services use similar or same production processes, have similar physical characteristics, and may share customer segments, distribution channels, pricing methods, promotional campaigns, and other elements of the marketing mix. Products comprising a family are usually priced and discounted as a package. Several product families make up a product portfolio.

Revocation is a process by which a software vendor allows return of licenses by the customer.

NOTE   Third-party licenses can be revoked using the Revoke Immediately option.

The hardware-based protection and licensing component of Sentinel—a physical Sentinel HL key (such as a dongle).

>Sentinel HL Basic key. Standard Sentinel HL local key that is used to protect software, and has a perpetual license. This key:

•Does not have any memory functionality.

•Does not support concurrency or remote desktops.

•Does not support V‑Clock.

>Sentinel HL network key. Any Sentinel HL key that supports concurrency. This includes the following keys:

•Sentinel HL Net key

•Sentinel HL NetTime key

•Any Sentinel HL (Driverless configuration) key except for Sentinel HL Basic keys

>Sentinel HL (Driverless configuration) key Sentinel HL key that does not require the Run-time Environment to protect an application or data file on a Windows machine.

>Sentinel HL (HASP configuration) key. Sentinel HL key that is fully compatible with protected applications that require the older HASP HL keys.

For more information about Sentinel HL keys, see Sentinel LDK Software Licensing and Protection Guide and Sentinel Hardware Protection Keys.

The software-based protection and licensing component of Sentinel—a virtual Sentinel HL key. Product activation is instantaneous. End users can immediately start using the software with its fully-licensed functionality. The online connection with end users can enable user registration data to be collected and used for marketing purposes.

A type of license that is intended for single computers.

Start Date (for an entitlement line item)

The date before which no operations, such as login by product key, activation, or revocation* All revocation options are available for Sentinel RMS (except for cloud-served lease entitlements). For cloud-served lease entitlements, third-party entitlements, and Sentinel Fit, use "Revoke Immediately". Revocation is not supported for Sentinel LDK., are allowed on an entitlement Glossary.

NOTE   As one line item can have multiple licenses for multiple features, specifying a license start date different from the line item start date helps in addressing different start dates for multiple features.

The time period (defined in the number of days or hours) to allow the use of the licensed application.

A Sentinel RMS license model, which is all of the following:

>Trial: A temporary license that allows software usage for fixed days or hours starting from the first use.

>Standalone: A license typically meant for non-networked environments (such as home users).

>Node locked: Means the software can only be used on one machine.

>For Network Licenses: Specifies the number of tokens (concurrent instances) a license can have.

>For Standalone Licenses: Setting a user limit for standalone licenses will limit the number of licensed features used concurrently. For example, a customer purchased a licensed application, which has five features licensed and hard limit is set to three. This limit will ensure that not more than three licensed features are used concurrently. However, since standalone licenses can be used by any number of local applications (instances), the hard limit set may not hold much meaning, especially in desktop environments.

It is useful for platforms where the whole OS is treated as a single application and so all tasks/processes share memory space. In such environments user limit can be used with standalone licenses for controlling features of a device.

Vendor-to-Customer package file. A file that contains license information for an activated product. The V2CP file is available for download at the end of the activation process. For offline activations, the vendor or end user (customer) uses the V2CP file to apply the encoded license on the relevant computer. V2CP files can safely be sent by email.

You can customize the V2CP file name format, if needed. For details, see License File Name (V2CP) Configuration.

Refers to miscellaneous information that a software vendor can include as a part of the license code for identification.

The private vendor information will remain encrypted in all license formats (whether readable or encrypted). The public vendor information will remain encrypted in encrypted licenses and readable in readable licenses, respectively.

<5.5Preview>