The Sentinel RMS License Manager enforces and manages licensing in multi-user environment. It keeps track of all the licenses and handles requests from network users who want to run your application, granting authorization to the requester to allow them to run the application, and denying requests when all licenses are in use. It is an integral component of the network licensing schemes that can be implemented with Sentinel RMS, namely server-locked licenses, site licenses and commuter licenses.
The License Manager usually runs on a computer within the network where users (clients) have installed the licensed application. See the diagram below:
Usually the licenses reside on the License Manager in a license file. On startup, the License Manager reads the licenses from the file and creates a license table. Otherwise, these are added dynamically to the License Manager. The dynamically added licenses are only available in the License Manager memory. Once the License Manager is stopped these licenses are lost.
You program your application to look for a License Manager with available licenses.
When the licensed application is run on a client, a request is sent to the License Manager for obtaining an authorization. The License Manager processes the request (including the task of authenticating the clients, if required) and returns the status to the client. The License Manager maintains each request separately, treating these authorizations as separate clients.
Figure 1: Multiple Clients Accessing the Sentinel RMS License Manager
Figure 2: Client Requesting for a Network License
Here are some quick facts about the RMS License Manager:
|Parameter||Sentinel RMS License Manager|
Operating Systems Supported
> Windows (32-bit and 64-bit) operating system
>UNIX-based (32-bit and 64-bit) operating systems, including Linux, Mac, Solaris Sparc, x86, AIX, and HPUX
>Linux ARM (32-bit [Hard Float/Soft Float] and 64-bit) operating system.
NOTE From Sentinel RMS v9.7 onwards, Linux ARM operating system is supported.
For specific versions, refer to the release notes or contact the Technical Support.
The default installation path on Windows is:
>Windows 32-bit - <Osdrive>:\Program Files\Common Files\Thales\Sentinel RMS License Manager\WinNT.
>Windows 64-bit - <Osdrive>:\Program Files(x86)\Common Files\Thales\Sentinel RMS License Manager\WinNT.
>On UNIX and Linux ARM operating systems, you can place the License Manager executable (lserv) at any chosen location.
UDP (User Datagram Protocol) that can support both IPv4 and IPv6 addresses.
NOTE The IPv6 protocol is not supported for Linux ARM OS.
A client can contact the License Manager using the IPv4 or IPv6 communication protocol. When the License Manager is hosted on a dual stack system, both IPv4 and IPv6 clients can communicate with it, however, not all combinations are supported (see the illustration below for more information).
|Network Port (default)||
NOTE Sentinel RMS License Manager uses port number 5093 and 5099. Make sure these ports are not blocked by a firewall. Otherwise, it may result in unexpected behavior.
Broadcasts within a subnet. Directed calls can access License Manager across subnets.
NOTE Sentinel RMS is an enterprise-level product functioning within an intranet that is not publically exposed. It is the responsibility of the system administrator on the customer’s site to ensure that the RMS License Manager is set up on a system that is not public. Thales cannot control this setup.
The License Managers may exist on different platforms than the clients running the licensed application. For example, a License Manager running on UNIX may administer Windows clients.
The License Manager provides backward compatibility to previous version clients as well, as shown in the version compatibility matrix below.
|For information about configuring the License Manager (like error and transaction logging and tracing) and License Manager utilities (such as lslic, WlmAdmin, WRlfTool) refer to the Sentinel RMS SDK System Administrator Guide. The system administrators, who will be deploying and administering the License Managers in a network, will require this document.|
|Provides License Manager redundancy for up to 11 License Managers.
For information about the redundant License Managers see "Redundant License Managers".
For information about customizing the License Manager see "Customization Features" in the Sentinel RMS SDK API Reference Guide.
Starting RMS 9.8.1, the industry-standard RSA algorithm is used to secure the RMS License Manager communication by default. Prior to RMS 9.8.1, a proprietary encryption algorithm was used for message encryption. In case, you still choose to use the proprietary encryption algorithm, you will need to obtain a separate add-on component called the License Manager Compatibility-Mode Library from Technical Support and follow the guidelines on using it.
See Also: License Loading Behavior on RMS License Manager Restart
The License Manager Compatibility-Mode Library is available only in DLL/shared library formats and is consumed by the licensing library on run-time only.
If you want to use the License Manager Compatibility-Mode Library, overriding the default RSA-based client-RMS License Manager communication, you need to follow the guidelines below:
>When using the static licensing library: Place the License Manager Compatibility-Mode Library at the same location as the licensed application.
>When using the dynamic licensing library: Place the License Manager Compatibility-Mode Library at the same location as the licensing library.
The licensed application will communicate with RMS License Manager using the proprietary encryption algorithm.
With the new encryption algorithm in place, now when the v9.8.1 (or later) RMS License Manager is restarted, additional tasks related to key-exchange are performed by the running licensed application. During this interval, the licensed application attempting to contact the License Manager (such as for automatic renewal calls via auto-timer), may return with error 210133 (SNTL_RESOURCE_LOCK_FAILURE). To overcome this, try calling the licensing API again after few seconds.