Tag Archives: License Manager

Application Note 1035: Configuring OpenLM v1.7 to interface the EasyCopy License Manager

Posted on by

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM (Flexnet), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This application note elaborates the steps required to configure OpenLM to interface the EasyCopy License Manager, and obtain reliable license reports and usage statistics. This capability is available for Easycopy versions 8.7.12 onward.

OpenLM Server configuration

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

  • Click the ‘Add’ button.
  • Set the LM Type to ‘Other’
  • Set the License server’s Time zone (e.g.: Central Time)
  • Type in the Hostname (e.g. easycopy_lm) or IP of the EasyCopy License server.
  • The port number is insignificant here. Type in any number (e.g.: 123). Note that the same number will need to be used in the OpenLM Broker configuration as well (see below).
  • Click the ‘Apply’ and “Restart now” buttons.

OpenLM Broker Configuration

After setting the OpenLM server, the Broker needs to be configured as follows:

  • Please refer to the Application Note 1004: OpenLM Broker quick start guide document for general Broker configuration. In the example below – the OpenLM server hostname was set as openlm_server, the OpenLM Broker port was maintained at its default 7016.
  • The license server characteristics are set exactly as they were on the OpenLM Server configuration tool: The type is set to ‘Other’, the name to easycopy_lm, and the port to 123.
  • Type in the EasyCopy command line in the Broker’s “data_inquiry” command text box. The command is “eclic openlm” and it needs to be run from the location of the eclic.exe path.
  • Click the ‘Apply’ and “Restart Broker” buttons.

What Flexnet version is ESRI ArcGIS using ?

Posted on by

OpenLM monitors FlexLM license managers, for improved Application usage management. Historically – OpenLM was written by ArcGIS users for ArcGIS users, and it is an ESRI partner.

As such, we in OpenLM receive many queries about ESRI ArcGis licensing, one of which is: “What Flexnet publisher version is my ESRI ArcGis using ?”

Well – ESRI has written it all down in this post.
Enjoy.

Troubleshoot Form: OpenLM Server Item 003 (Unable to connect to FLEXlm license server error: -96,7:11004 “Comm. error”)

Posted on by

Title Unable to connect to FLEXlm license server
Category OpenLM Configuration Form
Date Oct 24, 2012
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXera FLEXnet,
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation Clicking the “Check” button for one of the FlexLM license servers on the OpenLM Configuration Form resulted in an error
Trouble shoot process Check License server connectivity configuration.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the FLEXlm license server”. Attempting to connect to the license server resulted in the following message box appearing on his screen:

lmgrd is not running: License server machine is down or not responding. (-96,7:11004 “Comm. error”)

Troubleshoot process

1. Make sure the license manager machine is up and that you could check out licenses from it.

2. Make sure that the hostname , Port number, License Manager type and timezone are configured correctly in the OpenLM server configuration tool. Also, please review this Troubleshoot guide.

3. Check the connectivity between the OpenLM server machine and the license server (using ping or telnet).

4.  Make sure that any security components (Firewall) are not blocking communication on both ends. The OpenLM server uses ports 7012, 7014, 7016, 7017 and 7019. The OpenLM server’s communication with the License server relies on port 7014.

Make sure that the port is open:

 

  • Try disabling the firewall temporarily.
  • Enter “Control Panel”→“System and Security”→“Windows Firewall”→ Advanced settings”.
  • If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:

5. The OpenLM Broker may bypass such communication issues. Install the OpenLM Broker on the license server machine. See this application note for more information: Application Note 1004: OpenLM Broker quick start guide

IBM LUM i4blt command reference

Posted on by

Scope:

Even though the IBM LUM license monitoring tool has decreased in popularity over the passed several years, it is still a widely spread tool for monitoring and tracking license usage of many CAD applications.

The OpenLM license monitoring tool extracts information from a variety of license managers, such as Flexnet / FlexLM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and – of course IBM LUM. OpenLM extracts comprehensive license reports and obtains license statistics for all these lisence managers.

In order to interface the IBM LUM license manager, OpenLM employs the i4blt command.
The i4blt command is very versatile; its usage depends on the attached i4blt flag options. The following document is a reference to some of these flags.

Syntax:

There are several syntax rules to be met:
1. Named strings containing spaces must be presented within single quotation marks.
2. Names are case sensitive
3. Listed values must be presented within double quotation marks, e.g.:
i4blt -lp -n my_server -v “‘Vend A’ ‘Vend B’”
4. Parameters that appear within options are position specific, e.g.: vendor information in the i4blt -E (Enrollment) option include vendor_name, vendor_id, and vendor_password.

Command reference

The following diagram is a reference to some of the main i4blt options. The Yellow rectangle is a complete reference to the primary i4blt command options. the turquoise rectangles contain elaboration for some of these primary options.

Usage examples:

The following are usage examples of the i4blt command. The examples are taken from real workstations, and include genuine usage information. They were cleared of any user identification markings.

i4blt -s -lc

In order to obtain current license usage information, OpenLM employs the i4blt -s -lc option.

i4blt -ln

The list display option with the ‘n’ flag lists the servers which are monitored by the IBM LUM.

i4blt -r1 -e

The r1 report type enables the extraction of  further information. This example shows license related event logging, in this case: license release.

Forward reading

I have found the following links helpful:
From the University of Alberta

A bit about HAL (High – Availability licensing) : i4blt -H.

Application Note 1001_b: Configuring OpenLM to interface the Sentinel RMS license manager

Posted on by

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Sentinel RMS License Manager, and obtain reliable license reports and usage statistics.

Enabling the OpenLM server to work with RMS

In order to configure OpenLM to work with  Sentinel RMS, please follow this procedure:
1. Download lsmon.exe and lsapiw32.dll . These files aren’t included in the OpenLM installation package. For information on how to obtain these files, please contact OpenLM on support@openlm.com.
2. Copy these files to “C:\Program Files\OpenLM\OpenLM Server\LM”
3. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RMS.
4. Type in the full path of the executable file, i.e.:  “C:\Program Files\OpenLM\OpenLM Server\LM\lsmon.exe” in the “RMS executable file” text box.

See the following image for further clarification:

Introducing a new Sentinel RMS server

After configuring the OpenLM configuration tool to work with Sentinel RMS as elaborated above, the user may introduce an new  Sentinel RMS server under the License Servers tab:
1. Select the “License Servers” tab.
2. Select the RMS type from the “Type” dropdown list.
3. Type in a meaningful description in the “Description” text box.
4. Type in the appropriate “Hostname” and “Port” numbers. The Sentinel RMS default port is 5093.
5. Check the “Enabled” check box.
6. Click the “Apply” button. The  Sentinel RMS server is now ready to interface the OpenLM.

OpenLM Broker configuration for RMS

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the RMS license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RMS license manager type from the ‘Type’ dropdown list.
In the port’s Commands list make sure the ‘status’ command is
lsmon <License Server Name>

Document Revision Table

Version Author Date Changes
0.1 Orik May1, 2012 Preliminary
1.0 Orik Jun3, 2012 Revised.
1.1 Orik Jun6, 2012 Added Broker

 

OpenLM Hotfix: Broker version 1.7.2.0 for IBM-LUM and LM-X license managers

Posted on by

The OpenLM Broker version 1.7.20 is a Hotfix version, dedicated for the solution of an issue that was raised by a customer.

Issue description:

The IBM LUM license manager was not configured correctly on the Broker configuration interface, when Java JRE 1.7 was installed on the PC. It was configured correctly for JRE 1.6.

OpenLM recommends to download and install version 1.7.20 of the OpenLM Broker on IBM LUM and LM-X license servers that run JRE 1.7.

Setting FlexLM port numbers statically

Posted on by

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

ESRI ArcGIS 10 Service Pack 4

Posted on by

ESRI has announced the release of ArcGIS 10 Service Pack 4. The new service pack is now available for download from ESRI’s patches and Service Packs download site. Download and installation of the new service pack is straightforward, and the software update runs seamlessly.

As far as OpenLM is concerned, Service Pack 4 does not incorporate fixes to the ArcGIS License Manager. Hence, transition to the new Service Pack should be transparent to OpenLM as a monitoring tool of floating licenses.

Please note that previous Service packs have included fixes to the ArcGIS License Manager. Here is a full list of the issues that were addressed and solved in ArcGIS 10 Service Pack 4, as well as in previous Service Packs.

IBM Rational – FlexNet Token based licensing

Posted on by

IBM Rational license management using FLEXnet

The IBM Rational License Server uses FLEXnet (FlexLM) for licensing IBM Rational products.

FLEXnet main components

The four main components of FLEXnet are:

  • The License Manager Daemon, lmgrd

  • The Vendor Daemon, telelogic

  • The client application program, in this case any IBM Rational application

  • The license file, license.dat

