Skip to main content

Peloton RigView

Follow these steps to monitor Peloton RigView licenses with OpenLM. RigView is the rig scheduling application of Peloton, and its network licenses come from the RigView License Server on a server in your organization. The license server writes a usage log with a line for each logon, logoff, and denied request. OpenLM Broker reads that log on the license server machine and reports each session and denial to OpenLM SLM.

Requirements​

Before starting, make sure you have:

  • OpenLM SLM installed on a machine in your organization, or a Software License Management Cloud (SLMC) account.
  • OpenLM Broker v23.8.20.840 or higher, installed on the RigView License Server machine and reporting to OpenLM SLM. Earlier Broker versions do not list Peloton RigView as a license manager type. Use v24.4.5.1002 or higher if you want OpenLM to show the number of RigView licenses that you own, because that version added the settings file that holds the license total.
  • RigView network licenses served by the RigView License Server.
  • Access to the RigView License Server machine, and the location of its usage log.

Monitoring capabilities​

The current monitoring capabilities for Peloton RigView through OpenLM Broker are:

LM Type in the BrokerCommandsLogsQuantityExpiration dateDeniedBorrowingAllocationsReport resolution
Peloton RigViewNoYesYesNoYesNoNoSeconds

For each session, Broker reports:

  • Feature name: always RigView. The usage log does not name a feature, so Broker reports every session against this one feature.
  • Username: the user in the second column of the log line.
  • Workstation: the host in the third column of the log line. When users run RigView through Citrix, this is the Citrix server, not the user's own computer.
  • Start and end time: the time of the logon and logoff lines, to the second.
  • Vendor: the vendor that you select for the log file.

Broker also reports a denial for each line in which the license server refuses a logon because all network licenses are in use.

The license total comes from a settings file that Broker keeps for the license manager, because the usage log does not state how many licenses you own. Until you set the total, OpenLM shows RigView as unlimited. See Set the license total. Expiration dates, borrowed licenses, and license allocations are not available.

How OpenLM interfaces with Peloton RigView​

Diagram: OpenLM Broker on the license server reads its log files and sends the data to OpenLM Server, which you manage in the EasyAdmin web application. How OpenLM collects Peloton RigView usage

Broker runs on the RigView License Server machine, reads the usage log there, and sends the license data to OpenLM SLM.

  • Log file: Broker reads the usage log of the RigView License Server. Each line holds tab-separated columns: the time, the user, the host, the event, the number of licenses in use, the RigView version, a session ID, the session duration, and an optional message. Broker reads 3 kinds of event:

    2026-10-19 08:12:51	jdoe	CTX-01	logon	3	3.1.5051.26110	25A40322098847A1BED64F223D034DA0	00:00:00
    2026-10-19 09:47:05	jdoe	CTX-01	logoff	2	3.1.5051.26110	25A40322098847A1BED64F223D034DA0	01:34:14
    2026-10-19 09:50:12	asmith	CTX-02	note	5	3.1.5051.26110	E97BE0328A2941DC99CA41D43F93AD6F	00:00:00	User denied license because all network licenses in use.

    A logon line is a check-out, a logoff line is a check-in, and a note line is a denial. Broker counts the licenses in use from the sessions that it tracks, not from the fifth column, and ignores the version and the duration. It takes the usernames and workstations from the log as they are.

  • Sessions: Broker matches each logoff to its logon by the session ID in the seventh column. A logoff whose session ID Broker has not seen is ignored. The license server also writes a logoff line when it removes a timed-out or orphaned session, and Broker ends the session in OpenLM at that point.

  • First read: When you add the log file, Broker reads the whole file once to find the sessions that are still open, and reports them as in use. From then on it reports each new logon, logoff, and denial. Broker does not upload earlier usage history. After a Broker restart, Broker rebuilds the open sessions the same way and continues from the line where it stopped. If Broker was down for more than a day, it skips the lines written while it was down.

  • License total: Broker reads total.RigView from peloton@<port>.properties in the Broker installation folder when it starts reading the log. -99, the default, means unlimited.

  • Commands: None run on a schedule. Broker does not connect to the RigView License Server, so the port that you enter in Broker only identifies the license server in OpenLM.

OpenLM Broker configuration​

Note

Install OpenLM Broker on the RigView License Server machine and confirm that it reports to OpenLM SLM before starting these steps.

  1. Open a browser on the RigView License Server machine and go to the Broker web UI at http://localhost:5090/.

  2. On the License Managers page, check Host.

    OpenLM lists the license server under this host name, and the field holds the host for every license manager on the page, not for Peloton RigView alone. If the field is empty, enter the host name of the RigView License Server machine and select the save icon next to the field.

  3. Go to License Managers → Add License Manager.

  4. From LM Type, select Peloton RigView.

  5. In Port, enter a port number, and select Add.

    Broker does not connect to this port, so any port that no other license manager on this Broker uses works, for example 5055. Broker refuses a port that another license manager already uses. The port also names the settings file that holds the license total, peloton@<port>.properties.

    The Add License Manager dialog with LM Type set to Peloton RigView and port 5055 Add Peloton RigView as a license manager

  6. On the Vendors tab, select Add Vendor, enter the vendor name that you want OpenLM to show, for example Peloton, and select Continue.

    The new vendor appears in the list after you switch to another tab and back.

  7. On the Log Files tab, select Add Log File, and fill in the dialog:

    • Log Type: Usage Log, the only type for Peloton RigView.
    • Log Name: a name for the log, for example RigView usage log.
    • Log Path: the full path of the usage log of the RigView License Server, for example C:\Program Files\Peloton\RigView License Server\rigview.log. Select the search icon next to the field to browse to it.
    • Vendor: the vendor that you added on the Vendors tab.
    • Under Advanced, leave the defaults. Broker reads the file every 10 seconds, with Watch files by pattern off.

    The Add Log File dialog with Log Type Usage Log, the path of the RigView usage log, the vendor Peloton, and the Advanced section with its defaults Point Broker at the RigView usage log

    The Commands tab stays empty. Broker runs no commands for Peloton RigView, and Use the operating system start/stop commands is off.

  8. Select Continue, then select Save.

