---
title: Sentinel RMS
description: This guide explains how to configure OpenLM with Sentinel RMS to monitor license usage and generate license statistics.
product: OpenLM Platform
---

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

## Before you begin

To query Sentinel RMS:

- OpenLM Platform

- OpenLM Broker v25.x or higher installed on the same machine as Sentinel RMS, and approve it in [Broker Hub](https://openlm.com/documentation/cloud/data-collection/broker-hub).

## Monitoring capabilities

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

| Report resolution | License totals | License usage | Denials reporting | Borrowed license reporting | Expiration date reporting | Multiple server redundancy |
| --- | --- | --- | --- | --- | --- | --- |
| By second | Yes | Yes | Yes | Yes | Yes | No |

- Yellow cells: Features available with OpenLM Server.

- Blue cells: Extra features available with OpenLM Server + Broker.

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

*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 Server.

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

## Automatic Broker configuration

1. Open Broker UI at http://localhost:5090/.

1. Go to License Managers → Detect

1. Sentinel RMS appears

1. Validate and save

### Broker UI configuration

Alternatively, configure through the Broker UI in your browser:

1. Open Broker UI at http://localhost:5090/.

1. Go to License Manager → Add License Manager.

1. Select RMS, enter port, and add.

1. Check the executable path.

1. (Windows only) Set service to Sentinel RMS License Manager.

1. Run data_inquiry and verify output.

1. Add vendor information if required.

1. Configure Log Files for RMS usage logs.

1. Save changes.

*Broker UI settings for RMS*

## Activate token calculations

1. Back up `appsettings.json`.
1. Open the file (default location: `C:\Program Files\OpenLM\OpenLM Server\bin`).
1. Locate the following section:

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

1. Change `EnableTokenCalculations` to `true`:

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

1. Save the file.
1. Restart OpenLM Server:

    ```powershell
    net stop "OpenLM Server"
    net start "OpenLM Server"
    ```

1. Verify in OpenLM Server that token calculations are activated.

## Approve Sentinel RMS in OpenLM Platform

1. Sign in to OpenLM Platform.
2. From the menu, go to **License Servers** → **Pending Server**.
3. Select the Sentinel RMS license manager, then select **Approve and Merge**.

## Verify the integration

1. In OpenLM Platform, go to **License Servers Live** → **Server Statistics**.
2. Confirm Sentinel RMS appears with a green status indicator.

:::note
It can take up to 3 minutes for the status to update for a new connection.
:::
