Subscription
| Sentinel LDK Functionality | Creates an unconditional license that can be updated remotely |
| Software Distribution Method |
>Physical package >Electronic distribution |
| Applicable Key Types |
>All Sentinel HL (Driverless configuration) keys except Sentinel HL Basic >Sentinel SL (including CL) |
| Protection Method |
>Envelope-based automatic implementation >API-based automatic implementation |
Description
The end user pays a monthly subscription fee that covers the initial software package plus periodical updates. If the end user does not renew the subscription, the basic package and all paid updates remain the property of the end user. New updates are not provided.
Implementation
1.Select the executable file that you want to license, and determine by which Feature ID it will be identified.
2.Select the protection method for your software:
•Envelope-based automatic implementation
Protect the executable file using Sentinel LDK Envelope, specifying its Feature ID.
•API-based automatic implementation
In your code, insert a Sentinel Licensing API Login call to the Feature ID.
3.In Sentinel EMS, create a Product that includes the Feature ID for your initial software and define a perpetual license for the Feature.
4.Create a component in your software that manages the installation of software updates, and assign it a Feature ID. Select and implement your protection method for that component (Sentinel LDK Envelope or Sentinel Licensing API-based).
5.In Sentinel EMS, create a Product that includes the Feature ID for the update-installation component and define an expiration date for that Feature.
6.Envelope your software for additional security (optional).
7.Distribute your software with the appropriate Sentinel protection key programmed with the license.
8.During the subscription period, send updates to the subscriber. The updates are handled by the update-installation component in your software. Optionally, use Sentinel LDK to encrypt the update files so that the Sentinel protection key is required to decrypt them.
9.Continue sending updates as long as the end user’s subscription is valid.
10.When the end user renews the subscription, update the expiration date for the update-installation component’s license.