OpenLM Version 1.7.1.2 – Maintenance release

Posted on September 26, 2011 by rachel

Version 1.7.1.2 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.7.1.2?

OpenLM Server:

Easyadmin – fix licenses window visible columns problem.
Easyadmin – fix blinking LED problem for broker status.
Easyadmin – fix some issues where using permissions and there are denied servers.

Note: After upgrade, you may experience problems with “Licenses” window in easyadmin. If this is the case, open “User Settings” window, click “Clear Settings” and click “OK” for the problem to be resolved.

OpenLM Broker:

Add multi target OpenLM Servers.
Some bug fixes.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001″ which is related to a problem with Windows):

Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
Stop the OpenLM Server service
Make sure to close ALL windows, especially the services window
Install the new version on-top of the existing version

Application Note 1005: Configuring OpenLM to close idle Licenses

Posted on September 19, 2011 by orik

Scope

The OpenLM License management tool provides two capabilities; One is the extraction of license statistics and license usage reports. The Other is the capability to either save and close or suspend idle licensed processes. This document goes into the details of these features; it elaborates their capacities and required configuration.

General

Suspend and Resume

The basic idle process management method is the “Suspend and Resume” method. This method detects an idle process, identifies its respective license, releases the license into the common license pool, and “freezes” the application until the license is reclaimed. This method is a global one, intended for all sorts of licensed applications. At the time of writing this revision (Rev1.2) the “Suspend and Resume” method is supported for FLEXlm licensed applications.

Save and Close

Another idle process management method is the “Save and Close” method. In this method, an idle station is identified, the user’s work is saved, and the application is actively shut down altogether, not just suspended (as in the case of the “Suspend and Resume” method).
At the time of writing this revision (Rev 1.2), the “Save and Close” feature is reserved for three specific licensed application vendors: ESRI (vendors of ArcGIS), Autodesk (vendors of AutoCAD), and MathWorks (vendors of Matlab). These applications are named by convention “Extension Supported” applications.

Controlled workstations

Workstations are labeled as “Controlled” when they fulfil two conditions:

An “Active Agent” is installed and running on these stations
Both the License Server and the “Active Agent” report drawn licenses of “Extension Supported” applications.

Controlled workstations facilitate the “Save and Close” method of license retrieval. The indication of workstations as “controlled” is present as a green ‘V’ on the “Workstations” window in the EasyAdmin web application:

The “Active Agent” software module

The software module that interfaces the managed application directly, and enables either one of the idle processes’ management methods is the “OpenLM Active Agent” software module. This software module is optional, and its license should be acquired independently from the OpenLM basic software package. Please contact support@openlm.com for further clarification.

OpenLM Active Agent

As mentioned above, the software module that interfaces the managed application directly is the “OpenLM Active Agent” module. This module must be installed in the end user’s computer, In order to apply either one of the application management features mentioned above (“Suspend and Resume” or “Save and Close”).

Installing the Active Agent:

The OpenLM Active agent may be downloaded from the “Downloads” section of the OpenLM main site: http://www.openlm.com/index.php/component/docman/doc_download/75-openlm-active-agent
During the installation process, follow these steps:
1. Go through the standard download forms and procedures (Run the installation, read and accept the License Agreement etc.)
2. If an Extension Supported application was identified as installed on the computer, the “OpenLM Extensions” dialog window appears.

The user may either:

Select to install the appropriate software extensions, thus ruling an idle application to be treated in the “Save and Close” method, or
Select NOT to install the appropriate software extensions, thus ruling an idle application to be treated in the “Suspend and Resume” method, even though it is an “Extension Supported” application.

3. In the “Agent Configuration” dialog window, type in the OpenLM server with which the Agent is required to connect, and click the “Apply” button.

“Suspend and Resume” an Idle application

An idle application is treated in the “Suspend and Resume” method (as opposed to the “Save and Close” method) if it is:

A NON “Extension Supported” application, or
An “Extension Supported” application, upon which the application’s extension was not installed during the Active Agent’s installation (see Active Agent’s installation, above.)

In any such case, the linkage between the application’s process and its respective license needs to be manually established.

Process to License Link

In order to Establish a link between the monitored process and its respective license
follow these steps:
1. Find the process’ ID and exact format Name:
a. Click the Windows “Start” button
b. Select “All Programs” → ”OpenLM” → “Agent” → “Tools” → “Processes List”. The following “Processes” table window appears.

