End Google Tag Manager (noscript) -->
USA +1 866 806 2068 | UK +44 203 1292 513 | JAPAN +81 3 45208991 担当:萩原 info@openlm.com

Interfacing the IBM LUM license manager – AN4001h

Scope:

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.

Enabling the OpenLM server to work with IBM LUM:

In order to configure OpenLM to work with IBM LUM, follow these procedures:

  1. Select the LM Tools tab, located on the left side
  2. Select the LUM tab
  3. Copy i4blt.exe to “C:\Program Files (x86)\OpenLM\OpenLM Server\LM” (64bit)
  4. Copy the full path of the executable file :“C:\Program Files (x86)\OpenLM\OpenLM Server\LM\i4blt.exe” in the LUM executable file text box
  5. Click Apply

 

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:

Select the License Servers tab, and Click ’Add’. From the Type drop-down menu, select LUM

1. Type a descriptive name in the  Description text box, e.g. “IBM LUM license server”

2. Set the timezone to where the License Server physically resides, e.g. Eastern time.

3. Submit an appropriate Hostname and Port numbers, e.g. ibm_lum_server and 1515 respectively. The IBM LUM default port is 1515

4. Is Triad Configuration: When using Triad server option, check the “Is Triad configuration” box.

4a. The cluster’s member server names can be obtained by running the following command line:

i4blt -H s -N “clusterName”

4b. Specify the different cluster’s server names and respective port numbers, one beneath the other, in the ‘Hostname’ list.

4c. Here is some general information on LUM cluster configuration and activation, from the license servers’ perspective

5. OpenLM Server queries license manager check box:

  • Checked (Default): The OpenLM Server actively queries the license manager.
  • Unchecked: Usage information is obtained solely by the OpenLM Broker installation on the License manager machine

Keep this box checked, unless using the OpenLM Broker to query the license server locally (see below).

6. Click Apply, and the consequent “Restart now” button. The IBM LUM server is now ready to interface OpenLM.

Installing OpenLM on a machine other than the IBM LUM license server

When the OpenLM server is installed on the same machine as the IBM LUM License server, there are no additional configuration steps required. If the OpenLM server is installed on a machine other than the IBM LUM license server, we need to enable the OpenLM Server to access the LUM License Server. There are two possible solutions for that:

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

There are many benefits for employing the 2nd option, requiring the installation of the OpenLM Broker on the License server machine. These benefits include:

  • Improved robustness: License usage information will be buffered in case of connectivity failure.
  • The OpenLM Broker provides a more flexible configuration interface
  • Denial reports. The OpenLM Broker will extract license denials information and propagate it to the OpenLM Server.

 

Option 1: Configure the OpenLM Server machine to query usage on the IBM LUM License serverlum2

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:

C:\Users\\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.

Option 2: Employ the OpenLM Broker to send IBM LUM usage data to the OpenLM Server

 lum1

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 pushes it 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. Please refer to the quick reference OpenLM Broker Application Note for installation information.

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 “OpenLM Server queries license manager” check box should be cleared.

OpenLM Broker configuration for IBM LUM

1. Download and install the latest OpenLM Broker version. Follow the installation instructions on the OpenLM Broker Application Note.

2. Configure The OpenLM Broker to interface the license server and the OpenLM Server:

2a. The license server name and port number should be configured exactly as they were on the OpenLM Server configuration tool (i.e.: ibm_lum_server and 1515 respectively)

2b. The OpenLM hostname and port (e.g. OpenLM_Server and the default 7016)

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”

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.

IBM LUM denials reports

IBM LUM license denials will be presented in the EasyAdmin web application → 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.

That’s it.

Your OpenLM system is now configured to provide IBM LUM licensing information.

If you require further assistance on this subject, please contact support@openlm.com , and our team will be glad to assist.