Application Note 1019: Monitoring an IBM LUM License server using the OpenLM Utilizer


The OpenLM Utilizer supports the IBM LUM license server. IBM LUM licenses are used by various software vendors, the main being Dassault Systems (Catia software). In order for OpenLM to support the LUM License server it has to be able to access the LUM License server remotely or locally. Different configuration options are supported by OpenLM that allows system managers to configure license servers located on LAN and WAN networks.

Table of contents

System Configurations Options
IBM LUM and OpenLM on the same machine
IBM LUM and OpenLM on separate machines
Configuring the OpenLM Broker to push usage information to the OpenLM Server
Configuring the OpenLM Server machine to query usage on the IBM LUM License server
Adding an IBM LUM license server in the OpenLM server configuration form
IBM LUM Support Level

System Configurations Options

OpenLM Supports flexible configurations for LAN or WAN networks. This section elaborates these configurations. Most of the information in this section is also relevant to other license servers such as SafeNet RMS, SafeNet HASP, FLEXlm, FLEXnet, RLM and others.

IBM LUM license server and OpenLM on the same machine

This is the most simple configuration but not a very realistic one. Most companies have more than one license server and because of that, they install OpenLM on a separate machine. When OpenLM server is installed on the same machine as the IBM LUM License server, there is no additional configuration steps; just add the server name and port to the configuration.

IBM LUM license server and OpenLM on separate machines

In this scenario, the OpenLM Server is installed on one machine and the license server is installed on another. The problem we have to solve is how to enable the OpenLM Server to access the LUM License Server. There are two possible solutions:

  • Employ the OpenLM Broker to send IBM LUM usage data to the OpenLM Server.
  • Configure the OpenLM Server machine to be able to query usage on the IBM LUM License server.

Configuring the OpenLM Broker to push usage information to the OpenLM Server

This is the most simple solution but it requires access to the license server machine for installation. OpenLM Broker software is reading the license usage locally and pushing the information to OpenLM Server.
Installation of the OpenLM Broker requires Java JRE. It can run on any operating system supported by Java; hence OpenLM supports Linux, Windows and UNIX license servers. Please refer to the OpenLM Broker quick start Application Note for further information.

OpenLM supplies an updated version of the IBM LUM executable file i4blt.exe. On occasion, this file may be non-compliant by version to the one that runs the IBM LUM license manager. If this occurs, please change the path fo IBM LUM commands in the OpenLM Broker, as elaborated in this trouble – shoot article.

Configuring the  OpenLM Server machine to query usage on the IBM LUM License server.

The IBM LUM Server enables other machines to query license usage and perform other actions remotely. For a full install procedure please consult the IBM LUM documentation. The following list is a short overview of this procedure.

  1. Install Java JRE on the OpenLM Server machine.
  2. Make sure that you have IIS installed and configured on the OpenLM Server Machine.
  3. Install the LUM software on the OpenLM Server machine. There is no need to configure the OpenLM server machine as an LUM server.
  4. Add a reference to the OpenLM Server on the IBM LUM License server.
  5. After installing the LUM software on the OpenLM Server machine, the i4ls.ini file is created. For Windows versions Vista and beyond, copy this file from

C:\Users\<Username>\AppData\Local\VirtualStore\ProgramData\IBM\LUM  to C:\ProgramData\IBM\LUM.

For pre-Vista versions, copy this file from

C:\Documents and Settings\All Users\Application Data\IBM\LUM to

C:\Users\All Users\IBM\LUM

Note that if you use the Server’s IP instead of its name (for instance if the servers  are located on different DNS domains so that DNS resolution does not work), a ‘#’ symbol must precede the IP.

Adding an IBM LUM license server in the OpenLM server configuration form

Like the configuration of FLEXlm and SafeNet RMS Services, the configuration of an IBM LUM is simple and straight forward:

  1. Open the OpenLM Server Configuration, on the License Servers tab.
  2. Click the ‘Add’ button. Type in the License Server name (e.g.: olm_test_lum2) and port number (e.g.: 9999).
  3. Select ‘LUM’ in the license server ‘Type’ drop down menu.
  4. Type in a verbal Description in the ‘Description’ text box (e.g.: new LUM license manager)
  5. Click the ‘Apply’ button. A restart notification appears.
  6. Click the ‘Restart now’ button. That’s it: the OpenLM Utilizer is set to monitor the LUM license server.

IBM LUM Support Level