c. Find the required process and copy its exact format name.

2.    Open the Easyadmin tool
3.    Press the Easyadmin start button (On the bottom right corner of the Easyadmin window). A selection menu pops up.
4.    Select Administration. The Following window Appears

5. Select the Process / Features icon. The following window appears:

6. In order to add a new process to the currently managed processes’ list, click the “Add” icon in the Process List frame, on the left-hand side of the “Process features” window.
The following window appears:

7. Type in the required data:

The “Process name” as obtained in bullet #1 above, e.g: ArcMap.
A verbal description of the managed process, and
The application’s Vendor name as appears at the license file. e.g.: ARCGIS

8. Check the “Enabled” box.
9. Click ‘Add’, and add in the new application’s features.
The user may choose to do so automatically by clicking the “Add Vendor” green ‘+’ sign on the right side of the “Process features” window,
or by selecting each feature separately by clicking the “Add” green ‘+’ sign right next to it.

After completing the process described above in paragraphs 1 through 10, the Active Agent is ordered to monitor the managed process.

Setting the Active Agent’s preferences

The Active Agent’s preferences configure different aspects of the Active Agent’s intervention in a managed application’s operation. I order to configure these preferences, go through the following steps:
1. Open the Easyadmin tool.
2. Press the Easyadmin start button (On the bottom right corner of the Easyadmin window). A selection menu pops up.
3. Select Administration. The “Administration”window Appears.

4. Select the Active Agent icon. The “Active Agent” window appears:

5. Set a number in the range of 0 to 100 for the “Start releasing licenses after …” parameter. This number is the threshold over which idle licenses would be marked for releasing.
This threshold is presented as a percentage of the overall number of licenses of that specific application.
6. Set the “Minimum idle time before client is released” parameter. This parameter literally means that once the release threshold has been surpassed, and a license has been identified as idle, a timer is being set. once this timer is surpassed, the license would be freed.
7. The other parameters in the “Active Agent” window literally present system resource thresholds that determine the state at which a process is at, i.e: active or idle.

“Save and Close” an Idle application

An idle application is treated in the “Save and Close” method (as opposed to the “Suspend and Resume” method) if it is an “Extension Supported” application, upon which the extension installation was NOT cancelled during the Active Agent’s installation (see Active Agent’s installation, above.)
In such a case, the linkage between the application’s process and the specific license it drew from the license pool is automatically established. For this reason the actions taken in the “Process to License Link” section (above) are redundant in case of “Save and Close”-ing an idle application.
Setting an Active Agent’s preferences is done the same way as in the “Suspend and Resume” method described above.

Extension dedicated functions

The Active Agent window’s “Extension Dedicated” label contains several functions that are extension specific, i.e. intended solely (at the time of writing this revision, Rev 1.2) for managing Matlab, ArcGIS and Autodesk applications. The “Extension dedicated” tab incorporates three bars entitled:

Handling extensions,
Software items that will not be saved nor reported when closed and
List of Directories for which projects will not be saved when closed

Note: OpenLM recommends keeping the extension dedicated preferences at their default values, as this should be considered an advanced users’ section.

The Handling extensions bar

Folder to save closed projects:

Self explanatory.

Overwrite existing projects

Checked (Default): The same file name is used for project saving each time the application is detected as idle and closed.
Unchecked: Each recurrence of an idle application closing event brings about the creation of a new copy of the saved project.

Show extension list at software start up

Checked: The application’s extension list is shown when the application is restarted after detected as idle and closed. This is useful for manually prompting users to confirm their usage of a certain extension.
Unchecked (Default): The application’s extension list is NOT shown when the application is restarted after detected as idle and closed.

Turn off licensed extensions at shutdown

Checked (Default): Extensions that require licenses are closed together with the idle application. This requires the user to obtain a license for the extension when restarting the application.
Unchecked: Extensions that require licenses are NOT closed together with the idle application.

Turn off custom extensions at shutdown

Checked (Default): Extensions that do NOT require licenses are closed together with the idle application. This requires the user to obtain a license for the extension when restarting the application.
Unchecked: Extensions that do NOT require licenses are NOT closed together with the idle application.

