- 1. Method 1: Enabling the OpenLM server to query the IBM-LUM license server:
- 2. Methods 2 and 3: Installing OpenLM on a machine other than the IBM-LUM license server
- 3. Method 2: OpenLM Server queries the IBM-LUM License server via the LUM client
- 4. Method 3: Employ the OpenLM Broker to propagate data to the OpenLM Server
- 5. IBM LUM indications in EasyAdmin
OpenLM supports license monitoring of a wide and ever growing variety of license managers, such as FlexLM and DSLS. This application note elaborates the steps required to configure OpenLM to interface the IBM-LUM license server, to monitor license usage and denials, and obtain license statistics.
Three configuration methods #
There are three methods to query the IBM-LUM License Server, as elaborated below. This document refers to these methods henceforth:
Method 1 – Minimal installation. Installing only the OpenLM Server on the same machine as the IBM-LUM license manager. This method is the most straightforward, but lacks the benefits provided by the OpenLM Broker.
Method 2 – Installing the OpenLM Server and the IBM-LUM client software on a machine other than the IBM-LUM license server. The OpenLM Server will query the IBM-LUM license server via the IBM-LUM client. This method also lacks the benefits provided by the OpenLM Broker.
Method 3 – Installing the OpenLM Broker on the same machine as the IBM-LUM license server, query the License Server locally, and propagate the information to the OpenLM Server. The OpenLM server may be installed on any machine on the network (including the IBM-LUM license server machine). This is the most recommended method, as it displays various benefits for license administrators (e.g. obtaining license denial reports).
1. Method 1: Enabling the OpenLM server to query the IBM-LUM license server: #
Methods 1 & 2 require the OpenLM Server to query the IBM-LUM license server. In order to enable that – follow these steps:
2. Open the OpenLM Server configuration tool.
3. Select the LM Tools tab, located on the left side.
4. Select the LUM tab.
5.Copy the i4blt.exe file the OpenLM Server installation folder, under the LM directory, e.g.: “C:Program Files (x86)OpenLMOpenLM ServerLM” (64bit)
6. Type in the full path of the i4blt.exe file in the LUM executable file text box, e.g.:“C:Program Files (x86)OpenLMOpenLM ServerLMi4blt.exe”
7. Click ‘Apply’.
1.1. Introducing a new IBM-LUM server #
After configuring the OpenLM configuration tool to work with IBM-LUM as described above, introduce a new IBM-LUM server under the License Servers tab:
1. Select the License Servers tab, and Click ’Add’.
2. From the Type drop-down menu, select LUM
3. Type a descriptive name in the Description text box, e.g. “IBM LUM license server”
4. Set the Time Zone to where the License Server physically resides (e.g.: Eastern time).
5. Type in the IBM-LUM license server name in the Hostname text box, e.g.: ibm_lum_server.
6. Type in the IBM-LUM license server’s port number in the Port text box. (The IBM-LUM default port is 1515).
7. “Is Triad Configuration” : OpenLM supports multiple server redundancy configurations for IBM-LUM. This is referred to as “High Availability Licensing (HAL)”.
7a. For HAL multiple server redundancy configurations this box needs to be checked,
7b. OpenLM Brokers need to be installed on each of the IBM-LUM license server machines (see below).
7c. The HAL member server names can be obtained by running the following command line:
i4blt -H s -N "clusterName"
7d. Specify the different cluster’s server names and respective port numbers, one beneath the other, in the ‘Hostname’ list.
7e. Here is some general information on LUM cluster configuration and activation, from the license servers’ perspective.
8. Use Broker check box:
- Unchecked (Default): The OpenLM Server actively queries the license manager. Keep this configuration when not employing the OpenLM Broker.
- Checked: Usage information is obtained solely by the OpenLM Broker installation on the License manager machine.
9. Click Apply.
The OpenLM Server is now able to monitor the IBM-LUM license server when both are installed on the same machine, as described in method #1, above.
2. Methods 2 and 3: Installing OpenLM on a machine other than the IBM-LUM license server #
If the OpenLM Server is installed on a machine other than the IBM-LUM license server, additional actions are required. These actions elaborate methods 2 and 3, already mentioned above:
- Method 2: Configure the OpenLM Server machine to query the IBM LUM License server via the LUM client, or
- Method 3: Query the license server locally by installing the OpenLM Broker on the license server machine, and propagating IBM LUM usage data to the OpenLM Server.
There are many benefits for employing the method 3, requiring the installation of the OpenLM Broker on the License server machine. These benefits include:
- Robustness: License usage information will be buffered in case of connectivity failure.
- Configuration: The OpenLM Broker provides a flexible configuration interface
- Reports: The OpenLM Broker will extract license denial information and propagate it to the OpenLM Server.
3. Method 2: OpenLM Server queries the IBM-LUM License server via the LUM client #
The IBM-LUM Server enables other machines to query license usage and perform actions remotely. For a full install procedure please consult the Using License Use Management Runtime document. The following list is a short overview of this procedure.
1. Make sure that you have IIS installed and configured on the OpenLM Server Machine
2. Install the LUM client software on the OpenLM Server machine. There is no need to configure the OpenLM Server machine as a LUM server.
3. Add a reference to the OpenLM Server on the IBM-LUM License server
4. 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:
For pre-Vista versions, copy this file from
C:Documents and SettingsAll UsersApplication DataIBMLUM to
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.
4. Method 3: Employ the OpenLM Broker to propagate data to the OpenLM Server #
This solution is simple and very beneficial (see above) but requires access to the license server machine for installation. The OpenLM Broker queries the license usage information locally and propagates the data to the OpenLM Server. The OpenLM Broker is a Java application, and can therefore run on Windows or UNIX / Linux license servers. Installation of the OpenLM Broker includes the installation of Java JRE.
4.1. OpenLM Server configuration for IBM-LUM #
The OpenLM Server configuration will be exactly the same as performed in the previous method, i.e. without the Broker, except that the “Use Broker” box should be checked.
4.2. OpenLM Broker configuration for IBM-LUM #
1. Download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker Application Note:
- OpenLM Broker installation Guide: Quick Reference or
- OpenLM Broker Installation Guide: Comprehensive
2. Configure The OpenLM Broker to interface the license server and the OpenLM Server:
2a. Click “Add port” and enter the port number as it was set on the OpenLM Server configuration tool (i.e.: 1515)
2b. The OpenLM hostname and port (e.g. OpenLM_Server and the default 5015)
2c. The vendor name should be set correctly (e.g. “CATIADBS”)
3. The ‘Status’ and “data_inquiry” commands should be as depicted below. Replace <fullpath> with the actual path of the i4blt executable on the IBM LUM license server.
4. In case the IBM LUM system employs HAL – multiple server redundancy, the LUM ‘status‘ and “Data inquiry” commands should contain all 3 license servers as follows:
4a. status command:
i4blt -H s -N "clusterName"
As mentioned above, executing this command will obtain the cluster’s member server names.
4b. “data inquiry” command:
i4blt -s -lc -n “server1 server2 server3” i4blt -s -l co -n “server1 server2 server3 ” i4blt -lp -i -n “server1 server2 server3”
5. IBM LUM indications in EasyAdmin #
In order to verify OpenLM’s interface to the IBM LUM License Server, please
1. Open the EasyAdmin web application.
2. Click EasyAdmin Start → Widgets → License servers. The License Servers window appears. Verify that the configured license managers appear on the list. A green circle node indicates an active connection to a license server.
5.1. IBM LUM denials reports #
IBM LUM license denials will be presented in the EasyAdmin Start → Reports → Denials. Note that they are subject to “True denials” filtering. That means that denials’ reporting will be delayed for a while, to assert that the user has not been granted a license shortly after being denied one.
Your OpenLM system is now configured to provide IBM LUM licensing information.
If you require further assistance on this subject, please contact email@example.com, and our team will be glad to assist.