The main functionality of the OpenLM Utilizer is also applicable to IBM LUM licenses. In addition, the OpenLM Utilizer facilitates unique IBM LUM features, such as feature versions.

The main OpenLM supported features for IBM LUM include:

  • License inventory reporting.
  • License expiration alerts (from OpenLM v1.8).
  • Current license usage.
  • Usage reports and charts.
  • License billing for groups or projects.


IBM LUM (License Use Management) is the IBM product for technical software license management (analogous to FLEXnet, being Flexera’s  license management product). The OpenLM Utilizer fully supports the IBM LUM software, and provides a flexible architecture for complex configurations.

OpenLM supports unique features of IBM LUM such as versions for features. Advanced OpenLM features such as License Usage Billing, Usage Reports and Usage Charts are supported for IBM LUM.

Revision Date Author Notes
0.1 – Preliminary Nov27, 2011 Preliminary
1.0 May13, 2012 License expiration alerts:  from OpenLM v1.8.

ArcGIS Software Bug/Problem: “The ArcGIS Desktop Administrator does not connect to ArcGIS License Manager 9.3 while it is connected through VPN or network speeds are slow”


You must not panic when you see above mentioned issue during the process of ArcGIS license-claiming from ArcGIS License Manager 9.3. This is a software bug mostly observed in all level of ArcGIS software ver9.3; earlier releases of this software did not observe this problem but following mentioned all levels observed this issue.

  • ArcGISArcEditor 9.3
  • ArcGIS – ArcInfo 9.3
  • ArcGIS – ArcView 9.3 & 9.3.1
  • ArcInfo Workstation 9.3

All of the above software modules observe this problem while operating on following Windows Operating systems.

  • Windows 2000
  • Windows XP
  • Windows 2003 Server
  • Vista

This bug is identified by the ID ‘NIM037135’ and FlexNet licensing error ID “-15,570” which is shown in the error report/message returned against licensing request to the server. Following error message is returned with related details:

The name of the server and license path may vary as per network configuration. The error numbering scheme will be -15 and followed by 570 after comma; this is ArcGIS error reporting format.

Reasons for error:

This happens mostly in following two conditions when network/concurrent licensing scheme for ArcGIS is implemented.

  • The connection between server and license requesting machine is through VPN.
  • The connection is either Dial-up or a slow ISDN/DSL one.


There is a stepwise process to resolve this issue of the software through modification of the environment variables in the Windows operating systems. The network or server client messages take certain time to process and reach at their destinations. Therefore, the waiting time of the program for communication response to reach is set a bit larger to resolve this issue on the windows OS. Stepwise procedure is given below:

  • Right click My Computer and choose properties.
  • On system property dialogue box choose advanced tab.
  • Click on the environment Variables
  • On environment variable dialogue box choose system variables field and hit the new button
  • A new system variable dialogue box with two fields appears; put “FLEXLM_TIMEOUT” in variable name and put 1000000 in variable value field
  • .Click OK on all three dialogue boxes to close them
  • Launch the ArcGIS 9.3 program

If the problem still persists then, repeat above mentioned procedure with an increase the variable value in the multiples of 1000000 micro seconds and reach to the value which gives you satisfactory communication results.

OpenLM Broker Configuration on Windows XP

The use of Windows XP as an operating system  for FLEXlm license servers is very popular in organizations. It allows the reuse of existing OS licenses and provides the needed functionality.

OpenLM Broker is an optional but highly recommended component that can be installed on the license server. It supports any operating system that supports JAVA. On Windows it’s implemented as a service. The OpenLM Broker provides advanced functionality to FLEXlm and other supported license managers such as IBM LUM, Sentinel RMS, Sentinal HASP and others.

When logging out of Windows XP the operating system it sends the SIGHUP signal. The SUN JVM interprets it as a shut down command and closes the java.exe process that serves OpenLM broker.

This behavior on Windows XP  is causes the Java process to die away when the user is logging out of the XP based license server.

The solution is simple, add the -Xrs flag to the the Broker startup command.

open the registry editor,
go to key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\OpenLM Broker\Parameters
modify the “Application” value to :
“C:/Program Files/Java/jre6/bin/java.exe” -Xrs -jar “C:\Program Files\OpenLM\OpenLM Broker/OpenLMBroker.jar”  start “C:\Program Files\OpenLM\OpenLM Broker/broker.xml”

This issue is solved in version of OpenLM Broker.