Tag Archives: openlm broker

FAQ: Flexera lmgrd log file is very big

Posted on by


The lmgrd log file collects all license check out / check in activity. This log would continue to increase in size and as long as the licensed service is running.

The log is cleared when the licensed service is restarted.
This can be done via Flexera’s LMTOOLS UI.

On The “Services/License File” tab choose the licensed service. e.g.: Autocad.

On the “Config Services” tab – you can view the log (e.g: Autocad.log) and its path.

On the “Start/Stop/Reread” tab, use the marked buttons. This would clear the service log file (Autocad.log) and restart logging.

One of the advantages of the OpenLM system is that the accumulation of large amounts of data in this log file is made redundant. The OpenLM Broker is a component in OpenLM’s system which reads the licensed log file, and reports its content to the OpenLM server. There this information is processed and exhibited in a clear and negotiable manner.

 

 

OpenLM Maintenance Release Version 1.7.1.5

Posted on by

OpenLM Maintenance Release Version 1.7.1.5:

Version 1.7.1.5 (Broker version 1.7.1.6)

Version 1.7.1.5 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

This maintenance release includes a more advanced version (1.7.1.6) of the OpenLM Broker.

Upgrading

In order to upgrade to version 1.7.1.5:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window. Some of our customers experienced “error 1001″ as a result of not closing this window.
  4. Install the new version on top of the existing one.

New in version 1.7.1.5:

