An RLM Log Reader processes raw transaction logs generated by the Reprise License Manager (RLM) server into human-readable data. This allows you to track concurrent software license usage, peak demand, and user access details.
You can extract actionable insights from your license servers by configuring the logs properly and utilizing log-parsing tools. Step 1: Enable Report Logging on the RLM Server
Before reading logs, you must ensure the RLM server is actively recording raw data to an ISV options file.
Access Admin Interface: Open your browser and navigate to the RLM Web Admin interface. By default, this is localhost:5054. Configure ISV Options: Go to the ISV Runge Options dialog.
Add the Log Command: Enter the path where you want to output your logs using the REPORTLOG line:
REPORTLOG +C:\RLMLog\reportlog.txt detailed auth ROTATE monthly Use code with caution.
(Note: The + sign appends data to an existing file, while ROTATE monthly keeps individual log sizes manageable.)
Restart Server: Click Reread/Restart Servers to apply changes. The RLM server will generate a raw data file (reportlog.txt) in your specified folder. Step 2: Select an RLM Log Reader Utility
Raw RLM logs are notoriously difficult to digest manually. Choose a log viewer based on your organizational requirements:
Open-Source Readers: Utilities like the standalone RLM Log Reader on SourceForge translate raw logs into standard formats like CSV. This lets you analyze usage inside Microsoft Excel or Google Sheets.
Browser-Based Tools: Lightweight web parsers like the License Manager Log Analysis Tool allow you to drop the log directly onto your browser for client-side charting without sending corporate data over the cloud.
Enterprise Management Suites: Solutions like OpenLM monitor active connections dynamically by linking straight to your RLM vendor setup via rlmutil.exe. Step 3: Analyze Essential Metrics
Once the reader loads your reportlog.txt, filter and monitor these core metrics:
Peak Concurrent Demand: Find the highest number of licenses checked out simultaneously. If you purchased 50 seats but peak usage never clears 20, you can trim your software budget during the next renewal cycle.
License Denials: Pay close attention to logs tracking when a user is denied an application seat. High denial counts point to a true license deficit or configuration mistakes, like trying to fetch the wrong software version.
User/Host Session Durations: Identify active sessions or “license hogging,” where a specific machine checks out an asset and fails to return it over days.
Feature Tracking: Track specific sub-features or modules of a CAD/engineering program to understand exactly what components your team relies on most. If you want to dive deeper, let me know: Which specific log reader tool or software you plan to use?
Whether you are dealing with a Windows or Linux server environment?
If you need help troubleshooting a high rate of license denials? Version 25: Reprise RLM | OpenLM Documentation
Leave a Reply