Application’s behavior when extension passes usage threshold

There are two methods of operation to deal with an event in which an application was NOT compelled to close according to the Active Agent’s preferences, but a licensed extension that is embedded in that application WAS compelled to close. These two optional operations are either turning off the extension, or shutting down the application altogether.

Solve license manager errors

Checked (Default): The Active Agent employs an algorithm to solve license manager errors (e.g.: hung up license).
Unchecked: This algorithm is not activated

Actively shut open applications down at …

Checked: The Active Agent actively shuts down all the applications, and frees all licenses on a given time, in accordance with certain company policies.
Unchecked (Default): No such shut-down is set.

Hide ‘Set ArcGIS License Level’ from agents

ArcGIS comprises of three usage license levels: ArcInfo, ArcEditor and ArcView. The vendor allows a selection of required level of usage license, however the Active Agent incorporates an elementary GUI to set this level (See following image).

This option may be presented or hidden from the user according to the selection of this check box.

Checked: The ArcGIS license level GUI is NOT presented to the user.
Uchecked (Default): The ArcGIS license level GUI is presented to the user. In order to view it, right click the OpenLM Agent icon (Marked by the black ellipse). “Set ArcGIS License level” appears on the top of the pop-up menu (Marked by the red ellipse).

The “Software items that will not be saved …” bar

This bar lists a number of objects that would not be saved when the application is closed ; e.g.: ArcCatalog.exe is a file browser which holds no substantial data at its own right, and therefore is not saved.

The “List of Directories for which …” bar

This bar lists directories onto which no changes would be made upon application automatic closure. This is intended for projects that should keep the same static information every time they are started.

Revision 1.3, Jun 05, 2012.

Application note 1002: Agent connectivity and application closure issues

Posted on September 18, 2011 by orik

scope:

This document is a constantly updating troubleshoot guide for OpenLM’s Agent module issues. It offers solutions for Agent problems in the following categories:

Connectivity issues.
Application Closure via the ‘Active products’ tab.
Agent refuses to release license even though the user is in idle state.

Connectivity issues

Connectivity issues can be caused by the following reasons:

Incorrect server name or address
Firewall blocks the OpenLM Server or the Agent port.
A proxy server blocks the Agent requests.

If you encounter connectivity issues, Please act according to the following checklist:

Make sure that the server name and address are correct.

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:

If connectivity issues persist, and a Proxy Server is configured on your machine, ensure that it is not blocking the OpenLM server; Open the OpenLM Agent Configuration window and uncheck the “Use local computer’s proxy settings” box as depicted below:

Troubleshooting automatic license release issues

General:

OpenLM supports several methods of controlling active licenses. These include:

Two modes of application closing

Suspend and Resume mode: Suspends the session and releases the license on the server side. When the user resumes work, the license is retaken (if still available) and the application resumes from the same position it was suspended.

Save and Close mode:Save and close the active session, and release the license for other users. The OpenLM Active agent fully closes the licensed software.

Three configuration options for closing sessions of licensed software

Automatic release: The administrator can set a time for a license to return to the license pool.

Administrative close: The administrator can close an application using the “close application” icon on the “Active Products Tab”. This option only supports the “Save and Close” method mentioned above.

Scheduled close: The administrator can set a time on which all active sessions will be be closed and their relevant licenses be released back to the license pool. This option only supports the “Save and Close” method mentioned above.

The OpenLM Agent extension requirement

The OpenLM Extension is a software module that enables OpenLM to provide dedicated services to specific software platforms (Please consult the OpenLM support page for information on supported platforms). The Save and Close mode is only applicable if the OpenLM Agent extension was installed as part of the OpenLM Agent installation.

Furthermore, the Save and Close method is only supported for ESRI ArcGIS Desktop ArcGIS and Autodesk software applications. In order to ascertain whether the OpenLM Agent extension is installed on either of these two platforms, please follow these actions:

ESRI ArcGIS Desktop ArcGIS: Click the “Customize” tab → Select “Extensions”. Confirm that “OpenLM Arcgis Extension” appears in the Extensions list.

Autodesk software: The Save and Close mode is supported for any Autodesk software application. In Autocad Map 3D, for example, type in the “OLM” command at the bottom of the AutoCAD window. If the OpenLM Agent extension was installed, you should get a message such as depicted below:

