Comparison Between Sentinel LDK-EMS and Sentinel EMS

Sentinel LDK is available with your choice of two different entitlement management systems:

>Sentinel EMS is an enterprise-level system that integrates with Sentinel LDK. In addition to supporting Sentinel LDK, Sentinel EMS supports multiple enforcement types, including custom and third-party enforcements. Sentinel EMS is hosted on Thales servers, where it is enhanced continuously with improvements and updates. Sentinel EMS provides an advanced user interface and REST API to manage resources.

>Sentinel LDK-EMS is a legacy entitlement management system for Sentinel LDK. Sentinel LDK-EMS provides a user interface and REST API to manage resources.

TIP   To learn about the tools that can help you migrate from Sentinel LDK-EMS to Sentinel EMS, see Migration from Sentinel LDK-EMS to Sentinel EMS.

Terminology Comparison

Sentinel LDK-EMS	Sentinel EMS	Description of Term
Batch Code What is a batch code? A batch code is a unique character string that represents a vendor code. The batch code is used in defining features, products, and orders. It is also used for ordering Sentinel protection keys. With Sentinel HL keys, the code is printed on the Sentinel HL key label.	Namespace Batch Code is mapped with Namespace. When a Batch Code is assigned to a vendor, a namespace with the same name is created in Sentinel EMS. A namespace is also: >Used to segregate data in the Sentinel LDK-EMS database. >Associated with a Market Group. A market group defines data access control for a group of users who share common characteristics, such as geographical locations or business units. For more details, see Namespaces and Market Groups .	Unique character string that represents a vendor code. If you are migrating from Sentinel LDK-EMS, see Additional migration and Sentinel LDK Wrapper considerations.
Contact For details, see Sentinel LDK-EMS User Guide.	User NOTE   Sentinel EMS users are known "vendor users". For details, see Sentinel EMS User Guide for Sentinel LDK.	An end user, or an individual who serves as the single point of communication on behalf of a customer. For example, someone that purchases and maintains licenses on behalf of the employees in a company.
CRM ID	Ref ID	Unique identifier for the customer in the vendor's customer relationship management system. See also: Customers During migration from Sentinel LDK-EMS to Sentinel EMS, the CRM ID value is mapped as follows: >For customers, CRM ID is mapped to Ref ID (refId1 in the Sentinel EMS REST API). >For channel partners, CRM ID is mapped to Ref ID 2 (refId2 in the Sentinel EMS REST API). The maximum number of characters for Ref ID* is 100. If the CRM ID prior to migration exceeds 100 characters, the remaining characters are truncated.
Feature ID	Feature Identifier	A functional component in your software application that can be licensed independently. A feature can range from specific functionality, such as Print or Export, to a module, or even to an entire application.
License Type	License Model	Licensing options. For a complete list of the available options, see Licensing Options.
Produce an entitlement	Mark an entitlement as Complete	Terms used for generating an entitlement.
Product ID	Product Identifier	The numeric identifier for the product. In Sentinel LDK-EMS, the product ID must be unique for the batch code. In Sentinel EMS, the product identifier can be duplicated, for example, to create a "modification product"
Product Key	EID (Entitlement ID)	The identifier that is used for logging on to the Customer Portal to view or activate the Products in an entitlement. In Sentinel LDK-EMS, product key is set at the entitlement level—not at the product level. In Sentinel EMS, product key is generated at the line-item level in a product, which is different from the Sentinel LDK-EMS implementation. (A line item refers to a product in the list of products in an entitlement.)
Specify at entitlement time	Define in Entitlement or Allow overwrite	Enables you to set various attributes when creating an entitlement instead of when creating a Product.
User For details, see Sentinel LDK-EMS User Guide	Vendor User For details, see Sentinel EMS User Guide for Sentinel LDK.	A software vendor employee who is responsible for performing various entitlement-related tasks in Sentinel LDK EMS or Sentinel EMS.

Sentinel LDK Master License and Master Key

