OpenLM Broker Maintenance Release Version 2.0.0.4

The OpenLM Broker version 2.0.0.4 is a maintenance release to version 2.0. It contains some bug fixes to problems found in previous versions.

 

OpenLM Broker version 2.0.0.4 is only comatible with the OpenLM Server version 2.0 and higher.

Upgrading the OpenLM Broker

Download:

OpenLM Broker version 2.0.0.4 is available for download on the OpenLM site.

Install:

In order to upgrade to version 2.0.0.4, just install the new version on top of the older one.

For more information – please see this Application Note:

Application Note (3004b) OpenLM v2.0: Broker Comprehensive Installation Guide

What’s new in OpenLM Broker 2.0.0.4 (May  19, 2014)

Fixes

– 0001772: [Config Tool] Recording time should be in minutes, not hours – resolved.

– 0001798: [Config Tool] There is no way to change the Port description text in the configuration tool. – resolved.

– 0001662: [Config Tool] Broker config tool: bad prompt – resolved.

– 0001844: [Config Tool] Broker config tool on Linux do not load – resolved.

– 0001842: [Config Tool] Can’t read or select long full name of license file – resolved.

 

Please follow and like us:

OpenLM Pre-Release Broker Version 2.0.0.3

The OpenLM Broker version 2.0.0.3 is a maintenance release to version 2.0.0.2. It contains a bug fix to connecting the DSLS license manager. Users that need to access the DSLS license manager using the broker should upgrade their version.

Upgrading the OpenLM Broker

Install:

In order to upgrade to version 2.0.0.3, just install the new version on top of the older one.

What’s new in OpenLM Broker 2.0.0.3 (April  10, 2014)

Fixes:

– 0001679: [Config Tool] Broker command syntax for DSLS is not working  – resolved.

Please follow and like us:

OpenLM Broker Maintenance release version 1.8.2.5

OpenLM Broker version 1.8.2.5

 

OpenLM Broker version 1.8.2.5 is a maintenance release to version 1.8. It contains a bug fix to connecting the DSLS license manager. Users that need access the DSLS license manager using the broker should upgrade their version.

 

What’s new in OpenLM Server 1.8.2.5 (Apr 09, 2014)

 

– 0001679: [Config Tool] Broker command syntax for DSLS is not working – resolved.

Please follow and like us:

OpenLM Pre-Release Broker Version 2.0.0.2

The OpenLM Broker version 2.0.0.2 is a maintenance release to version 2.0.0.0. It contains some bug fixes to problems found in previous versions. We  recommend that users of previous 2.0.0.0 Broker versions to whom these problems may be relevant upgrade their system to this version.

Upgrading the OpenLM Broker

Install:

In order to upgrade to version 2.0.0.2, just install the new version on top of the older one.

What’s new in OpenLM Broker 2.0.0.2 (April  07, 2014)

Fixes

– 0001736: [Config Tool] Broker, Port configuration can not be closed without selecting License File Path  – resolved.

– 0001710: [Config Tool] Unix / Linux Broker installation: non matching paths  – resolved.

– 0001739: [Config Tool] loads empty  – resolved.

– 0001743: [Config Tool] config tool hung up on the vendor configuration page  – resolved.

 

Please follow and like us:

OpenLM Broker Maintenance Release Version 1.8.2.3

The OpenLM Broker version 1.8.2.3 is a maintenance release to version 1.8. It contains some bug fixes to problems found in previous versions. We  recommend that users of previous 1.8 Broker versions to whom these problems may be relevant upgrade their system to this version.

 

OpenLM Broker version 1.8.2.3 is only comatible with the OpenLM Server 1.8.1.13 version onward.

Upgrading the OpenLM Broker

Download:

OpenLM Broker version 1.8.2.0 is available for download on the OpenLM site.

Install:

In order to upgrade to version 1.8.2.3, just install the new version on top of the older one.

For more information – please see this Application Note:

Application Note 2004: OpenLM Broker Comprehensive installation guide version 1.8

What’s new in OpenLM Broker 1.8.2.3 (April  07, 2014)

Fixes

– 0001736: [Config Tool] Broker, Port configuration can not be closed without selecting License File Path – resolved.

– 0001710: [Config Tool] Unix / Linux Broker installation: unmatching paths – resolved.

 

Please follow and like us:

FAQ: Flexera lmgrd log file is very big


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.

 

 

Please follow and like us:

OpenLM Maintenance Release Version 1.7.1.5

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.

Please follow and like us:

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

 

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

OpenLM Broker Upgrade Guide from version 1.6 to 1.7

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

OpenLM Broker Configuration on Windows XP

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.

Please follow and like us: