Vendor-Level Implementation Summary

The following steps summarize the process of implementing the cloud licensing model.

1.Protect your applications using Sentinel LDK. Ensure that the Locking Type includes the option to use SL AdminMode keys.

2.Use Sentinel LDK-EMS or Sentinel License Generation API to generate an SL AdminMode license for each customer organization. Ensure that a Master key with the required modules is attached to the machine. If you are using License Generation API, ensure that the license definition includes the tag <cloud_licensing> with the value Yes. The license must allow concurrency. Specify the required number of network seats.

3.Set up a global license server machine that allows access via the Internet, and install each SL license in a separate SL key on the server.

4.For each unique end user, use Sentinel Admin Control Center to generate a client identity. Each client identity can be configured to allow access to a specific SL key on the license server. Each client identity is also configured whether to:

•Allow the user's machine to log in to a license on the SL key.

•Allow the user to detach a network seat from the key.

•Allow the user to install the client identity on multiple machines. (Only one of the machines can consume a network seat at any given moment.) If you limit the number of machines, the License Manager automatically registers each machine when first used and allows you to view and manage the list. If you allow unlimited machines, the machines are not tracked.

For more information, see Viewing and Managing Client Identities.

5.Copy the identity string from the client identity and provide it to the end user.

6.The end user installs the relevant protected application. The user registers their identity string on their machine using either Admin Control Center or a text editor. The user can register their identity string on multiple machines (up to the limit you specify).

7.The end user proceeds to execute the protected application. The application consumes a network seat from the vendor's license server machine.

The end user detaches a network seat from the license server machine to the local machine. The user can then proceed to execute the protected application offline.