Sentinel LDK-EMS  (on-premises)	Sentinel LDK-EMS  (hosted by Thales)	Sentinel EMS (hosted by Thales)
Master key and Master license
>The Sentinel LDK Master License is located on the Master key. >The Master key must be connected to the Sentinel LDK-EMS machine when generating licenses. >The Master tab in Sentinel LDK-EMS can be used to view and update the license modules in the Sentinel LDK Master License.	>The Sentinel LDK Master License and its license modules are maintained by Thales. >The Master key is not used and should be stored in a secure location. >The Master tab in Sentinel LDK-EMS can be used to view the license modules in the Sentinel LDK Master License, which is maintained by Thales.	>The Sentinel LDK Master License and its license modules are maintained by Thales. >The Master key is not used and should be stored in a secure location.
Batch Codes / Namespaces
You must log in to Sentinel LDK-EMS using Sentinel Master Wizard to "introduce" your Batch Code on Sentinel LDK-EMS. This enables Sentinel LDK-EMS to recognize the Batch Code and perform actions for that Batch Code. During the introduction process, you download vendor-specific APIs and the vendor library from Thales servers. These files are used to protect your licensed application.	You must log in to Sentinel LDK-EMS using Sentinel Master Wizard to "introduce" your Batch Code on Sentinel LDK-EMS. This enables Sentinel LDK-EMS to recognize the Batch Code and perform actions for that Batch Code. During the introduction process, you download vendor-specific APIs and the vendor library from Thales servers. These files are used to protect your licensed application.	Logging in to Sentinel EMS using Sentinel Master Wizard is not required. Thales handles Batch Code (Namespace) introduction for you. You use Sentinel Master Wizard to perform other required functions, such as downloading the vendor-specific APIs and the vendor library from Thales servers. These files are used to protect your licensed application.

Roles

The role assigned to each user determines the functions that the user is authorized to perform in Sentinel EMS or Sentinel LDK-EMS. When a user logs on, only the relevant function groups are available to the user, according to the user's assigned roles.

In Sentinel LDK-EMS, you can assign users to pre-defined, out-of-the-box roles. For details, see the Sentinel LDK Software Protection and Licensing Guide. For implementation details, see the Sentinel LDK–EMS User Guide.

In Sentinel EMS, you create roles as needed and associate them with users. For implementation details, see the Sentinel EMS User Guide for Sentinel LDK.

Sentinel LDK-EMS—Out-Of-The-Box Roles	Sentinel EMS—How to Reproduce Sentinel LDK-EMS Roles
Batch Code Admin	>User Type: Standard >Associations: User must be associated with the relevant market group >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Customer Management (VEAD) •Channel Partner Management (VEAD) •Entitlement Management (VEAD) •Activation Management (VEAD) •Report Management (V) •Download Management (VEAD) •License Model Management (VEAD) •Catalog (Namespace) (VEAD)
Customer Services	>User Type: Standard >Associations: User must be associated with the relevant market group >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Customer management (VEAD) •Channel partner management (VEAD) •Entitlement management (V) •Activation management (VEAD)
Development	N/A. This role is not supported in Sentinel EMS.
Entitlement Manager	User Type: Standard >Associations: User must be associated with the relevant market group >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Customer management (VEAD) •Channel partner management (VEAD) •Entitlement management (VEAD)
Product Manager	>User Type: Standard >Associations: User must be associated with the relevant namespace >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Catalog (Namespace) management for all relevant namespaces (VEAD)
Production	>User Type: Standard >Associations: User must be associated with the relevant market group >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Entitlement management (V) •Activation management (VEAD)
Report Generation	>User Type: Standard >Role Permissions (View/Edit/Add/Delete Access—VEAD): •Report management (V)
Super User	N/A. To assign "super user" privileges to a user, associate that user with the equivalent of Batch Code Admin privileges for all namespaces.

User ID

User ID is used in both Sentinel LDK-EMS and Sentinel EMS for identification and login purposes. The main difference is the number of supported characters.

Sentinel LDK-EMS	Sentinel EMS
User ID: 1-30 characters	User Identifier: 6-100 characters (for Single sign-on (SSO): 3-100 characters)

NOTE   When migrating from Sentinel LDK-EMS to Sentinel EMS, ensure that the User ID for every user contains at least six characters.

Licensing Options

Licensing options are similar for both Sentinel EMS and Sentinel LDK-EMS, with an additional license option for Sentinel EMS. You assign a license model and license terms to a Feature when you add the Feature to a Product, or when adding the Product to an entitlement, if defined as such.

Sentinel LDK-EMS—License Types	Sentinel EMS—License Models
Execution Count. The maximum number of times the Feature may be used.	Execution Count. The maximum number of times the Feature may be used.
Expiration Date. The date on which the license for the Feature will expire.	Expiration Date. The date on which the license for the Feature will expire.
Perpetual. The license can be used an unlimited number of times and for an unlimited period of time.	Perpetual. The license can be used an unlimited number of times and for an unlimited period of time.
Time period. The number of days until the license expires. The number of days is counted from the date on which the licensed Feature is first used.	Time from First Use. The number of days until the license expires. The number of days is counted from the date on which the licensed Feature is first used.
N/A	Time from License Generation. This license type is valid for the number of days until the license expires. The number of days is counted from the date on which the license is generated.

