Interfacing the OpenText License Manager - AN3001s - OpenLM Software License Management
USA +1 866 806 2068 | JAPAN +81 3 45208991 担当:萩原

Interfacing the OpenText License Manager – AN3001s


OpenLM version 2.0 supports license monitoring of a wide, and ever growing variety of license managers. This application note elaborates the steps required to configure OpenLM to interface the OpenText License Manager, and obtain reliable license reports and usage statistics.

How does it work:

  • The OpenText license manager directs usage data into a log file.
  • A lightweight Java application (EventLog_Monitor) is run on the OpenText license server. It  detects changes made to the log file and produces an OpenLM generic XML file which holds this data.
  • The OpenLM Broker propagates the XML file it to the OpenLM Server.
  • The OpenLM Server parses this XML and presents it in the OpenLM EasyAdmin web application.


OpenText License server configuration

1. The OpenText license manager needs to be configured to log all information to a specific file (e.g. opentext.log).  Make sure that the log size and rotation are adequate for containing the entire license usage information over a few minutes.

2. Download the EventLog_Monitor and copy the entire EventLog_Monitor folder to the OpenText server, preferably under the OpenLM Broker installation folder (see OpenLM Broker configuration, below).

3. Type in the license information in the <full_path>\EventLog_Monitor\binaries\LicenseInfo.txt file. For example:

Product: VME Used Seats: 8 Total Seats: 106

4. Open the <full path>\EventLog_Monitor\binaries\ file and configure it as follows:

    • server = OpenText hostname or IP (e.g.: OpenText_lm)
    • port = number to identify the output (e.g. 12345)
    • vendor = vendor used for logging in OpenText LM log file
    • monitored.log = filename and path as specified in #1 above (e.g. opentext.log)
    • = filename and path as specified in #3 above.
    • unified.xml = xml output file to be addressed by the OpenLM Broker
    • sync.interval = number of seconds to update the xml file. Should be smaller than the interval specified in “data_inquiry” command on the OpenLM Broker configuration tool.

Make sure to use ‘/’ instead of  ‘\’ as a separator for full paths in this file.

ImgLM.ini file

This file configures the OpenText logging. Please note the following:

Event log message IDs

The “Event log message IDs” part marks the information to be logged. ID numbers are attributed a value;

  • ‘1’ – Enable logging of an event
  • ‘0’ – Do not log this event.

For example, the line


will cause an event of successful license check-out to be logged, whereas


will cause an event of successful license check-out not to be logged.

Event Log File

  • Event Log File Max Size: Maximal size of the log file in MB. Set it to be large (see note below).
  • Event Log File Max Duration: Number of days for running the log. Set it for 365 days(see note below).

Important note:

When either Max Size or Max Duration limits are surpassed, a new log file will be commenced, and it will be named according to the commencement date  (e.g.: ImgLM_01_17_14.log started at January 17, 2014). Since OpenLM is configured to monitor a specific log file – this will end the OpenLM monitoring. The user should head this issue.

OpenLM Opentext event monitor

Click the LogMonitorService.exe icon in the EventLog_Monitor directory to start the “OpenLM Opentext event monitor” service.

Make sure the services has been started. The unified XML file should consequently be created now.

OpenLM Broker Configuration

Download and install the latest OpenLM Broker version from the ‘Downloads’ section in the OpenLM website. Please refer to the OpenLM Broker Comprehensive guide document for general Broker configuration:

Application Note (3004a) OpenLM v2.0: OpenLM Broker Quick Reference guide version

Application Note (3004b): OpenLM v2.0: Broker Comprehensive Installation Guide

  • Set the OpenLM server hostname (e.g.: openlm_server)
  • Set the OpenLM Broker port number (e.g.: maintained at its default value 7016).
  • Set the License manager type to ‘OpenLM_Generic’
  • The license server hostname and port should be set exactly as they were defined in step #4 above (e.g.: OpenText, 12345).
  • Configure the Broker’s “data_inquiry” command text box to periodically read the unified.xml output file defined in step #4 above. The command for that is:

cmd /C type <full_path>\unified.xml

  • Click ‘Execute’ to check the operation of the Data Inquiry
  • Do the same for the ‘status’ command.
  • Set the Vendor name to ‘ImgLM’
  • Click ‘Apply’ and “Restart Broker”


OpenLM Server configuration

In order to configure OpenLM to monitor a OpenText License Manager, The OpenLM Server must be configured as follows:

  • Click ‘Add’
  • Set the LM Type to “OpenLM Generic”
  • Set the License server’s Time zone (e.g.: Istanbul UTC+2)
  • Type in the Hostname (e.g. OpenText_lm) or IP of the OpenText License server. This should be the same name as configured in the OpenText server and OpenLM Broker configurations (see above)
  • Type in the port number of the OpenText License manager. This should be the same name as configured in the OpenText server and OpenLM Broker configurations (e.g. see above: 12345)
  • Clear the “OpenLM Server remotely queries license manager” box.
  • Click ‘Apply’ and then ‘Restart now’



Run the EventLog_Monitor.jar command. Note that at the time of writing these lines the EventLog_Monitor is not run as a service, but should remain running permanently. One option to bypass this obstacle is to use a 3rd party tool such as”alwaysUp” that would run it as a Windows service.

OpenLM EasyAdmin

Now OpenLM is configured to monitor the OpenText license manager. Open the EasyAdmin web application to monitor historical and real-time usage information