Mode of employment

  • When an IBM Rational product is started, the program uses the TELELOGIC_LICENSE_FILE system variable to find out the name of the computer that’s running the FLEXnet license server and the port that it’s using.

  • The program contacts the license manager on the FLEXnet license server, using the specified port. It requests a floating license and makes the request for the Telelogic vendor daemon.

  • On the FLEXnet license server, the license manager sends the request to the Telelogic vendor daemon. The Telelogic vendor daemon checks to see if any licenses are available.

  • If there are free licenses, the Telelogic vendor daemon grants a license and the program runs. If there aren’t any licenses available, the Telelogic vendor daemon refuses the request, and the program fails to start and displays a license denial message.


Token-based licensing

Token licenses are in fact a form of floating license, only that instead of having a pool of licenses – it has a pool of tokens. When a feature is checked-out, a certain amount of tokens are consumed. The number of consumed tokens is specific to each feature, and is apparent in the feature/Increment line in the license file. When the application is closed, the tokens are returned to the pool for other end users to use.

Advantages of Token licensing

Having the ability to apply the acquired licenses to multiple products is an appealing concept:

  • Customers are not always aware of the full array of features they may acquire. having a token based license scheme ensures customer satisfaction from the license acquisition.

  • As development stages progress, customer needs change. They may require different licensed features, and eliminate the charge of “unused” software.

  • The entire license purchasing method is simplified. Customer can add/try new software during project, without new PO or evaluation process

Rational tools’ token-based licensing

IBM Rational license types

IBM Rational includes the following license types:

DOORS, Synergy, Change, Tau, System Architect, Focal Point, Rhapsody, Publishing Engine, Logiscope and Team Webtop

IBM Rational token license file examples

  • The Increment / Change line marks the number of tokens to be consumed:

INCREMENT Change telelogic 2015.04302 30-apr-2015 1 …

VENDOR_STRING=T10-999999:t,TLSTOK,1.0,Change,5  … // 5 Tokens worth.

  • This is an INCREMENT line indicating the total number of Tokens in the license

file. In this case, it is 200:

INCREMENT TLSTOK ibmratl 2.0 30-apr-2015 200 ISSUER=IBM

Rational License Server 8.1.1

Rational License Server 8.1.1 incorporates all vendor daemons (telelogic, rational, and ibmratl) into one. This change has also been incorporated into multiple Rational products such as ClearCase and ClearQuest.


References

http://publib.boulder.ibm.com/infocenter/rational/v0r0m0/index.jsp?topic=/com.ibm.rational.license.doc/topics/r_lic_log_file.html


http://www-01.ibm.com/support/docview.wss?uid=swg27023414&aid=1

Application Note 1001: Configuring OpenLM to interface the Reprise RLM license manager

Posted on by

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Reprise License Manager (RLM), to monitor license usage and obtain license statistics.

Enabling the OpenLM server to work with RLM

In order to configure OpenLM to work with RLM, please follow this procedure:

  1. Download rlmutil.exe. This file isn’t included in the OpenLM installation package. It can be download from the Reprise Software website: http://www.reprisesoftware.com/enduser_kits/end-user-download.php.
  1. Copy the file to “C:\Program Files\OpenLM\OpenLM Server\LM”
  1. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RLM tab.
  1. Type in the full path of the executable file, should be:“C:\Program Files\OpenLM\OpenLM Server\LM\rlmutil.exe” in the “RLM executable file” text box.

See the following image for further clarification:

Introducing a new RLM server

After configuring the OpenLM configuration tool to work with RLM as elaborated above, the user may introduce an new RLM server under the License Servers tab:

  1. Select the “License Servers” tab.
  2. Select the RLM type from the “Type” dropdown list.
  3. Type in a meaningful description in the “Description” text box.
  4. Type in the appropriate “Hostname” and “Port” numbers. The RLM default port is 5054 (It was 9000 prior to RLM version 6).
  5. check the “Enabled” check box.
  6. Click the “Apply” button. The RLM server is now ready to interface the OpenLM.

OpenLM Broker configuration for Reprise RLM

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the Reprise RLM license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RLM license manager type from the ‘Type’ dropdown list.
In the port’s Commands list, make sure the ‘status’ command is either

rlmstat.exe -c <port>@<server> -a for older RLM versions or 

rlmutil.exe rlmstat -c <port>@<server> -a for newer versions.

Document Revision Table

Version Author Date Changes
0.1 – Preliminary
1.1 Mira; Orik Jun 3, 2012 Revised
1.2 Orik Jun6, 2012 Added Broker