Features

Sentinel LDK-EMS	Sentinel EMS
Created under the relevant Batch Code.	Created under the relevant namespace.
You associate and configure license terms for a Feature when associating the Feature with a Product or when creating an entitlement, depending on the Product settings.	You associate and configure license models for a Feature when associating the Feature with a Product or when creating an entitlement, depending on the Product settings. NOTE   If Sentinel EMS combines multiple enforcements (for example, Sentinel LDK and Sentinel RMS), the Associate License Models pane is visible when creating a Feature, but the license models are not relevant for Sentinel LDK and should be ignored.
Versions do not exist.	Versions are not supported. NOTE   If Sentinel EMS combines enforcements (for example, Sentinel LDK and Sentinel RMS), the version option is visible in Sentinel EMS, but the version number is not used when applied to a feature that is included in a Sentinel LDK product.

NOTE   When migrating from Sentinel LDK-EMS to Sentinel EMS, a feature description length that exceeds 510 characters is truncated.

Products

Sentinel LDK-EMS	Sentinel EMS
Created under the relevant Batch Code.	Created under the relevant namespace.
Default values for some options: >Rehost: Leave as is >Clone Protection: Platform Default	Default values for some options: >Rehost: Disable >Clone Protection: Only Platform Default is available NOTE   For vendors who migrate from Sentinel LDK-EMS, advanced clone protection schemes that were implemented for licenses continue to work as expected. You cannot change a clone protection scheme after migration.
Product type: >Base Product >Modification Product >Cancellation Product >Unlocked Product: •To create an Unlocked Product, you first create a Base Product and then create an unlocked variant of the Product. •You can generate a Bundle of one or more Unlocked Products for distribution using the Developer options.	Product type: A single, unified Product. >You can replicate the Modification-type Product used in Sentinel LDK-EMS by defining a new Product with the same Product Identifier as the original Product and updating the Product as needed. >Cancellation Products are not supported. You can remove all licenses from a key using the Remove licenses from keys before applying updates option when updating an entitlement. For details, see Sentinel EMS User Guide for Sentinel LDK. >Unlocked Product: •To create an Unlocked Product, you set the Unlocked from Device option when creating a Product. No variants are required. You can generate an Unlocked Product for distribution simply by creating and activating an entitlement that includes the Unlocked Product. If desired, you can also create a trialware package as described in the section on bundling unlocked products in the Sentinel LDK Software Protection and Licensing Guide. When migrating from Sentinel LDK-EMS to Sentinel EMS, product features are assigned an Apply License value. >Features in Base products: Overwrite >Features in Modification products: Add For details on the Apply License attribute, see Sentinel EMS User Guide for Sentinel LDK. See also: Additional migration and Sentinel LDK Wrapper considerations
Clone Protection: You can allow Sentinel LDK-EMS to automatically choose the best clone protection scheme for the scenario, or you can manually choose a pre-defined or custom clone protection scheme.	Clone Protection: You can allow Sentinel EMS to automatically choose the best clone protection scheme for the scenario, or you can manually choose an existing custom clone protection scheme. You can create custom clone protections schemes when adding or editing a product using the relevant product endpoint. For details, see Sentinel EMS REST API Guide. NOTE   For vendors who migrate from Sentinel LDK-EMS, advanced clone protection schemes that were implemented for licenses continue to be available for products marked as "Complete".
Product ID: When you first create a Product, the Product ID must be unique in the batch code. If you later create a Product based on that Product, such as a Modification Product or Cancellation Product, the same Product ID is used.	Product Identifier: Although you can potentially apply the same product identifier for multiple products, Thales recommends that for clarity and ease of use and maintenance that you apply a unique product identifier to every product.

Memory

