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

General

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

General
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
Summary

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.

Summary

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.
Please follow and like us:

Problem/Error with AutoCAD network license management: “A valid license could not be obtained by the network license manager”

Details:

You can face above problem frequently on AutoCAD 2007 based products when you are working in an organization where:

  • Concurrent licensing scheme is implemented through server/client networking mode.
  • Network bandwidth is low.
  • Network latency is high or connected through VPN.

All of the products based on AutoCAD 2007 contain licensing enhancements which tend to increase network latency and bandwidth utilization of the network. Therefore, you can face this problem while trying to claim the license of the program from the License Manager Server. Earlier versions of AutoCAD products i.e. older than 2007 release were not observing this problem. In this problem, first you are presented with a FLEXlm license finder dialogue box during license obtaining process followed by a message stating:

“A valid license could not be obtained by the network license manager.

Error [1.5. -15]”

In some other products you can receive a bit different message as given below:

“A valid license could not be obtained by the network license manager.

Error [1.5. -18]”

Reasons for Error:

A network throughput or data rate of the link is the main reason for this error especially in case of heavy applications like AutoCAD 2007. Reasons can be summarized as below:

  • Low Bandwidth of the connection i.e. Dial-up connection or low speed ISDN/DSL connection.
  • High Network Latency i.e. VPN
  • Response waiting time of the application/program

One or more of the above reasons can be the root cause of this problem. This problem has recommended solutions which given below.

Solutions:

  • Recommended solution for this problem is either increase in the bandwidth of the connection or decrease in the network latency or enhancement in both parameters.
  • By modification of the response waiting time counter/value which is used as the last resort for the solution of this problem. This is a stepwise procedure to modify the response waiting time counter. Here is the stepwise procedure for the same:
  1. Right click My Computer and choose properties.
  2. On system property dialogue box choose advanced tab.
  3. Click on the environment Variables
  4. On environment variable dialogue box choose system variables field and hit the new button
  5. A new system variable dialogue box with two fields appears; put “FLEXLM_TIMEOUT” in variable name and put 1000000 in variable value field.
  6. Click OK on all three dialogue boxes to close them
  7. Launch the AutoCAD application

 

 

 

 

 

 

 

 

If the problem persists, increase the variable value in multiples of 1000000 micro seconds and reach to the value which gives you satisfactory communication results.

Please follow and like us:

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”

Details:

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.

Solution:

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.

Please follow and like us:

Mac OS X – changing hostname is causing FLEXlm error

Using Mac OS X, the hostname of the workstation is changing depending on the network connection status. When disconnected from the network such a workstation will report the hostname as mac1.local, instead of the actual hostname.

This behavior is causing problems when such a workstation is also the FLEXlm server. When disconnected from the network the server the name is changing, causing a FLEXlm error. The license can not be used on the local workstation running FLEXlm.

This problem and a simple solution is reported on Deelip Menezes interesting Blog.

The most simple solution is to use 127.0.0.1 as a hostname. If the license is only used on that workstation, it is a good solution.

If the license is also used by other users then we recommend to install the license on another machine on the network. In that case, the MAC OS machine can borrow the license when it needs to disconnect from the network.

Autodesk announced few month ago on the support of Autodesk on Mac. Autodesk is joining other companies such as Siemens that already supports this operating system. As the use of FLEXlm licensed systems on Mac OS extends the need to solve this problem becomes more important.

Please follow and like us:

ArcGIS Version 9.3 and Windows 7

Installing ESRI ArcGIS Version 9.3 on Windows 7 can be a frustrating task because of problem with the registry size limit.

We faced the problem after trying to install Autodesk Map 3D on a Windows 7 machine already running ArcGIS 9.3 and another with Microsoft Visual Studio and ArcGIS 9.3.

The Autodesk Autocad (With concurrent network license using FLEXlm) installation failed at the same point on both computers. Searching the Internet for this problem suggested that the problem is related to the registry size. A helpful thread that contains this information is located at http://forums.esri.com/Thread.asp?c=93&f=1148&t=287391

The symptoms of a full registry are:

  • Software installations on the machine fails without a clear error message (In our case it was: “Micro​soft Visual C++ 2005 Redistributable Failed Installation aborted, Result=1603” when we tried to install Autocad Map 3D 2011)).
  • Windows components appears empty at the “Turn Windows on or off” window.

The weird fact is that the installation of ESRI ArcGIS 9.3 is adding the registry limit.
After running the installation of ESRI ArcGIS the registry key is added to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\RegistrySizeLimit with a limited value.

Our guess is that it was probably added to enlarge the defaults for older windows versions. As far as we know this key was removed in the new versions (see here: http://support.microsoft.com/kb/292726/)

The solution is (running as administrator):

  • Open the Windows 7 Registry using the command: regedit
  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control and locate the key: RegistrySizeLimit. Change its value to ffffffff (no limit) and then reboot the machine.
  • Run the command ” SFC /SCANNOW” on command line (with administrator rights)

This may solve many other Windows 7 problems as well.

Please follow and like us: