KickStart (Quick-delivery Grace)
| Sentinel LDK Functionality | Grants a grace period to use software until key is delivered |
| Software Distribution Method |
>Physical package >Electronic distribution |
| Applicable Key Types |
>All Sentinel HL keys except Sentinel HL Basic >Sentinel SL (including CL) |
| Protection Method |
>Envelope-based automatic implementation >API-based automatic implementation |
Description
Locking a license to a Sentinel HL key provides a higher level of security than locking to a Sentinel SL key, but delivery of the Sentinel HL key to an end user can take time. This model enables you to electronically supply your software with a quick-delivery license locked to a Sentinel SL (software) key (“KickStart license”) as soon as an order is processed. For increased protection, you may choose to limit some software functions in the KickStart license.
The KickStart license can be used as part of a two-phased sales model:
>Phase 1: The end user purchases your software, and a 30-day KickStart license with limited functionality is supplied electronically.
NOTE The KickStart license is typically defined for a period of up to 90 days.
>Phase 2: The Sentinel HL key, programmed with the full license (the “final” license), is delivered within 30 days. The end user replaces the KickStart license with the full license
The KickStart license also serves as a super-distribution mechanism, since it will run for the grace period on any computer on which it is installed.
Implementation
1.Determine which global Feature ID you will use for the KickStart license.
2.Select the software functions that you want to include only in the full license, and determine by which Feature IDs each function will be identified.
3.Select a protection method and do one of the following:
For Envelope-based automatic implementation:
1.Determine which global Feature ID you will use for the full license.
2.Create two executable files, one with limited functionality for the KickStart license, and the other with full functionality for the full license.
3.Envelope each executable file separately, using the global Feature IDs you defined for the KickStart and full licenses respectively.
For API-based automatic implementation:
1.In your code, insert a Sentinel Licensing API Login call to the global Feature ID for the KickStart license.
2.In your code, for each software function you want to include only in the full license, insert Sentinel Licensing API Login calls to the appropriate Feature IDs.
In Sentinel LDK-EMS:
1.Create a Product that includes the global Feature ID for the KickStart license.
2.Select the
3.Distribute your software with Sentinel LDK Run-time Environment. Your software can run for a grace period of 30 days and can be installed on any other computer, for a 30‑day period, as a super-distribution mechanism.
4.Create a Product that includes the full license Feature IDs.
5.Define appropriate license terms for each Feature.
NOTE If the full license is based on a metered licensing model, metering will commence only when the full license is activated and not during the grace period.
6.Distribute your software with a Sentinel protection key programmed with the full license.