Sentinel LDK-EMS	Sentinel EMS
Memory segments are used to segregate data between Products to avoid overlapping memory data when the same memory file is associated with multiple products.	When creating a Product, you can directly configure the offset and length of a memory file to segregate data between Products. Memory segments are not used.
Types of memory: >Dynamic: •Memory segments that contain memory data. >Default: •Memory segments that you define or load when creating a product. •File ID is hidden.	Types of memory: >User-created: •Memory files that can contain file-specific attributes such as reference IDs, as well as memory data. >Default: •Out-of-the-box memory files that are used as placeholders for text. You can add text when associating the memory file with a Product. •File ID is visible. You select the file ID when associating a memory file with a Product.
Multiple navigation levels require you to select the relevant memory type before you can choose a memory segment.	Unified list of all available memory files makes it easy to select the required memory file.
Both types of memory support text and hexadecimal data in the Sentinel LDK-EMS user interface.	Both types of memory support text data in the Sentinel EMS user interface.
When creating a Product, you can create and apply memory using Create New Memory > Action: Set/Overwrite/Delete. For details, see the sections on memory in the Sentinel LDK–EMS User Guide.	When creating a Product, you create and apply memory using Apply Memory: Add/Overwrite/Delete. For details, see the Apply Memory section in the Sentinel EMS User Guide for Sentinel LDK.

NOTE   When migrating from Sentinel LDK-EMS to Sentinel EMS, managing multiple memory segments using Sentinel LDK Wrapper is not supported.

Entitlements

Sentinel LDK-EMS	Sentinel EMS
Created under the relevant Batch Code.	Created under the relevant market group.
Types of entitlement: >Hardware Key >Product Key >Protection Key Update	Unified entitlement workflow for SL and HL keys for both new and updated licenses: >Based on locking types of associated Product >Number of activations is mapped with quantity
You can specify the Number of Product Keys to generate multiple Product Keys for distribution. (This is equivalent to EIDs in Sentinel EMS.)	You can use batch entitlements to generate multiple EIDs for distribution. (This is equivalent to Product Keys in Sentinel LDK-EMS.)
Adding Comments: You can add comments by clicking the Add Entitlement Notes link and entering a string in the Comments box.	Adding Comments: You can add comments by creating a custom attribute of type string for entitlements. You create custom attributes from the Configuration > Custom Attributes page. The attribute will be accessible under Additional Attributes on the Add Entitlement page. NOTE   If you migrate from Sentinel LDK-EMS, your comments will automatically be mapped to a custom attribute of your choice during the migration process.
Test Entitlement mode is not supported.	Supports Test Entitlement mode to confirm that an entitlement works correctly.
Batch Entitlement mode is not supported.	Supports Batch Entitlement mode, which lets you create large batches of entitlements, eliminating the need for small and low-volume production cycles.

Reports

Sentinel LDK-EMS

Sentinel EMS

Sentinel LDK-EMS supports specific pre-defined reports and enables you to run and distribute reports automatically using the Scheduled Reports functionality. For details, see the Reports section in the Sentinel LDK-EMS User Guide.

Sentinel EMS supports specific pre-defined reports, custom reports, and data export reports, but does not support the following reports and functionality that are available in Sentinel LDK-EMS: >Reports: •Total Entitlement Utilization •License Expiration Report >Scheduled Reports functionality If you are migrating from Sentinel LDK-EMS to Sentinel EMS, you can contact Thales Customer Support for assistance in adding these reports and scheduling functionality using Custom Reports. If you are new to Sentinel EMS and want to use Custom Reports, contact Thales Professional Services for assistance. For more information on working with the various reports in Sentinel EMS, see the Reports section in the Sentinel EMS User Guide for Sentinel LDK.

License Activation in the Vendor Portal

Sentinel LDK-EMS	Sentinel EMS
All Products in the entitlement are activated. Product-level (line-item) activation is not supported.	>You can activate an entire entitlement or selected line items (Product-level activation). Each line item is activated in its entirety. >The Fixed activation method is supported with a fixed quantity of 1.

Customer Portal

Sentinel LDK-EMS	Sentinel EMS
Login You log in using a product key (entitlement-level PKID).	Login You can log in using: > EID (entitlement ID) >PKID (line-item-level product key ID) >email address >vendor credentials
Applying Updates You can apply all outstanding updates to all protection keys connected to the machine used to access the Customer Portal. In the Customer Portal URL, you can also select the License Update tab and click the Update Licenses button to automatically check for and install any licenses that are available for the connected keys.	Applying Updates You apply updates by activating entitlements. You can also click the Update Licenses button in the login screen to automatically check for and install any licenses that are available for the connected keys.
For applying updates, see this note.

Customers

