Standalone Mode
You need a bundle of CA root certificates (cacert.pem) to facilitate SSL client authentication that can be downloaded from http://curl.haxx.se/ca/cacert.pem.
The cacert.pem file must be placed at one of the following locations:
>If the SCP_CONFIG_FILEPATH_<Vendor_Alias> environment variable is set, place it at the path mentioned in the environment variable.
>If the SCP_CONFIG_FILEPATH_<Vendor_Alias> environment variable is not set, place it at the location where the licensed application exists.
NOTE In the absence of cacert.pem file, the following error is thrown when the license application is executed: "Configuration supplied are invalid/incomplete".
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, the 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 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
|
|
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. |
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 |