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 requesters 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.
NOTE RMS does not support servers with numeric host names. The License Manager may not start on such machines due to external dependencies.
The License Manager usually runs on a computer within the network where users (clients) have installed the licensed application. See the diagram below:
Figure 1: Multiple Clients Accessing the Sentinel RMS License Manager
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 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 and 64-bit
>UNIX-based (32 and 64-bit) operating systems, including Linux, Macintosh, Solaris Sparc and x86, AIX, and HPUX
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\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.
•Windows 64-bit - <Osdrive>:\Program Files(x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.
On UNIX, you can place the License Manager executable (lserv) at any chosen location.
UDP (User Datagram Protocol) that can support both IPv4 and IPv6 addresses.
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.
|Network reach||Broadcasts within a subnet. Directed calls can access License Manager across subnets.|
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.
|Startup options||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's Guide. The system administrators, who will be deploying and administering the License Managers in a network, will require this document.|
|Failover support||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.