If the Extension is not installed, an Error message should appear, stating that the “OLM” command is not recognized.

The OpenLM Agent Extension installation

In order to install the OpenLM Agent extension installation, please refer to this guide.

Further causes for application closure failure

Applications may normally be closed manually by an administrator through the EasyAdmin tool:

Open the “OpenLM easy admin” window.
Click “Active products” (see image above).
Find the current open session of the program on your machine.
Click the “Close Application” button.

If an application fails to close via the close application button, please try the following actions:

Server Side fault: License server configured incorrectly.

Open the OpenLM server Configuration window.
Configure the License Server in the License Server Settings by adding a new license manager, entering the IP address or the name of the license server, and the port ( usually 27000 \27004 ).

Installation fault: The agent is not installed correctly.

Remove the Agent using the “Program files” → “Add/Remove programs” application.
Download the latest version of the Active Agent (as opposed to the Utilizer Agent) from OpenLM’s downloads area, and review our agent installation guide.

Revision table

Revision	Author	Date	Remarks
0.1 – Preliminary		Sep 12, 2011
1.0	Mira; Orik	Sep 14, 2011	Revised
1.1	Orik	Oct 03, 2011	Added GIS Image
1.2	Orik	Jan 22, 2012	Minor fixes

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

Posted on September 18, 2011 by orik

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:

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.

Copy the file to “C:\Program Files\OpenLM\OpenLM Server\LM”

Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RLM tab.

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:

Select the “License Servers” tab.
Select the RLM type from the “Type” dropdown list.
Type in a meaningful description in the “Description” text box.
Type in the appropriate “Hostname” and “Port” numbers. The RLM default port is 5054 (It was 9000 prior to RLM version 6).
check the “Enabled” check box.
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

Application Note 1003: OpenLM Grouping tool

Posted on September 18, 2011 by orik

Scope

The Group Reporting Interface facilitates a flexible method to define groups of users based on the active directory database of the organization, and query the OpenLM server to get license usage reports for these groups.

The Group Reporting Interface serves as an extension to the groups and projects capabilities on the “Active Directory” tab in the OpenLM server configuration tool. It demonstrates enhanced flexibility, and usage history logging.

Configuring the Group Reporting Interface

Server settings configuration

Open the “OpenLM Grouping Tool” application.

Select the “Settings” tab.
Type in the OpenLM Server; Enter either its IP or Host Name.
Type in the OpenLM Server Port. This port number is the same as the “User interface http server port” set in the “OpenLM Server Configuration” tool under the “Port Settings” tab. Its default value is 7014.
Click “Save” to save the new settings.

Notes:
1. Throughout the “OpenLM Grouping Tool“, the user may click the “Cancel” link in order to return to the previously selected window. Specifically in the “Settings” window, clicking “Cancel” would lead the user back to the “OpenLM Grouping Tool” main window.
2. Click the “Check Connectivity” link in order to perform a connectivity test with the OpenLM server.

Active Directory domains setting

1. Click the “Domains” tab.
2. Press “Add”, and type in the available Active Directory domains in the organization.
3. Click “Connect” to test and save the added connection.

Domains may also be edited by clicking the ‘Edit’ tab. In such case – the Domain window will reappear for editing:

Defining Groups – Organizational units.

This tab enables the user to connect to an Active Directory and to define groups of users. The usage report produced from the tool will be based on these groups. In order to add a group of users, go through the following action list:

1. Select the “Define Groups” tab, and click “Add”. The “New Group” dialog window appears.
2. Type in a meaningful name to the new group in the pink background text box.
3. Select a criterion for the required filtered selection of the organization’s data, e.g.: “From Organizational Unit”.
4. Select a Domain name from the “Domain” drop down list. If no such domain exists, click the green ‘+’ symbol adjacent to the “Domain” drop down list. The “New Domain Connection” window appears, and the user is prompted to present a new domain(see further below).
5. Click “Refresh” in the “Filtered Users” area. The users that fit the filter conditions are shown.

6. Filters may be applied to this pool of users. These filters use ‘AND’ logic, i.e. – all conditions must comply in order for a user to pass. In order to create an ‘OR’ condition, click any criteria again (e.g. “From Organizational Unit”). Another frame would consequently open, to apply further ‘OR’ logic. See the image below for clarification.

