Standalone Lease Mode

For standalone environments, the SCP-integrated Sentinel RMS libraries are provided (not the SCP installer). The API calls making use of SCP-integrated Sentinel RMS libraries are implemented within the application, thus integrating the SCP functionality with the application. This is similar to how the RMS License Manager capabilities are integrated with the application.

The topics included in this section are:

>Integration Notes

>Setting Trace Logs and Trace Levels in Standalone Mode

>Configure SCP

•By Using the SCP Configuration File

•By Using the RMS Unified APIs

>(Optional) Configure Proxy Settings

>Software And Services Evaluation Tool

Integration Notes

>If your application is intended to be run in standalone environments, you need to integrate SCP functionalities into the application by implementing Sentinel RMS API calls. For API details, refer to the Sentinel RMS API Reference Guide.

NOTE You can also use the sntl_lease_demo sample to understand the standalone application workflow in the lease deployment mode. For instructions on using the sample, refer to the Quick Start Guide - Cloud Served-Lease Standalone License Deployment Mode.

>The SCP configuration file should be placed in the same directory as the licensed application. Alternatively, you can use RMS Unified APIs to configure SCP.

>If you wish to place them in different directories, specify the configuration file path in the environment variable, SCP_CONFIG_FILEPATH_[vendor_alias]. SCP will then look for the configuration file at the path specified.

NOTE

The SCP_CONFIG_FILEPATH_[vendor_alias] environment variable (if defined) has higher precedence than the application directory.

The environment variable to pick the configuration file should be set under the system variables for the SCP service to run successfully.

>It is recommended to specify the trace log file and trace levels in the licensed application. This ensures the application execution activity is tracked and error logs are generated. These prove to be useful during troubleshooting in the event of any error.

>It is also recommended to call the sntl_licensing_get_info API with the syncLicenseJobInfo query type to obtain the status of the lease synchronization job. This query type helps to check whether leased licenses have been fetched to the standalone machine or not.

NOTE If the SCP configuration file is updated while SCP is running, the application restart is required to apply the updated settings.

Setting Trace Logs and Trace Levels in Standalone Mode

The log settings defined in the SCP configuration file are not applicable for the standalone mode. You need to use the sntl_licensing_configure Sentinel RMS API to configure logging. The attributes of this API are:

Atrribute	Possible Values
>SNTL_ATTR_CONFIG_TRACE_LEVEL	>SNTL_ATTR_CONFIG_TRACE_FUNCTION > SNTL_ATTR_CONFIG_TRACE_ERROR
>SNTL_ATTR_CONFIG_TRACE_WRITER_FILE

Atrribute

Possible Values

>SNTL_ATTR_CONFIG_TRACE_LEVEL

>SNTL_ATTR_CONFIG_TRACE_FUNCTION

> SNTL_ATTR_CONFIG_TRACE_ERROR

>SNTL_ATTR_CONFIG_TRACE_WRITER_FILE

For API details, refer to the Sentinel RMS API Reference Guide.

Configure SCP

Now you can configure the SCL processes using the RMS Unified APIs in addition to the SCP configuration file (only option available previously). By default, SCP is configured using the configuration file, which can be changed via SNTL_ATTR_CONFIG_SCP_USE_CONFIG_FILE attribute.

Available configuration options:

>By using the SCP configuration file

>By using the RMS Unified APIs

By Using the SCP Configuration File

Open the SCP configuration file available in the SCL Add-on package and modify the following mandatory elements:

Element	Description
Customer Id	Specify the ID of the customer defined in Sentinel EMS for whom licenses will be fetched by SCP. For example, if Customer ID in EMS is "Demo", you can modify the element like: <Customer id="Demo"/> TIP The Customer ID can be copied from EMS entitlement certificate emails received from EMS. SCP supports only one customer ID.
YPSaddress	Specify the URL of Directory Services (DS) which is received in emails from Thales. For example: https://demo-yps.com/YPServer
Fingerprint Friendly Name	Specify the fingerprint-friendly name that identifies the customer's machine where the application is running.

Element

Description

Customer Id

Specify the ID of the customer defined in Sentinel EMS for whom licenses will be fetched by SCP.

For example, if Customer ID in EMS is "Demo", you can modify the element like:

<Customer id="Demo"/>

TIP
The Customer ID can be copied from EMS entitlement certificate emails received from EMS. SCP supports only one customer ID.

YPSaddress

Specify the URL of Directory Services (DS) which is received in emails from Thales. For example:

https://demo-yps.com/YPServer

Fingerprint Friendly Name

Specify the fingerprint-friendly name that identifies the customer's machine where the application is running.

(Optional) Configure Proxy Settings

For the standalone lease deployment mode, the proxy settings are defined using the following options:

>SCP configuration file

>System settings (as defined in Internet Explorer)

By default, the system settings are used, but if defined, the configuration file settings take the precedence.

By Using the RMS Unified API

You can choose to configure SCP through the RMS Unified APIs available for the following programming languages:

Programming Language	API
C	sntl_licensing_configure
Java	configure
.NET	configure

Software And Services Evaluation Tool

A new tool "SoftwareAndServicesEvaluationTool" for Windows is introduced to quickly demo/evaluate the standalone deployment and consumption of standalone lease licenses. You can find it under the Samples directory.