Sentinel RMS

This guide explains how to configure OpenLM with Sentinel RMS to monitor license usage and generate license statistics.

Requirements

To query Sentinel RMS:

• Install OpenLM SLM v4.3 or higher on a machine in your organization, or use a Software License Management Cloud (SLMC) account.
• (Optional) Install OpenLM Broker v4.x or higher on the Sentinel RMS machine to take advantage of advanced monitoring features.

Monitoring capabilities

Monitoring features depend on whether you use OpenLM SLM alone or together with OpenLM Broker.

Feature	Resolution	License totals	License usage	Denials reporting	Borrowed license reporting	Expiration date reporting	Multiple server redundancy
Support	By second	✔	✔	✔	✔	✔	❌

• OpenLM SLM only: license totals and license usage.
• OpenLM SLM with OpenLM Broker: every capability marked ✔ in the table, including denials, borrowed license, and expiration date reporting.

Using Broker also allows buffered communication and remote start/stop of the license manager service.

Monitoring with OpenLM SLM only

Diagram of OpenLM SLM querying Sentinel RMS directly

OpenLM SLM can query Sentinel RMS directly through RMS command-line tools. This option provides license totals and usage only.

LM tools configuration

To allow OpenLM SLM to query Sentinel RMS:

1. Copy lsmon.exe, lservnt.exe, and lsapiw32.dll from the Sentinel RMS machine (for example,
   C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT)
   to the OpenLM SLM installation folder (for example,
   C:\Program Files\OpenLM\OpenLM Server\LM).
2. Open EasyAdmin → Start → Administration → License Manager Servers.
3. Select LM type RMS.
4. Set the full path to the RMS executable (lsmon.exe).
5. Select Save.

Configuring LM tools for Sentinel RMS

Adding a new Sentinel RMS server

After setup:

1. Open the License Servers tab.
2. Select Add LM.
3. Enter a Display Name.
4. Select RMS as LM type.
5. Enter Server Host Name and Port (for example, 5093).
6. Set the correct Time Zone.
7. Turn Use Broker toggle off.
8. Select Save.

Adding Sentinel RMS server in EasyAdmin

Monitoring with OpenLM SLM and Broker

Diagram of OpenLM Broker querying Sentinel RMS locally

When Broker queries Sentinel RMS locally using RMS command-line utilities and log files, you gain full monitoring capabilities. Broker then forwards the data to OpenLM SLM.

note

You must install and configure OpenLM Broker before continuing.
See the Broker installation guide and the Broker configuration guide.

Activating Sentinel RMS usage log

By default, RMS does not record usage logs. Activate logging with the -l <usage-log-filename> argument in the RMS startup command (lservnt/lserv) or the LSERVOPTS environment variable.

For detailed steps, see the Sentinel RMS documentation.

Logs are required for denial monitoring.

OpenLM Broker configuration

Broker can detect Sentinel RMS automatically. If detection fails, configure Broker manually in the Broker configuration tool or in the Broker web UI.

Automatic detection

In the Broker configuration tool:

1. Select Detect.
   If the Sentinel RMS service is running, Broker detects the port and utility path automatically.

tip

Detection may not capture all settings. Continue with manual configuration if needed.

Automatic Broker detection

Manual configuration

If detection fails:

1. Select Add Port → enter RMS port (for example, 5093).
2. Select RMS as license manager type.
3. Under Commands, update the utility path to the RMS tools folder.
4. (Windows only) Check Use Service and enter Sentinel RMS License Manager.
5. Select Apply.
6. Run a data_inquiry to verify valid output.
7. Add the RMS usage log under Log Files.
8. Restart Broker.

Manual Broker configuration

Broker UI configuration

Alternatively, configure through the Broker UI in your browser:

1. Go to License Manager → Add License Manager.
2. Select RMS, enter port, and add.
3. Check the executable path.
4. (Windows only) Set service to Sentinel RMS License Manager.
5. Run data_inquiry and verify output.
6. Add vendor information if required.
7. Configure Log Files for RMS usage logs.
8. Save changes.

Broker UI settings for RMS

OpenLM SLM configuration

If Broker was configured successfully, Sentinel RMS is added automatically to OpenLM SLM.

If automatic setup fails, configure manually:

1. In OpenLM SLM configuration, add Sentinel RMS server.
2. Enter hostname and port from Broker.
3. Check Use Broker.
4. Save.

Activating token calculator (OpenLM SLM v24.6+)

By default, token calculations are deactivated. To activate:

1. Back up appsettings.json.

2. Open the file (default: C:\Program Files\OpenLM\OpenLM Server\bin).

3. Locate this section:

   },
   "AspenTokens": {
       "AspenTechTokensFile": "../config/aspen_tokens_breakdown.json",
       "EnableTokenCalculations": false
   }

4. Change EnableTokenCalculations to true:

   },
   "AspenTokens": {
       "AspenTechTokensFile": "../config/aspen_tokens_breakdown.json",
       "EnableTokenCalculations": true
   }

5. Save the file.

6. Restart the OpenLM Server service:

   net stop "OpenLM Server"
   net start "OpenLM Server"

7. Verify in OpenLM SLM that token calculations are enabled.

Verifying Sentinel RMS configuration

To confirm monitoring is active:

1. Open EasyAdmin.
2. Go to Start → Widgets → License Servers.
3. Check that Sentinel RMS servers appear in the list.

A green circle indicates an active connection. It may take up to 3 minutes for new connections to display as active.