8. Click “Save” in order to save the new group.

Defining Groups – By Security groups, and by Name.

The Grouping tool’s groups can also be defined in a very similar manner by relating to the Active directory’s Security groups or named users. The following images demonstrate this:

Groups summary

Click the “Define groups” tab in order to see a summary of the saved groups:

Setting a new domain

As stated in bullet #4 in the previous “Defining Groups” section, the user may require to add a new group domain. In order to do so, click the green ‘+’ symbol adjacent to the “Domain” drop down list. The “New Domain Connection” form appears.

1. Type in the domain name in the upper “Domain Name” text box (e.g.: olm.openlm.com).
2. Type in the Controller (DC) number (e.g.: 123.123.123.123)
3. Select whether to use a Windows Identity, or manually insert Custom Credentials. If the latter is chosen, type in the User name and Password in the designated text boxes.

Usage Reports

The Group reporting Interface tool queries the OpenLM Server for the total license usage of all the users in the predefined groups. This report can only be obtained after configuring Settings, Domains and Groups, as elaborated above.

In order to obtain a report of the license usage query, follow these steps:
1. Click the “Run Query” tab.
2. Select the date interval for the query occurrence.
3. Check the required groups’ check boxes.
4. Click ‘Server’ , ’ Vendor’ and ‘Feature’ in order to see those items in the report.
5. Click the “Run” button to run the query.

The query’s output is a summary report of the total license usage for each of the selected groups.

Revision Table

Revision	Author	Date	Note
0.1 – Preliminary			Preliminary Version
1.0	Orik	Sep 14, 2011	Revised
1.1	Orik	Sep 9, 2012	Enhancements

OpenLM Version 1.7.1.1 – Maintenance release

Posted on September 15, 2011 by rachel

Version 1.7.1.1 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.7.1.1?

OpenLM Server:

Easyadmin – Workstation export csv contains now also first & last names.
Easyadmin – add Japanese.
Easyadmin – Add feature name to licenses export.
Easyadmin – Add product description to features’ search window.
Easyadmin – Fix Internet explorer error when Easyadmin starts.
Increase SqlServer command timeout to 120 seconds.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001″ which is related to a problem with Windows):

Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
Stop the OpenLM Server service
Make sure to close ALL windows, especially the services window
Install the new version on-top of the existing version

Application note 1004: OpenLM Broker Quick start guide

Posted on September 14, 2011 by orik

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:

Please go over the installation prerequisites for the OpenLM Broker.
Download the Broker for Unix/Linux from the OpenLM version 1.7 section.
The installation requires root user privileges.
cd to the folder that contains the setup file
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:

cd to the installation folder
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

Do not close the terminal.
After configuration changes, the Broker needs to be restarted.

In order to uninstall the Broker:

cd to the installation folder
run the following command :

sudo ./uninstall

Windows

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

Please go over the installation prerequisites for the OpenLM Broker on the OpenLM site.
Download the OpenLM Broker for windows from the OpenLM version 1.7 section (see above), and follow the installation instructions.
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:

Mark the “OpenLM Servers” directory icon.
Click the green “Add” icon
Select “OpenLM Server” from the selection list.

OpenLM Servers – Configuring the Server

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.

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.

Select “License Servers” on the left side of the screen.
Click “Add”. A drop-down list appears.
Select “License Server” from the list. The right-hand side of the Broker configuration window changes.
Type in and enter the Description and the Host Name / IP of the new License Server

License Servers – License Manager Port

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.

Description: Name of the new License Server’s log file
Path: Fill in the Path on which to locate the License Log file.
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.

Vendor Name: Vendor’s name (e.g.: ARCGIS, adskflex, ptc_d, MLM, ugslmd)
License: The license file is the one supplied by a specific vendor, stated with its full path.
Option File Description: A descriptive name of the user’s choice (e.g.: my_OptionFile).
Option File Path: The option file related to the vendor, stated with its full path.
Watch Option File: This should be checked for the Option File to be effective.
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:

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.
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.
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

Click the “Status” bullet under the “Commands” bullet. The “Status” command definition form appears on the right-hand side of the window.
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.
It is recommended not to change any other of the default values presented in this form.

Data Inquiry