Sentinel LDK-EMS	Sentinel EMS
A customer can be associated with one or all Batch Codes.	A customer can be associated with a single market group.
Types of customers: >Company. Can have one or more contacts. >Individual. No contacts.	Type of customer: >Single, unified customer type for both companies and individuals. >Users (formerly known as "contacts") are optional, with the exception of user-based licensing, which requires at least one user. For details, see Sentinel EMS User Guide for Sentinel LDK.
When migrating from Sentinel LDK-EMS: > Both types of Sentinel LDK-EMS customers are mapped to the single customer type in Sentinel EMS. >The CRM ID value from Sentinel LDK-EMS is mapped to Ref ID 1. Before migration, it is important to take into consideration that the maximum number of characters for CRM ID is 255 (Sentinel LDK-EMS), whereas the maximum number of characters for Ref ID 1 is 100 (Sentinel EMS). The value is truncated if the CRM ID contains more than 100 characters. If needed, consider updating the CRM ID prior to migration to limit the number of characters to 100 or less.

Channel Partners

Sentinel LDK-EMS	Sentinel EMS
A channel partner can be associated with one or all Batch Codes.	A single channel partner user can be associated with multiple market groups.
Types of channel partners: >Company. Can have one or more contacts. >Individual. No contacts.	Type of channel partner: >Single, unified channel partner type for both companies and individuals. >Contacts are not supported.
Advanced channel partner functionality is supported. For details, see Channel Partners in the Sentinel LDK Software Protection and Licensing Guide.	Advanced channel partner functionality is not currently supported.
When migrating from Sentinel LDK-EMS: > Both types of Sentinel LDK-EMS channel partners are mapped to the single channel partner type in Sentinel EMS. >The CRM ID value from Sentinel LDK-EMS is mapped to Ref ID 1. Before migration, it is important to take into consideration that the maximum number of characters for CRM ID is 255 (Sentinel LDK-EMS), whereas the maximum number of characters for Ref ID 1 is 100 (Sentinel EMS). During migration, the value is truncated if the CRM ID contains more than 100 characters. If needed, consider updating the CRM ID prior to migration to limit the number of characters to 100 or less. >When using the Sentinel LDK Wrapper, channel partner users may be duplicated as vendor users. You can delete any channel partners that are erroneously added as vendor users in Sentinel EMS. For details, see Sentinel EMS User Guide for Sentinel LDK.

Web Services - REST API

Sentinel LDK-EMS and Sentinel EMS each have their own REST API. Although the functionality is similar, the format and structure are different.

When you migrate from Sentinel LDK-EMS to Sentinel EMS, Thales provides a Sentinel LDK Wrapper, which handles the conversion from the Sentinel LDK-EMS Web Services to the Sentinel EMS REST APIs. This ensures a seamless transition for your deployed licensed software.

Here are some useful links that will assist you in the migration process:

>Sentinel LDK Migration Checkup Tool User Guide

>Sentinel LDK Wrapper

>Sentinel LDK-EMS Web Services Guide

>Sentinel EMS REST API Reference

>Sentinel EMS REST API Guide

Developer Options

Sentinel LDK-EMS	Sentinel EMS
You use the Developer tab to perform the various tasks described in this table.	The Developer tab does not exist in Sentinel EMS. The functionality in this tab is not relevant or is handled differently in Sentinel EMS as described in this table.
Bundle Unlocked Products for distribution.	Bundling Unlocked Products is not required. You can generate an Unlocked Product for distribution simply by creating and activating an entitlement that includes the Unlocked Product. If desired, you can also create a trialware package as described in the section on bundling unlocked products in the Sentinel LDK Software Protection and Licensing Guide.
Export catalog definitions.	You can export catalog definitions directly from the relevant entity in Sentinel EMS. For details, see the Sentinel EMS User Guide for Sentinel LDK.
Generate a Sentinel Run-time Environment (RTE) Installer. NOTE   This functionality is now provided by the Sentinel LDK Master Wizard and is no longer available from the Developer tab in Sentinel LDK 8.4 and later.	Sentinel Run-time Environment (RTE) Installer generation is provided by the Sentinel LDK Master Wizard.
You can use the Sentinel RUS Generator tool to generate a branded RUS utility that is associated with your batch code. For details, see Sentinel RUS Generator and the Sentinel LDK Software Protection and Licensing Guide.

V2C and V2CP Files

Sentinel LDK-EMS	Sentinel EMS
Vendor-to-Customer Files Sentinel LDK-EMS generates either V2C files or V2CP files depending on the function being performed.	Vendor-to-Customer Files Sentinel EMS generates only V2CP files, which include all of the content of the relevant V2C files.

Migration from Sentinel LDK-EMS to Sentinel EMS

Your Thales representative will help you plan your migration to Sentinel EMS. During this process, you may be asked to provide information that will assist in determining what you need to do prior to migration.