Set the license total​

The usage log does not say how many RigView licenses you own, so OpenLM shows the feature as unlimited until you set the total in the settings file of the license manager. The file needs Broker v24.4.5.1002 or higher.

  1. On the RigView License Server machine, open peloton@<port>.properties in a text editor that you run as administrator.

    The file is in the Broker installation folder, C:\Program Files\OpenLM\OpenLM Broker by default, and <port> is the port that you entered in Broker, for example peloton@5055.properties. Broker creates the file the first time it reads the usage log for that port. If the file is not there yet, wait for Broker to read the log once after you save the configuration.

  2. Set total.RigView to the number of RigView network licenses that you own, for example:

    total.RigView=22

    -99 means unlimited.

  3. Save the file, and restart the OpenLM Broker service in Windows Services.

    Broker reads the file when it starts reading the log, so the new total reaches OpenLM after the restart.

OpenLM SLM configuration​

Automatic configuration through EasyAdmin​

If the preceding steps are complete, Broker reads the log every 10 seconds, by default, and reports Peloton RigView to OpenLM SLM. Approve the license server in EasyAdmin:

  1. Open EasyAdmin (http://<Server IP>:5015) and go to Start → Widgets → License Manager - Servers.

  2. Select the There are N servers pending approval link at the top of the widget.

    The Administration - License Manager Servers window opens, with the pending entries at the top of the list.

  3. Find the pending Peloton RigView entry, with the host name and the port that you configured in Broker, and select the edit icon at the end of its row.

    Broker reports Peloton RigView with the OpenLM Generic protocol, so its Type is OpenLM Generic.

  4. Optionally rename the connection in Display name, confirm the Host Name and Port, and select APPROVE.

Manual configuration through EasyAdmin​

If automatic configuration fails:

  1. Go to Start → Administration → License Manager Servers.

  2. Select Add LM.

  3. In Display name, enter a name for the connection, for example Peloton RigView.

  4. From Type, select OpenLM Generic.

    Use Broker turns on.

  5. In the row under Host Name, Port, and Time Zone, enter the host name and the port exactly as configured in Broker for Peloton RigView, and select a time zone.

  6. Select SAVE.

Verify your configuration​

  1. Open EasyAdmin in your browser.
  2. Go to Start → Widgets → License Manager - Servers.
  3. Confirm that the Peloton RigView license server shows the Status Up to date, and that Quantity shows the total from the settings file, or Unlimited if you have not set it.
  4. Go to Start → Reports → License Activity, select Include Current Activity, and select Apply. Confirm that the RigView feature appears after its first logon, with each session's username and workstation.
  5. Go to Start → Reports → Denials and confirm that denied logons appear, if the license server has refused any.

Troubleshooting​

If Peloton RigView never appears as pending in EasyAdmin, confirm that the Broker reports to OpenLM SLM: other license managers on the same Broker update in EasyAdmin.

If the license server is approved but shows no usage, check these points:

If OpenLM shows RigView as unlimited, set total.RigView in the settings file and restart the Broker service, as described in Set the license total. If the total does not change after the restart, check that the port in the file name matches the port of the license manager in Broker.

If OpenLM shows a session that ended long ago, the license server has not written a logoff line for it yet. The RigView License Server writes a logoff line when it removes a timed-out or orphaned session, and Broker ends the session at that point.

The Broker log holds the detail, in the logs folder of the Broker installation.

Known limitations​

  • Broker reports every session against the single feature RigView, because the usage log names no feature.
  • Broker counts 1 license for each logon line that has no logoff line yet, even when the license server does not charge a second license for a second session of the same user on the same host.
  • The license total comes from the settings file, not from the license server. Until you set it, OpenLM shows RigView as unlimited.
  • Broker does not report expiration dates, borrowed licenses, or license allocations, and does not upload usage history. Usage in OpenLM starts when you configure the license manager.
  • When users run RigView through Citrix, the workstation in OpenLM is the Citrix server, because that is the host in the usage log.
  • Broker does not check whether the RigView License Server is running. OpenLM shows the license server as up while Broker reports it.
  • Broker reads the log on the machine where it runs. Install a Broker on each RigView License Server machine that you want to monitor. 2 RigView License Server installations on the same machine need 2 license managers in Broker, each with its own port and usage log.
Last updated on by test

The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.