Click the “Data Inquiry” bullet under the “Commands” bullet. The “Data Inquiry” command definition form appears on the right-hand side of the window.
The default command line is set to send the queried license usage information periodically from the Broker to the OpenLM Server.
The period time is set by the “Interval” parameter.

Start and Stop

Click the “Start” or “Stop” bullets under the “Commands” bullet. The respective command definition form appears on the right-hand side of the window.
The start and stop commands literally start and stop the the License Manager Server’s activity.

Reread

Click the “Reread” bullet under the “Commands” bullet. The “Reread” command definition form appears on the right-hand side of the window.
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

Click the “Save Option File” bullet under the “Commands” bullet. The respective command definition form appears on the right-hand side of the window.
This command enables the user to save the option file upon demand.

Advanced Settings

The advanced settings form handles vendor specific supplied executable files.

Click the wrench icon (highlighted blue) . The “Advanced Settings form appears on the right hand side of the window.
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 Version 1.7.1.0 – Maintenance release

Posted on September 5, 2011 by oren

Version 1.7.1.0 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.7.1.0?

OpenLM Server:

Fix issues in servers configuration.
Easyadmin now supports the following languages: French, Portuguese, Chinese, Russian (in addition to Spanish).
Fix problems with hours/weeks/month statistics computing.
Fix problems when having more than one vendor in one license manager.
Add C++ distributable package to installation.
Increase timeout for Easyadmin requests.
Add Easyadmin console alert when OpenLM Broker server time is different than OpenLM Server time.
Fix Easyadmin License Servers Status not showing when server is down.
Option file UI fixes – don’t allow to add empty features; Don’t allow entities with spaces; When deleting host groups also delete option file references.
Easyadmin – fix filtering for Workstations window.
Fix issue with storing data sent from broker when license output is too big.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001″ which is related to a problem with Windows):

Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
Stop the OpenLM Server service
Make sure to close ALL windows, especially the services window
Install the new version on-top of the existing version

Application Note 1018: Setting OpenLM components’ logging level

Posted on September 4, 2011 by oren

General

The OpenLM system generates detailed log files which help System Managers to locate problems with the OpenLM operation. Log file generation is supported by all OpenLM software components. Logging settings can be configured using the application configuration form.

If you experience problems with OpenLM, you can enable logging on any specific system component, and then post the issue on the OpenLM issue reporting interface.

This guide distinguishes between operating systems, organizing them into 3 categories to make finding the path to the specific log file in your operating system easier.
Pre-Vista - Includes win xp, win server 2003, win server 2003R2
Post-Vista - Includes vista, win 7, win server 2008, win server 2008R2
UNIX/Linux – UNIX or Linux platforms

Set logging levels on different OpenLM System Components

OpenLM Server

Open the “OpenLM Server Configuration Form”, and select the “Advanced” tab. Select the “ALL” option in the “Logging level” drop-down menu. Click “Apply” to apply the changes (Changing the logging level does not require restarting the OpenLM service).

The server log files are located by default under the server installation folder, i.e.:
C:\Program Files\OpenLM\OpenLM Server\Log

OpenLM Agent

Open the OpenLM Agent configuration form. Set the logging level to “ALL” and apply the changes. Since the OpenLM Agent supports terminal server environment, the log files are written under the user’s “Application Data” folder. For example:
Operating System Log File Location
Pre-Vista C:\Documents and Settings\<user name>\Application Data\OpenLM
Post-Vista C:\Users\<user name>\AppData\Roaming\OpenLM

The Windows start menu provides a link for easily locating the OpenLM Agent logs: Click Start → All Programs → OpenLM → Agent → Tools → OpenLM Agent Logs Folder.

Logging the OpenLM Java Agent

Access the OpenLM Java Agent configuration form, set logging level to “ALL” and apply the changes (Changes to the logging level will take effect without having to restart the OpenLM server). Log files are written in the installation folder.

OpenLM Broker

The OpenLM Broker is a Java software component. It can be installed on any Java-compatible environment. In order to set the Broker logging level, please do the following:

Open the Broker configuration tool.
Select the “Advanced Settings” node.
Click the ‘Edit’ button and change the log levels selection drop-menu to ‘ALL’

The OpenLM Broker log files are usually located in the installation folder, i.e.:
Windows OS: this is C:\Program Files\OpenLM\OpenLM Broker\Logs
In UNIX/Linux: Under the predefined installation folder.