After the migration, you will use Sentinel EMS and Sentinel EMS REST API instead of Sentinel LDK-EMS, which will no longer be available. To learn more about Sentinel EMS, see Sentinel EMS User Guide for Sentinel LDK and Sentinel EMS REST API Reference.

Thales understands that you require time to learn to use and apply the Sentinel EMS REST API to your applications. If needed, Sentinel LDK Wrapper can help to bridge the gap between Sentinel LDK-EMS Web Services and Sentinel EMS REST API until you are completely ready to switch to using Sentinel EMS REST API. Using Sentinel LDK Wrapper ensures that your deployed licensed software and Sentinel LDK-EMS Web Service integration with your ERP system will continue to work as is.

When you are comfortable with Sentinel EMS, Thales recommends replacing Sentinel LDK-EMS Web Service integration in your ERP system with Sentinel EMS integration. This change will enable you to take advantage of all the functionalities and flows that Sentinel EMS offers. At the same time, you can continue using Sentinel LDK Wrapper for your deployed licensed software.

To ease the migration process from Sentinel LDK-EMS to Sentinel EMS, Thales provides the following tools:

>Sentinel LDK Migration Checkup Tool

>Sentinel LDK Wrapper

Sentinel LDK Migration Checkup Tool

Sentinel LDK Migration Checkup Tool is a command-line utility for vendors who currently host their customers' cloud licenses on their own license manager service (LMS) database and want to migrate to those licenses and client identities to Sentinel EMS with Sentinel LDK CL Service, both of which are hosted by Thales.

Purpose: Use this tool to check migration readiness and to locate issues that need to be handled prior to migration.

Relevant for: Vendors that currently use Sentinel LDK-EMS.

Prerequisites and instructions: See Sentinel LDK Migration Checkup Tool User Guide.

Sentinel LDK Wrapper

Sentinel LDK Wrapper automatically translates Sentinel LDK-EMS Web Service calls and passes the responses to Sentinel EMS. This enables vendors that migrate from Sentinel LDK-EMS to Sentinel EMS to continue using pre-existing Sentinel LDK-EMS Web Service calls in their licensed software and ERP systems after the migration. By bridging the gap between Sentinel LDK-EMS Web Services and Sentinel EMS, vendors can transition to Sentinel EMS while ensuring a seamless user experience for their customers and vendor users. Customers can continue using deployed licensed software without any updates, and vendor users can still perform tasks using Sentinel EMS Web Services.

For more information and to determine if you need to use Sentinel LDK Wrapper, contact your Thales representative. The information below provides general guidelines on using Sentinel LDK Wrapper.

Purpose: Enable vendors to migrate from Sentinel LDK-EMS to Sentinel EMS smoothly and quickly. After migrating to Sentinel EMS:

>A vendor's customers can continue using deployed licensed software that integrates Sentinel LDK-EMS Web Services.

>Vendor users, such as order takers and other ERP users, can continue using their existing ERP system, which is integrated with Sentinel LDK-EMS Web Services.

By keeping existing integrations intact and operational, vendors can allocate the necessary time to upgrade to the Sentinel EMS REST API and implement it effectively.

Relevant for: Vendors that currently use Sentinel LDK-EMS Web Services to do any of the following:

> activate licenses and install license updates

>automate the creation and management of entitlements from their ERP system

>manage catalog elements, such as products and features

Prerequisites:

>Sentinel LDK-EMS 10.x (latest version) must be available.

>Vendors who currently host their customers' cloud licenses on their own license manager service (LMS) database and want to migrate to those licenses and client identities to Sentinel EMS with Sentinel LDK CL Service must run the Sentinel LDK Migration Checkup Tool, implement any required changes, and share the results with their Thales representative.

>Vendors who currently host their customers' cloud licenses on their own license manager service (LMS) database must have an SSL certificate for their existing website.

>Deployed licensed software must include at minimum:

• Sentinel LDK-EMS Web Services 8.0 or later. (The wrapper "wraps" the Sentinel LDK-EMS Web Service calls in the licensed software.)

•Sentinel Run-time Environment (RTE) 7.8 or later. (Relevant if the licensed software requires Sentinel Run-time Environment. For details, see Sentinel LDK Software Protection and Licensing Guide for Sentinel LDK-EMS.)

How does it work?

Sentinel LDK Wrapper automatically translates your licensed software's Sentinel LDK-EMS web service calls and passes the responses to Sentinel EMS. This enables your existing licensed software and ERP system continue to work as is.

To implement Sentinel LDK Wrapper:

1.Together with your Thales representative, determine if Sentinel LDK Wrapper is needed. If so, determine if any changes are required. For example, you may need to upgrade your Sentinel Run-time Environment to the latest version. Your Thales representative will provide instructions as needed. Implement any required changes prior to migration.

2.Your Thales representative migrates your data to Sentinel EMS and enables Sentinel LDK Wrapper on your Sentinel EMS instance.

3.Test the implementation on your new development Sentinel EMS instance. For example, you might make a copy of your deployed licensed software to use as a sample application for testing purposes. (Thales provides you with a development instance for validation in addition to staging and production instances.) Ensure that your sample application uses the new Sentinel EMS URL. Validate and implement fixes as needed.

4.Your Thales representative migrates your data to the production instance of Sentinel EMS and enables Sentinel LDK Wrapper on your Sentinel EMS instance.

If you are migrating from an on-premises instance of Sentinel LDK-EMS, make sure to reroute any custom domain or sub-domain calls to the new Sentinel EMS domain and sub-domain. This enables the deployed licensed software to continue working as is. For custom root domain changes, this may require setting a proxy for Sentinel EMS.

That's it. Your customers and vendor users can continue working seamlessly, without interruptions, and you can start leveraging all the benefits that Sentinel EMS offers.

Sentinel LDK Wrapper flows:

The following flows describe how you might use Sentinel LDK Wrapper.

>Activation:

For the productKey value, use the entId or Order Number value, depending on where you retrieve the value from.

a.Log in using the product key:  https://<serviceURL>/ems/v<XX>/ws/loginByProductKey.ws

b.Activate (generate a license): https://<serviceURL>/ems/v<XX>/ws/productKey/<productKey>/activation.ws

>Downloading the V2CP file:

Add a call to your application to download the V2CP file.

>Installing Licenses:

Use the Sentinel Run-time (RTE) Installer API to install a license. For details, see Sentinel LDK RTE Installer API Reference.

Make sure to use a supported Sentinel Run-time Environment version as described in Prerequisites:.

>Checking for Updates:

a.Fetch the C2V file and check for pending updates: https://<serviceURL>/ems/v<XX>/ws/activation/target.ws

b.Use the Sentinel Run-time (RTE) Installer API to install a license. Make sure to use a supported Sentinel version as described in Prerequisites. For details, see Sentinel LDK RTE Installer API Reference.

What's not supported?

In most cases, Sentinel LDK Wrapper supports the conversion of all your Sentinel LDK-EMS Web Service calls. In some cases, especially if you are migrating from an older version of Sentinel LDK-EMS, your application may include calls to web services that are not relevant or supported in Sentinel EMS. The following describes some of these items.

>UI-only operations, such as burning a key. This is because Sentinel LDK Wrapper supports only Sentinel LDK-EMS Web Services.

>Items that are either not supported or are implemented differently in Sentinel EMS, such as:

•Advanced channel partner functionality. For details, see Channel Partners.

•Using V2C files. (V2C files should not be an issue if your deployed licensed software includes Sentinel Run-time Environment 7.8 or later, which supports the generation of V2CP files.) For more details, see V2C and V2CP Files.

•Generating a list of features and products (Export Definition) (v<XX>/ws/vendor/{vendorId}/exportDefinition.ws). For more details, see Developer Options.

•Bundling unlocked products (Bundle Unlocked) (v<XX>/ws/vendor/{vendorId}/bundleProvisional.ws?prodIds={prodIds}). For more details, see Products and Developer Options.

•Managing Cancellation products. For details, see Products.

•Managing multiple memory segments. For details, see Memory.

•When updating a protection key, the following actions are not supported: Format, ForceIntroduce, Disable, Fingerprint, Locate, ConvertV2CToExe (deprecated), and ClearTimeTamper.

•For the protection key entity, the following web services are not supported:

–v<XX>/ws/entitlement/{entId}/target.ws

–v<XX>/ws/productKey/{productKeyId}/target.ws

–v<XX>/ws/target/{protectionKeyId}/entitlement.ws

–v<XX>/ws/target/{protectionKeyId}.ws (GET, DELETE)

–v<XX>/ws/target/{protectionKeyId}/activation.ws?AID={AID}

•For the vendor entity, the following web services are not supported:

–v<XX>/ws/enforcement.ws?vendorId={vendorId}

–v<XX>/ws/enforcement/{enforcementId}/vendor.ws

–v<XX>/ws/vendor.ws?userId={userId}

•For the channel partner entity, the following web services are not supported:

