Sentinel LDK-based Solution
The following diagram provides a high-level view of the Sentinel LDK-based solution:
Customer and Vendor Components
The table below lists the components that are used either at the vendor's site or redistributed to customers:
Component | Description | Deployment |
---|---|---|
Sentinel LDK Vendor Suite |
Contains all the programs required to implement protection and licensing such as Sentinel LDK Envelope, Sentinel Licensing API, and Sentinel LDK ToolBox. |
SDK to be installed on your (vendor's) end |
Protected Application with Sentinel Protection Keys |
Your software is distributed with Sentinel protection keys: >Sentinel HL: The hardware keys connect to the end users’ computers. Most times, it is possible to use these keys while installing no additional support software. >Sentinel SL: The software-based keys that exist in the secure storage of a specific computer. Sentinel SL keys provide the same functionality as Sentinel HL keys, without requiring physical distribution. |
Customer's environment depending upon standalone or network licensing. With standalone licensing, the Sentinel protection key exists on the same system where the protected application is installed. With network licensing the protected application and Sentinel protection key exist on separate systems. |
Redistributables |
The protected application is deployed in the customer's environment with redistributables such as: >Sentinel LDK Run time Environment (RTE): Enables communication between a Sentinel protection key and a protected application. The Run-time Environment also contains: •License Manager enables the protected application to locate and query the protection key that provides licensing authorization to operate. •Sentinel Admin Control Center (ACC) is a customizable, Web-based, end-user utility that enables centralized administration of License Managers and Sentinel protection keys. >Sentinel Remote Update System (RUS): Utility that enables licenses in deployed Sentinel protection keys to be securely, remotely updated, or the contents of the keys to be modified. |
Redistributables with the protected application in the end user's environment |
To learn more about the Sentinel LDK components, refer to the Sentinel LDK Software Protection and Licensing Guide.
Back-End Components
The table below lists the back-end components of the Sentinel LDK-based solution:
Component | Description | Deployment |
---|---|---|
Sentinel EMS |
Web-based license and entitlement management system that can simplify licensing fulfillment and activation workflows, automate back office processes and provide several useful reports. The Sentinel EMS web front-end comprises the following portals: >Vendor Portal: Authorized users in your organization access the Vendor Portal for defining product catalogs, and managing customers, entitlements, and downloads. >Customer Portal: Your customers log on to the Customer Portal to activate licenses and to view profile information. However, this portal for Sentinel LDK is to be added in the upcoming releases. Sentinel EMS also provides a set of REST API for integrating the entitlement management functions with external IT systems, such as ERP and CRM. |
|
Sentinel Connect | A Sentinel cloud-based component for seamless connection of Sentinel EMS to business applications in your back end. | Deployed and managed by Thales |
Thales Server |
Used for post-installation tasks such as introducing your Batch Code to Sentinel LDK components and downloading your vendor-specific libraries such as ToolBox library and licensing API libraries. |