OpenLM Server:

  1. Fixed in License activity: Counting produced an exception when the request contained a Vendor name.
  2. Fixed in OpenLM Server Configuration Form: Clicking the grid title when the servers’ grid was empty produced an exception.
  3. Fixed: Option file policy settings was not saved.
  4. Fixed: OpenLM Service doesn’t load on machine startup.
  5. Easyadmin – when there is only one option file it becomes the default.
  6. Error for SQL Server users when sorting by last user in workstations window (Bug #328).
  7. Easyadmin Active Agent window (EasyAdmin → Administration → Active Agent): fixed visualization problem in spinner field (Bug #329).
  8. Configuration form – crashed when deleting empty server (Bug #332).
  9. AD Synchronization feature – Users are enabled to select which attribute would be used as a synchronization field between LDAP and the licensing system (Active Directory, post or pre win 2000 username Bug #189)
  10. AD Synchronization bug fix: Synchronizing group names longer than 50 characters.
  11. Feature in EasyAdmin “License Usage” report: Show more details: server, vendor, feature. (Bug #323).
  12. Fixed: Multiple License draw for the same user and workstation is not reported correctly (Bug #335).

OpenLM Broker (1.7.1.6):

  1. Fixed Linux permissions problem in setup.
  2. Improved the interface of the license server detection process (Bug #278).
  3. Removed quote marks (“”) from the command line (Bug #27).
  4. A The broker command template is ready for the user at the beginning of the configuration (Bug #293).
  5. Use the term “OpenLM Server” instead of “Server” in the Broker configuration window (Bug #296).
  6. Feature: Facilitate global update of the Broker commands’ path to all the commands of a specific port.
  7. Fixed installation problem: Support installation on top of java 64 bit version. A 32bit version installation workaround is no longer required.
  8. Add pane to installation, explaining about the configuration tool, to prevent confusion.
  9. Improve the automatic detection of licese servers.

Note:
After upgrading the OpenLM Server version, you may experience problems with the “Licenses” window in the Easyadmin web application. In this case, open the “User Settings” window, click the “Clear Settings” button and “OK” for the problem to be resolved.

Trouble Shoot Form: Broker Item 003 (LUM licenses don’t show up in EasyAdmin)

Posted on by

 

Title LUM licenses don’t show up in EasyAdmin
Category Broker
Date Nov 11, 2011
Handled by
Relevant Links http://bug.openlm.com/view.php?id=225
Applies to license managers LUM
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms LUM licenses don’t show up in EasyAdmin.
Observed during dubug 1. The Broker was not sending any information to the OpenLM Server
2. The Broker “test connectivity” button clicked: Broker saw the OpenLM Server OK.
Trouble shoot process 1. Upgraded Broker version.
2. Changed the I4BLT.EXE path from the OpenLM folder to one supplied by the application vendor.
Solution Found (Found/Pending/Known Issue)

Symptom

LUM licenses don’t show up in EasyAdmin.

Solution

1. Upgrade the OpenLM Broker on the license server machine. Refer to the Application Note for reference.
2. As part of the OpenLM package, the latest version of the I4BLT.EXE file is supplied. This file may not be inter-operable (version too new) with the licensed application version. If this is the case, please follow these steps:

Changing a single port’s configuration

  1. Open the OpenLM Broker configuration tool.
  2. Select the relevant License server.
  3. Check the “Update to the following path” radio button
  4. Click the “Edit” button. The text box becomes active.
  5. In the “Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.

This configuration change may also be achieved by individually typing the I4BLT.EXE file path in each Broker command text box.

Changing all ports’ configurations

  1. Open the OpenLM Broker configuration tool.
  2. Click the “Advanced Settings” wrench icon. The Advanced settings window opens.
  1. Click the “Edit” button. The text boxes become active.
  2. In the “I4BLT Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.
  1. Select a specific port’s “Commands” list item. The “Commands” window opens.
  1. Check the “Update according to advanced settings” radio button, and click the “Update” button. The I4BLT path of the specific port is changed.
  2. Repeat steps 5 & 6 for all ports.

Application note 1004: OpenLM Broker Quick start guide

Posted on by

Scope

This document presents the OpenLM Broker software module. It elaborates the module’s installation process, and conveys basic information regarding the OpenLM Broker’s functionality and configuration options.

General

The OpenLM Broker tool is a Java software module installed on the License Manager Server. The Broker interacts directly with the License Manager Server, initiating queries in order to get the current License Server status. It communicates the answers to these queries to the OpenLM Server.

Being a Java component, OpenLM Broker can run on any Java-supported platform. It can be installed on any platform that is supported by the license managers that work with OpenLM; i.e.: FLEXlm (FLEXnet), IBM LUM, HASP, Sentinel RMS, RLM and more.

The OpenLM Broker provides the following services to the OpenLM server:

  • Sending license usage information from the license manager to the OpenLM Server.

  •  Reading the information in FLEXlm debug log files and pushing it to OpenLM Server.

  • Reading and Editing the FLEXlm option files information from the OpenLM EasyAdmin interface.

  • Starting/Stopping/ of the license server.

At the time of writing this revision (Rev 1.3), the installation of the OpenLM Broker on Windows license servers is easier than for Unix license servers. This is because the Windows installation incorporates an automatic configuration software. This software automatically detects the license servers installed on the machine, and configures the Broker accordingly.

Regardless of this, manual configuration is comprehensive, and includes all the options implemented by the automatic configuration software available for Windows platforms.


OpenLM Broker – Installation Guide

The OpenLM System components are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.7 section

 

Unix/Linux

 

In order to install the OpenLM Broker module on Unix/Linux platforms:

  1. Please go over the installation prerequisites for the OpenLM Broker.

  2. Download the Broker for Unix/Linux from the OpenLM version 1.7 section.

  3. The installation requires root user privileges.

  4. cd to the folder that contains the setup file

  5. Run the following command:

sudo ./openlmbroker-linux-install

 

In order to run the Broker configuration tool, type in the following command:

sudo <location_of_java_runtime> -jar <Installation_folder>/BrokerConfigurator.jar -setup

e.g.:

sudo /usr/bin/java -jar /usr/local/openlm/broker/BrokerConfigurator.jar -setup

The broker is not run automatically after restart. In order to start the Broker service, follow these steps:

  1. cd to the installation folder

  2. Run the following command:

sudo <location_of_java_runtime> -jar <Installation_folder>/OpenLMBroker.jar

start <Installation_folder>/broker.xml

e.g.:

sudo /usr/bin/java -jar /usr/local/openlm/broker/OpenLMBroker.jar start /usr/local/openlm/broker/broker.xml

  1. Do not close the terminal.

  2. After configuration changes, the Broker needs to be restarted.

In order to uninstall the Broker:

  1. cd to the installation folder

  2. run the following command :

sudo ./uninstall

 

Windows

 

In order to install the OpenLM Broker module on Windows platforms:

  1. Please go over the installation prerequisites for the OpenLM Broker on the OpenLM site.

  2. Download the OpenLM Broker for windows from the OpenLM version 1.7 section (see above), and follow the installation instructions.

  3. When installing a Broker on a 64bit Windows system, with a JRE version for 64bit installed, the following “Browse for Folder” window appears:

Please select the jre6 (or higher) folder and click OK.

For both operating systems:

When the installer finishes its installation procedure it launches an automatic configuration tool. This tool automatically detects the settings of the license mangers installed on the machine. In most cases, all that is left for the user to do is to configure the receiving OpenLM server parameters.

At the time of writing this revision (Rev 1.3), The existence and location of an Option File is not automatically configured. Setting its name and path remains to be done manually.


OpenLM Broker – Configuration Tool

 

OpenLM Servers – Adding a Server

The “Servers” folder holds a list of the designated receiving OpenLM Servers. In order to add an OpenLM server, do as follows:

  1. Mark the “OpenLM Servers” directory icon.

  2. Click the green “Add” icon

  3. Select “OpenLM Server” from the selection list.


OpenLM Servers – Configuring the Server

  1. Select the OpenLM server targeted for configuration (i.e.: localhost:7016). The “OpenLM Server Connectivity” form appears on the right-hand side of the window.

 

  1. Configure the OpenLM Server’s parameters:

  • OpenLM Server: The server’s name or IP address (e.g.: localhost).

  • Port: The OpenLM port dedicated for the Broker (7016 by default). This is the same port number as appears in the “OpenLM Server Configuration” tool, under the “Port Settings” tab, in the “License Managers Reporting Port” text box.

  • Sending Timeout: The Broker’s sending timeout limit (e.g.: 45 sec).

  • Active: Check this box in order to enable the Broker’s communication with the OpenLM Server (Enabled by default).

  • The “Check connectivity to OpenLM Server” button literally performs a connectivity check. The function of this button is similar to that of the “Check” button in the “OpenLM Server Configuration” tool, under the “License Servers” tab.


License Servers – Add a license server

Upon start-up, the Broker recognizes all License Servers, and displays them under the “License Servers” folder on the left of the screen.

The user may add any number of License Servers. In order to do so, please perform the following actions for every additional License Server.


  1. Select “License Servers” on the left side of the screen.

  2. Click “Add”. A drop-down list appears.

  3. Select “License Server” from the list. The right-hand side of the Broker configuration window changes.

  4. Type in and enter the Description and the Host Name / IP of the new License Server

License Servers – License Manager Port


  1. Click on the “Port …” bullet under the new License Server key symbol. The “License Manager Port” form appears on the right-hand side of the Broker Configuration window.

 

2. Fill in the License manager port parameters:

  • Port Number: This Number is the same as the one configured in the “OpenLM Server Configuration Window”, under the “License Servers” tab.
  • Description: This is a free text name or description of the License Server.
  • Keep Alive Interval: A number representing how often the server sends messages to the OpenLM Server, in seconds. It is recommended not to change the 10 seconds default value.
  • Type: Type of the License server (e.g.: FLEXlm, IBM-LUM, LM-X).
  • Active: The License manager’s activity status check box. Keep it checked as is by default.
  • Click the “Apply” button on the bottom-right corner of the Broker Configuration window to accept the new License Server’s configurations.

License Servers – Log Files.

Click the “Log Files” bullet under the License server, and select the required log file name (e.g.: “Log File 1”). The Log file definition form appears on the right-hand side of the OpenLM Broker Configuration Window.

 

  1. Description: Name of the new License Server’s log file

  2. Path: Fill in the Path on which to locate the License Log file.

  3. Type: The log file type. At the time of writing this revision (Rev 0.1), the debug log type is the only type supported. Other log file types may be supported on later versions.


It is recommended not to change any other of the default values presented in this form.

License Servers – Vendors

Click the “Vendors” bullet under the New License Server Key icon, and a specific vendor bullet from the vendor bullets’ list. The vendor Definition form appears on the right-hand side of the “OpenLM Broker Configuration Tool” window. This form handles the specific vendors’ License and Option files.


  1. Vendor Name:  Vendor’s name (e.g.: ARCGIS, adskflex, ptc_d, MLM, ugslmd)

  2. License: The license file is the one supplied by a specific vendor, stated with its full path.

  3. Option File Description: A descriptive name of the user’s choice (e.g.: my_OptionFile).

  4. Option File Path: The option file related to the vendor, stated with its full path.

  5. Watch Option File: This should be checked for the Option File to be effective.

  6. Watch interval: The Interval at which the Option File is read. It is recommended to keep the 600 sec default value.

 

License Servers – Commands

The “Commands” menu sets the path to License manager commands. These commands are License Manager specific, and the paths for these commands may be set for each License server or vendor (port) individually.


Upon installation, the default search path for FlexLM commands would be automatically detected through the system registry. Other license managers’ commands’ paths (e.g.: IBM LUM) are set by default to: C:\Program Files\OpenLM\OpenLM Broker\tools\

 

Changing command paths

Click the “Commands” bullet under the New License Server’s Port icon. The “Commands” window opens on the right hand side of the Configuration tool window.

There are 3 options for changing the command paths:


  1. In order to set all the License manager’s commands for a specific license manager type (e.g. FlexLM), check the “Update according to Advanced Settings” radio button and click the ‘Update’ button. This applies the globally declared License manager’s command paths listed in the “Advanced settings” menu (marked by the wrench icon) on the selected port.

  2. In order to set all the License manager’s commands of a certain vendor (port), check the “Update to the following path” radio button, fill in the required path in the adjacent text box, and click the ‘Update’ button.
  3. In order to change the path for a specific License manager command to a specific vendor (port), click on the specific command (e.g. Status), change the command path in the “Command line” text box, and click the “Restart Broker” button.

In any case – the updated command path would be visible in the specific command window, as elaborated below.

Individual commands

The user may edit individual command paths and parameters:

 

status

  1. Click the “Status” bullet under the “Commands” bullet. The “Status” command definition form appears on the right-hand side of the window.

  2. The default command line calls the command according to the selected license manager type. This command queries the License Server for its status: is it up and working or idle. For example, for FLEXlm the system is using the lmutil lmstat command, for IBM LUM it uses the i4blt command.

  3. It is recommended not to change any other of the default values presented in this form.

Data Inquiry

  1. Click the “Data Inquiry” bullet under the “Commands” bullet. The “Data Inquiry” command definition form appears on the right-hand side of the window.

  2. The default command line is set to send the queried license usage information periodically from the Broker to the OpenLM Server.

  3. The period time is set by the “Interval” parameter.

Start and Stop

  1. Click the “Start” or “Stop” bullets under the “Commands” bullet. The respective command definition form appears on the right-hand side of the window.

  2. The start and stop commands literally start and stop the the License Manager Server’s activity.

Reread

  1. Click the “Reread” bullet under the “Commands” bullet. The “Reread” command definition form appears on the right-hand side of the window.

  2. The command line sets the Broker to update the Option File stated in the License Management Server, by new data inserted by the EasyAdmin OpenLM server application (e.g.: new available licenses).

Save Option File

  1. Click the “Save Option File” bullet under the “Commands” bullet. The respective command definition form appears on the right-hand side of the window.

  2. This command enables the user to save the option file upon demand.


Advanced Settings

The advanced settings form handles vendor specific supplied executable files.


  1. Click the wrench icon (highlighted blue) . The “Advanced Settings form appears on the right hand side of the window.

  2. Set the Advanced settings’ parameters:

    1. LMUtil Path: This is the path for the FlexLM supplied executable file.

    2. i4blt Path: This is the path for the IBMlum supplied executable file.

    3. lmxendutil Path: This is the path for the LM-X supplied executable file.

    4. Log levels: Set the Log file’s notification level; i.e.: Should it only present Error messages or more verbose information.


Revision 1.3: July 10 2012.

 

OpenLM Broker Upgrade Guide from version 1.6 to 1.7

Posted on by
OpenLM Broker is a tool on the license server. This optional but highly recommended program significantly enhances OpenLM System capabilities.

Although the upgrade process of OpenLM components is usually fully automatic, the transition from OpenLM Broker version 1.6 to version 1.7 is more complex. Thus, some manual steps are required in order to preserve your settings.

In order to preserve your current configuration, you must follow these steps:

  1. Save your broker configuration. To do this, copy the ‘broker.xml’ file from the broker installation folder, whose default location is “C:\Program Files\OpenLM\OpenLM Broker,” to a temporary folder.
  2. Download  the OpenLM Broker 1.7 installer from our download area.
  3. Run the installation package. Removing the previous installation is uneccessary, as it is a standard ‘Next-Next’ installation.
  4. At the end of the installation process, the “OpenLM Broker Configuration Tool” will pop up.
If your configuration was saved:
  1. Click ‘Servers’ on “OpenLM Broker Configuration Tool,” and select “Add.”
    Complete the fields as illustrated in  in the following image:
  2. Apply your changes.
  3. Exit the configuration tool.
If your configuration was not saved:

Please close the “OpenLM Broker Configuration Tool.”

  1. Open the “Openlm Broker” Folder and replace the new ‘broker.xml’ file with the copy you made earlier.
  2. Open “Openlm Broker Configuration’” from the start menu and then click “Servers.” Choose “Add,” and fill in the fields as shown in the following image:
  3. Apply your changes and click “Restart Broker” to restart the broker service.
  4. Exit the configuration tool.

OpenLM Broker Configuration on Windows XP

Posted on by

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 1.6.0.6 of OpenLM Broker.