–v<XX>/ws/contact/{contactId}.ws (GET, POST, DELETE)

–v<XX>/ws/contact/{contactId}.ws?firstName={firstName}&lastName={lastName}

For a list of the specific differences between Sentinel LDK-EMS and Sentinel EMS, review the sections above.

Additional migration and Sentinel LDK Wrapper considerations

>Integration with vendor ERP. If you create and manage entitlements from your ERP using Sentinel LDK-EMS Web Services, Thales recommends that you use Sentinel LDK Wrapper to manage your entitlements (orders). This is because Sentinel LDK Wrapper is designed to support Sentinel LDK-EMS Web Services, ensuring that critical information is added to Sentinel EMS as needed.

>Custom attributes.

•Sentinel LDK Wrapper generates custom attributes for items that cannot be mapped directly to Sentinel EMS. Do not delete these custom attributes because they are required by the wrapper. For example, Sentinel LDK Wrapper assigns a custom attribute to a "default contact" when more than one contact is associated.

•Order number. Sentinel LDK Wrapper automatically creates the "Order Number" custom attribute in Sentinel EMS and maps the entitlement ID (entId) value from Sentinel LDK-EMS to this attribute. "Order Number" is visible in the Sentinel EMS user interface and in the Sentinel EMS REST API response.

>Multiple, vendor-specific batch codes. (Relevant only for vendors with more than one batch code, excluding DEMOMA and DEMOMB) Whereas Sentinel LDK-EMS supports the use of multiple batch codes per customer, Sentinel EMS supports a single batch code per customer. In Sentinel EMS, a batch code is associated with (mapped to) a namespace, which, in turn, is associated with a market group. If you have multiple batch codes, you need to create a single market group in Sentinel EMS and include all relevant namespaces in that market group. Then you can associate each customer with the relevant market group. For details, see Sentinel EMS User Guide for Sentinel LDK.

>Maximum number of characters:

•CRM ID. (Relevant for customers and channel partners) If a customer or channel partner entity contains a CRM ID value, that value is mapped to Ref ID 1. If the CRM ID value exceeds 100 characters, the value is truncated in Sentinel EMS as Ref ID 1 supports a maximum of 100 characters. If needed, you may want to shorten the CRM ID value prior to migration.

•Ref ID 1 and Ref ID 2 (refId1 and refId2). (Relevant for products, features, entitlements, namespaces, and vendor users.) In Sentinel EMS, the maximum length for a Ref ID value is 100 characters versus 250 characters in Sentinel LDK-EMS. If the Ref ID value exceeds 100 characters, the value is truncated in Sentinel EMS. If needed, you may want to shorten the Ref ID value prior to migration.

•Description. (Relevant for features.) With the exception of features, the maximum length for a Description value is 510 characters in both Sentinel LDK-EMS and Sentinel EMS.

In Sentinel LDK-EMS, the maximum length for the Description value for features is 1024 characters. If a feature's Description value exceeds 510 characters, the value is truncated in Sentinel EMS. If needed, you may want to shorten the Description value prior to migration.

>Channel partner contact. Sometimes, channel partner contacts are duplicated in Sentinel EMS as vendor users, in addition to channel partner users. If this occurs, you can manually delete the vendor user using Sentinel EMS or Sentinel EMS REST API. For details, see Sentinel EMS User Guide for Sentinel LDK and Sentinel EMS REST API Reference.

>Unlocked products:

•Retrieving license models for unlocked products. Sentinel EMS does not differentiate between unlocked (bundled) products and other types of products. Therefore, if you need to retrieve a list of license models for unlocked products, use Sentinel LDK Wrapper. For details, see Sentinel LDK-EMS Web Services Guide.

•Checking in C2V files. C2V files for unlocked products do not need to be checked in.

>Retrieving activation input (activationInput and activationAttribute). Sentinel EMS' Get Activation API does not return activationInput and activationAttribute in the response. To retrieve this information, you can use Sentinel LDK Wrapper. For details, see Sentinel LDK-EMS Web Services Guide.

>Creating products:

•Setting the Apply License value. (Relevant for products and entitlements.) Sentinel EMS requires an Apply License value when creating a product. When using Sentinel LDK Wrapper:

–Base products are assigned the Overwrite value.

–Modification products are assigned the Add value.

For details, see Sentinel EMS User Guide for Sentinel LDK.

>New batch code. If you purchase or receive a new batch code after migration, contact your Thales representative to ensure that the new batch code is linked to your Sentinel LDK Wrapper.