A License Manager program need not run on a file server system or any specific hardware server. It can be installed and run on any operating system recommended by your software vendor.
The License Manager can be installed even on a computer that is used to run one of the licensed applications. The application running on a client machine can choose any available License Manager with a valid license code for that client.
>On Windows, you can install the Sentinel RMS License Manager using the installer (provided by your software vendor). On UNIX, you can share the License Manager executable (lserv) available in the /bin directory.
>If you already have an older version of the Sentinel RMS License Manager installed on your system, upgrade to the latest version.
>Administrator or root privileges are required to install and run the RMS License Manager.
>By default, the License Manager is installed at the following location:
•On Windows: <OSDrive>:\Program Files\Common Files\Thales. You can change this when prompted to do so during the installation process.
•On UNIX and Linux ARM, you can place the License Manager executable (lserv) at any desired location.
Here are few recommendation that you may find helpful while setting up the RMS License Manager:.
>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.
>Sentinel RMS does not support servers with numeric host names. The License Manager may not start on such machines due to external dependencies.
>The machines on which License Managers run should use static IP addresses rather than dynamically allocated IP addresses (DHCP). In fact, redundant License Manager computers must use static IP addresses (Refer to: Requirements and Recommendations for Setting up Redundant License Managers).
>The RMS License Manager supports UDP (User Datagram Protocol) that supports IPv4 and IPv6 addresses. This means that 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 (refer to the following illustration for more information).
License Manager Host Protocol
|Client Side Protocol
>Client computers should directly contact the License Manager that services the licenses used by that client. The LSHOST and LSFORCEHOST environment variables or the lshost file can be used to do this.
>Client computers should contain a 'hosts' file that maps IP addresses to the host names of the computers on which the License Manager runs. This speeds up the process of contacting those License Managers.
•For some supported versions of Windows, this file may be located at: <rootdir>:\Windows\system32\drivers\etc The file itself contains instructions on entry format.
•On UNIX, this file may be located in the /etc directory.
NOTE The License Manager can communicate over a single IP address only on a multi-home PC. You do not have the choice of specifying any particular IP address for use by the License Manager. If the IP address to which the License Manager is bound becomes unavailable for any reason, then the License Manager needs to be restarted to allow using any other IP address on the system.
For successful communication between network clients and License Manager:
> The MTU value should be set to 1474 or above.
>For larger packets having size larger than MTU size, packet fragmentation should be allowed.
If you experience communication problems, you may diagnose your network using the following command:
•Prior to RMS SDK v8.4.1: ping –l 1500 <machine -name>
•Post RMS SDK v8.4.1: ping –l 7554 <machine -name>
>Restart the License Manager in the case the time zone changes.
To check the presence of the License Manager:
>On Windows, look for the Sentinel RMS License Manager entry in the list of the services installed on the system.
>On UNIX and Linux ARM, use the ps -ef|grep lserv command.
If an exception for Sentinel RMS License Manager is not under system Firewall exceptions, the communication between the clients requesting licenses and the License Manager will not take place.
>On Windows, by default, the installer adds an entry for Sentinel RMS License Manager. If you change this default addition during the installation, you will need to manually allow it.
>On UNIX and Linux ARM, you need to allow the 5093 (default port) as the trusted port for the RMS License Manager . The underlying protocol used is UDP.