Interfacing the Sentinel RMS license manager - KB4001e - OpenLM Software License Management
Israel +972 4 6308447         USA +1 619 831 0029              JAPAN +81 505 893 6263 担当:萩原

Interfacing the Sentinel RMS license manager – KB4001e

You are here:
< All Topics

This document describes the steps required to interface OpenLM with the Sentinel RMS license manager in order to monitor license usage and obtain license statistics.

 

1. Requirements

To query the Sentinel RMS license manager:

  1. OpenLM Server v4.3 or higher must be installed on a machine in your organization.
  2. (Optional) OpenLM Broker v4.x or higher must be installed on the Sentinel RMS machine in order to take advantage of additional monitoring capabilities and features.

 

2. Monitoring capabilities and features

Monitoring capabilities will depend on which method you choose for interfacing the Sentinel RMS license server.

Feature Resolution License totals License usage Denials Reporting Borrowed License Reporting Expiration Date Reporting Multiple Server Redundancy
Support By second

Cells in yellow indicate features available when using OpenLM Server.

Cells in blue indicate additional features available when using OpenLM Server together with OpenLM Broker.

Additionally, using the Broker component allows for buffered communication and the ability to remotely start / stop the license manager service.

 

3. Interfacing Sentinel RMS using OpenLM Server only

Diagram of how OpenLM interfaces with Sentinel RMS using OpenLM Server only

The first option for interfacing Sentinel RMS is to have OpenLM Server query the license manager server directly. This is done remotely with the RMS command-line tools. Using this option however limits the available data to only license totals and license usage.

 

3.1. LM Tools configuration

In order to get OpenLM Server to query the Sentinel RMS license server, OpenLM needs access to the RMS command-line tools to query the server. Since these are usually located on a different machine than OpenLM Server, they must first be copied:

  1. Copy lsmon.exe, lservnt.exe and lsapiw32.dll from the Sentinel RMS machine where the license manager is installed (e.g. C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT) to the OpenLM Server machine in the installation folder (e.g. C:\Program Files (x86)\OpenLM\OpenLM Server\LM).
  2. Click Windows Start → OpenLM → OpenLM Server. The OpenLM Server configuration tool will open.
  3. Select the LM Tools tab located on the left side.
  4. Select the RMS tab.
  5. Click and browse to where you just copied lsmon.exe (e.g. “C:\Program Files (x86)\OpenLM\OpenLM Server\LM”), select it and click Open.
  6. Click Apply to save the configuration.

3.2. Adding a new Sentinel RMS server

After setting up the OpenLM Server configuration tool to work with the Sentinel RMS command-line utility as described above, add a new Sentinel RMS server under the License Servers tab:

  1. Select the License Servers tab.
  2. Click Add.
  3. From the Type drop-down menu, select RMS.
  4. Insert a description in the Description box to help you recognize the license manager.
  5. Set the Time Zone to where the License Server physically resides (e.g. UTC +02:00 Jerusalem).
  6. Submit an appropriate Hostname and Port number (default is 5093).
  7. Is Triad Configuration box: unchecked.
  8. Use Broker box: unchecked.
  9. Vendor Name: the Sentinel RMS vendor name – any descriptive text to help differentiate by vendor in EasyAdmin reports.
  10. Click Apply then close the OpenLM Server configuration tool.

OpenLM Server should now be ready to query your Sentinel RMS license manager remotely and present the relevant license information via the EasyAdmin interface.

 

4. Interfacing Sentinel RMS using OpenLM Server + OpenLM Broker

Diagram of how OpenLM interfaces with Sentinel RMS using OpenLM Broker

The second option for interfacing Sentinel RMS is to have OpenLM Broker query the license manager server locally. This is done through the RMS command-line utilities (lsmon and lservnt) and any available RMS usage log files. Once this data is queried by Broker, it is sent to OpenLM Server for processing. Using this option gives you full monitoring capabilities over Sentinel RMS.

Please note that OpenLM Broker must already be installed and configured to report to OpenLM Server before proceeding further.

 

4.1. Enabling Sentinel RMS usage log functionality

By default, RMS does not record usage log files. This setting may vary from vendor to vendor, however it must be enabled in order for OpenLM to monitor denials.

The -l <usage-log-filename> argument must be added to either the lservnt / lserv start-up command or to the LSERVOPTS environment variable.

Instructions on how to do so can be found in the Sentinel RMS documentation.

Once usage log functionality has been enabled, note the location of the usage file as you will have to provide it below in step 11 of section 4.2.

In case RMS has already been configured to create a usage log and you want to confirm that the file is the correct one, the first lines of a typical RMS usage log file look like this:

# Startup Sentinel RMS License Manager v8.5.5.0015 Thu Feb 27 06:18:53 2014 1393503533 d55syinf02 4 1984

2 1 MTcyMzY= Thu Feb 27 06:18:54 2014 1393503534 FT-Unified v1.0 0 1 0 e3007110 BLR-SGH123T84M_1 8.5.5.0015 1 - - - - - - 0 - - - MA== 275766 MTM5Mzc3OTMwMA==

2 1 MTcyMzY= Thu Feb 27 06:18:54 2014 1393503534 FTAddins v1.0 0 1 0 e3007110 BLR-SGH123T84M_1 8.5.5.0015 1 - - - - - - 0 - - - MQ== 442468 NzE4MjM0

2 1 MTcyMzY= Thu Feb 27 06:18:54 2014 1393503534 FT-Unified v1.0 0 2 0 e3008699 BLR-2QHZ2BS_1 8.5.5.0015 1 - - - - - - 0 - - - Mg== 570497 MTAxMjk2NQ==

2 1 MTcyMzY= Thu Feb 27 06:18:54 2014 1393503534 FTAddins v1.0 0 2 0 e3008699 BLR-2QHZ2BS_1 8.5.5.0015 1 - - - - - - 0 - - - Mw== 1178556 MTc0OTA1Mw==

 

4.2. OpenLM Broker configuration

Automatic OpenLM Broker configuration

To have OpenLM Broker automatically detect part of the settings required to monitor Sentinel RMS, click Detect in the bottom right corner of the Broker configuration tool window:

If the Sentinel RMS service (e.g. “Sentinel RMS License Manager”) is started, Broker will detect and configure the port and utility path settings automatically. Please note that this only auto-detects some settings and does not guarantee that the configuration is valid. To verify and configure the remaining settings, please continue with step 7 in the “Manual” section below.

 

Manual OpenLM Broker configuration

If auto-detect did not work, you can also add and configure the license manager manually. To do so:

  1. Click Add Port
  2. Enter the Sentinel RMS server port number (e.g. 5093)
  3. Select RMS from the “License Manager Type” drop-down menu.
  4. Select the Commands node. Click […] to the left of “Update path for commands:” and browse to the folder where the RMS command-line utilities are located (typically C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT). Click Update.
  5. (Windows only) If your RMS install is configured to run using a Windows service, check the Use Service box and type in Sentinel RMS License Manager.
  6. Click Apply.
  7. Select the data_inquiry node under Commands then click Execute. Make sure that you see a valid output. Note: on some RMS installs, the lsmon utility is placed in a separate folder. In such cases, you would have to manually edit the “data_inquiry” node to point to the correct path and click Apply before clicking Execute.
  8. Right-click the Log Files node and then click Add Log File.
  9. Select the newly created log node.
  10. Select Other from the Type drop-down menu.
  11. Click […] right to the Path field and browse to the location of the Sentinel RMS usage log file as you have configured it in section 4.1.
  12. Click Apply.
  13. Click Restart Broker.

 

4.3 OpenLM Server configuration

Once Broker has been configured, it should be sending data to OpenLM Server. The final step in interfacing Sentinel RMS with OpenLM is to approve the configuration in EasyAdmin.

Automatic OpenLM Server configuration via EasyAdmin

  1. Open the EasyAdmin interface (Windows Start → OpenLM → OpenLM EasyAdmin User Interface or navigate to http://<OpenLM Server host>:7019/EasyAdmin2/)
  2. In the License Servers window, hover over the red row that contains the details of the newly added Sentinel RMS server entry and click Approve.

The Sentinel RMS configuration has now been automatically added to OpenLM Server and should also be present in the OpenLM Server configuration tool.

 

Manual OpenLM Server configuration

If automatic configuration of OpenLM Server via EasyAdmin has failed, you can manually configure OpenLM Server to connect to the Broker installation located on the Sentinel RMS machine.

The hostname and port settings must match those that have been configured for OpenLM Broker above.

The steps for configuring OpenLM Server are the same as described in section 3.2 of this document, with the following difference(s):

  1. The “Use Broker” box must be checked.

 

5. How to verify your Sentinel RMS configuration

To check if the Sentinel RMS License Server is monitored correctly:

  1. Open the EasyAdmin interface (Windows Start → OpenLM → OpenLM EasyAdmin User Interface or navigate to http://<OpenLM Server host>:7019/EasyAdmin2/)
  2. Click EasyAdmin Start → Widgets → License Servers.

The License Servers window will open. Verify that the configured license manager(s) appears on the list. A green circle node indicates an active connection to the license server.

Please note that sometimes it may take up to 3 minutes for the status indicator to change for new connections.

Previous Interfacing the Sentinel HASP license manager – KB3001f
Next Interfacing the Slickedit license manager – KB4001o
Table of Contents