OpenLM Alerts

In order to receive alerts, access the OpenLM Alerts configuration menu, and set logging level to “ALL.”

The server log files are located by default under the installation folder, i.e.:
C:\Program Files\OpenLM\OpenLM Alerts System\Log

Logs Uploader

OpenLM Logs Uploader is a solution for loading information from FLEXlm debug log files into the OpenLM database, and view it on EasyAdmin. It too has a logging system. These logs are located as follows:
Pre-Vista: C:\Documents and Settings\All Users\Application Data\OpenLM\LogsUploader\
Post-Vista: C:\ProgramData\OpenLM\LogsUploader\

In order to change the default location, edit the file:
C:\Program Files \OpenLM\OpenLM Logs Uploader\ConfigLogsUploader.xml , and change the default location under the “file value” tag.

Easyadmin proxy logger

The Easyadmin proxy log files are located by default under:

Operating System Log File Location

Pre-Vista: C:\Documents and Settings\All Users\Application Data\OpenLM

Post-Vista: C:\ProgramData\OpenLM

In Order to set the logging level and location of the Proxy logger, Open an editor as an administrator, and apply changes to two instances of the config.ini file:

C:\Program Files (x86)\OpenLM\OpenLM Server\WebApps\EasyAdmin2\cgi-bin\config.ini

and

C:\Program Files (x86)\OpenLM\OpenLM Server\WebApps\EasyAdmin2\config.ini

You can change the logging level (‘ALL’ / ‘ERROR’), log file size, number of backed-up log files and log file location by editing the following lines in the two config.ini files:

# Set root logger level

log4j.rootLogger=ERROR, R

# log file location

log4j.appender.R.File=C:/ProgramData/OpenLM/openlm_proxy.log

# log file size

log4j.appender.R.MaxFileSize=10MB

# Keep ten backup files

log4j.appender.R.MaxBackupIndex=10

OpenLM Grouping Tool

The OpenLM Grouping Tool is an optional component that adds capabilities to OpenLM Groups & Projects extension.
The Grouping tool log files are located in:
Pre-Vista: C:\Documents and Settings\All Users\OpenLM\ADTool\ADToolLogger.txt
Post-Vista: C:\ProgramData\OpenLM\ADTool\ADToolLogger.txt

The Grouping tool’s configuration is done by an XML file, which stores the tool settings. The location of this XML file is:
Pre-Vista: C:\Documents and settings
\<UserName>\ApplicationData\OpenLM\Groups.config
Post-Vista: C:\Users\<User Name>\AppData\Roaming\OpenLM\Groups.config

OpenLM Data Migrating Tool

The OpenLM Data Migration Tool can transfer OpenLM information between different databases.
The Data Migration log file is located by default in the folder:
Pre-Vista: C:\Documents and Settings\<User Name>\Application Data\OpenLM
Post-Vista: C:\Users\<User Name>\AppData\Roaming\OpenLM

DB upgrade logs

DB upgrade log files are created during the upgrade of a DB from an older version of OpenLM, usually as part of a software upgrade. The log files’ location is:
Pre-Vista: C:\Program Files\OpenLM\OpenLM Server\bin\DBUpgrade_Log.txt
Post-Vista: C:\Program Files\OpenLM\OpenLM Server\bin\DBUpgrade_Log.txt

Advanced Logging settings

The default logging setting is “rotate,” which maintains the last ten log files in the folder in order to avoid disk overflow. Advanced users can change this behavior by modifying the log configuration file.

OpenLM Server Advanced Configuration

The log configuration file is typically located under the software installation folder. For example, the server logger configuration is located in:
C:\Program Files\OpenLM\OpenLM Server\Server_Config.
This setting is accessible from the OpenLM Server Configuration form:

Advanced Editing of the Logger Configuration

Using a simple test editor to edit the logger configuration file enables users to change a variety of properties. For example:

The maximum size of a log file
The rotation of the log files
Format of each row in the log file

The following image is an example for a logger configuration file:

OpenLM system requirements for version 1.7 published

Posted on September 1, 2011 by oren

OpenLM published the system requirements for the new version 1.7.

http://www.openlm.com/index.php?option=com_content&view=article&id=20&Itemid=26