Tag Archives: Application Note

Application note 1017: Changing ports numbers in OpenLM

Posted on by

Introduction

The OpenLM Utilizer is a licensing management software. It provides productivity tools for system administrators, managers and end users. OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module. In addition to these core components, the OpenLM software package includes modules and capabilities which provide additional functions. In order to interface these components and obtain full functionality of the OpenLM software, it is essential to open certain port numbers.

OpenLM license Server

The OpenLM Server is the core element of the OpenLM Utilizer system. It integrates the functionality of all other OpenLM peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

License manager: Default port 7016

The OpenLM Server interfaces the License manager over a dedicated port. this port’s default number is 7016.

Configuring the License manager Port:

In the “OpenLM Server” configuration window, select the “Port Settings” tab.
In the “License managers reporting port” text-box, type in the OpenLM server port number (e.g.: 7016).

The OpenLM Broker is an optional software component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server. The Broker is required in order to provide advanced licensing information and capabilities; such as controlling license servers remotely, managing FLEXLM option files etc.

The OpenLM module interfaces the OpenLM Server via a dedicated port. This pot number is 7016 by default, and should be configured the same as the license manager port (see above). For additional information on the OpenLM Broker component, please refer to this application note.

Configuring the OpenLM Broker Port:

There are two methods for configuring the OpenLM Broker port: via the OpenLM Broker configuration tool, and via the broker.xml configuration file.

OpenLM Broker configuration

  1. Open the “OpenLM Broker configuration”.

  2. Choose an OpenLM Server from the OpenLM servers list and click “Edit” .
    Edit the “Port” textbox. Repeat this for all OpenLM Servers.

broker.xml configuration file

  1. Open the broker.xml file,  located on: “C:\Program Files\OpenLM\OpenLM Broker”

  2. Search for the line <Port>7016</port>.

  3. Edit the port number.

OpenLM Agent:  Default port 7012

The OpenLM Agent facilitates available license querying, among other functions. It connects to the OpenLM Server through another dedicated port: the OpenLM Agent default port number is: 7012. The OpenLM Agent port number should be configured the same on the OpenLM Agent configuration tool, and on the OpenLM Server configuration tool.

OpenLM Agent configuration tool

  1. Right-click on the Openlm Agent blue icon on the Windows taskbar,

  2. Open the ”OpenLM Agent configuration” tool. The “Agent Configuration” window pops.

  3. Type in the port number in the “Port” textbox (e.g.:7012).

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Agent port in the “Agent reporting port” text-box (e.g.: 7012).

HTTP Server Port:  Default port 7014

This port enables EasyAdmin web application to send requests to the OpenLM Server.

This port number should be configured the same on the OpenLM Server configuration tool, and on the “config.js” file.

OpenLM Server configuration:

In the “OpenLM Server” configuration tool, select the “Port Settings” tab. Type in the HTTP Server port in the “User Interface http server port”  textbox (e.g.: 7014).

config.js file:

  1. Open the “config.js” file, typically located on:”C\Program Files\OpenLM\OpenLM Server\WeebApps\EasyAdmin2”
  2. Search for the number 7014.
  3. Edit the port number(Should be 7014).

OpenLM Alerts System:  Default port 7017

The OpenLM Alerts module produces alerts for system managers based on predefined conditions. These alerts may be directed to email messages, SMS text messages, the EasyAdmin web application or to a dedicated log file. Please refer to this application note for elaborated information on the OpenLM Alerts module.

Configuring the OpenLM Alerts port:

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Alerts port in the “Alerts server checking port” textbox (e.g.: 7017).
  1. In the OpenLM Alerts configuration form, of the OpenLM Alerts Editor, type in the port number in the “Alerts Port” textbox.

OpenLM HTTP port Default port 7019

OpenLM installs the LightTPD web server with the installation of OpenLM Server. LightTPD is configured as a Windows Service and starts up with the machine. The use of web servers such as Apache or IIS or others is also supported.

Configuring the OpenLM LightTPD port:

  1. Open the “lighttpd-inc.conf” file,  located on: “C:\Program Files\OpenLM\OpenLM Server\WebServer”.
  1. Search for the line “bind to port (default: 80) server.port = <port number>”.
  2. Edit the port number (e.g: 7019).

Serve OpenLM EasyAdmin using Microsoft IIS 6 & 7

The OpenLM Software package is delivered with LightTPD; a built-in web server. The LightTPD web service starts upon installation or machine start-up. Users can either use LightTPD or choose a standard web server such as Microsoft IIS.

For additional information on how to serve OpenLM EasyAdmin using IIS6, please refer to this application note. For information on how to serve OpenLM EasyAdmin using IIS7, please refer to this application note.For information on how to serve OpenLM EasyAdmin using Apache webserver, please refer to this application note.

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

Posted on by

General

The OpenLM Utilizer supports the IBM LUM license server. IBM LUM licenses are used by various software vendors, the main being Dassault Systems (Catia software). In order for OpenLM to support the LUM License server it has to be able to access the LUM License server remotely or locally. Different configuration options are supported by OpenLM that allows system managers to configure license servers located on LAN and WAN networks.

Table of contents

General
System Configurations Options
IBM LUM and OpenLM on the same machine
IBM LUM and OpenLM on separate machines
Configuring the OpenLM Broker to push usage information to the OpenLM Server
Configuring the OpenLM Server machine to query usage on the IBM LUM License server
Adding an IBM LUM license server in the OpenLM server configuration form
IBM LUM Support Level
Summary

System Configurations Options

OpenLM Supports flexible configurations for LAN or WAN networks. This section elaborates these configurations. Most of the information in this section is also relevant to other license servers such as SafeNet RMS, SafeNet HASP, FLEXlm, FLEXnet, RLM and others.

IBM LUM license server and OpenLM on the same machine

This is the most simple configuration but not a very realistic one. Most companies have more than one license server and because of that, they install OpenLM on a separate machine. When OpenLM server is installed on the same machine as the IBM LUM License server, there is no additional configuration steps; just add the server name and port to the configuration.

IBM LUM license server and OpenLM on separate machines

In this scenario, the OpenLM Server is installed on one machine and the license server is installed on another. The problem we have to solve is how to enable the OpenLM Server to access the LUM License Server. There are two possible solutions:

  • Employ the OpenLM Broker to send IBM LUM usage data to the OpenLM Server.
  • Configure the OpenLM Server machine to be able to query usage on the IBM LUM License server.

Configuring the OpenLM Broker to push usage information to the OpenLM Server

This is the most simple solution but it requires access to the license server machine for installation. OpenLM Broker software is reading the license usage locally and pushing the information to OpenLM Server.
Installation of the OpenLM Broker requires Java JRE. It can run on any operating system supported by Java; hence OpenLM supports Linux, Windows and UNIX license servers. Please refer to the OpenLM Broker quick start Application Note for further information.

OpenLM supplies an updated version of the IBM LUM executable file i4blt.exe. On occasion, this file may be non-compliant by version to the one that runs the IBM LUM license manager. If this occurs, please change the path fo IBM LUM commands in the OpenLM Broker, as elaborated in this trouble – shoot article.

Configuring the  OpenLM Server machine to query usage on the IBM LUM License server.

The IBM LUM Server enables other machines to query license usage and perform other actions remotely. For a full install procedure please consult the IBM LUM documentation. The following list is a short overview of this procedure.

  1. Install Java JRE on the OpenLM Server machine.
  2. Make sure that you have IIS installed and configured on the OpenLM Server Machine.
  3. Install the LUM software on the OpenLM Server machine. There is no need to configure the OpenLM server machine as an LUM server.
  4. Add a reference to the OpenLM Server on the IBM LUM License server.
  5. After installing the LUM software on the OpenLM Server machine, the i4ls.ini file is created. For Windows versions Vista and beyond, copy this file from

C:\Users\<Username>\AppData\Local\VirtualStore\ProgramData\IBM\LUM  to C:\ProgramData\IBM\LUM.

For pre-Vista versions, copy this file from

C:\Documents and Settings\All Users\Application Data\IBM\LUM to

C:\Users\All Users\IBM\LUM

Note that if you use the Server’s IP instead of its name (for instance if the servers  are located on different DNS domains so that DNS resolution does not work), a ‘#’ symbol must precede the IP.

Adding an IBM LUM license server in the OpenLM server configuration form

Like the configuration of FLEXlm and SafeNet RMS Services, the configuration of an IBM LUM is simple and straight forward:

  1. Open the OpenLM Server Configuration, on the License Servers tab.
  2. Click the ‘Add’ button. Type in the License Server name (e.g.: olm_test_lum2) and port number (e.g.: 9999).
  3. Select ‘LUM’ in the license server ‘Type’ drop down menu.
  4. Type in a verbal Description in the ‘Description’ text box (e.g.: new LUM license manager)
  5. Click the ‘Apply’ button. A restart notification appears.
  6. Click the ‘Restart now’ button. That’s it: the OpenLM Utilizer is set to monitor the LUM license server.

IBM LUM Support Level

The main functionality of the OpenLM Utilizer is also applicable to IBM LUM licenses. In addition, the OpenLM Utilizer facilitates unique IBM LUM features, such as feature versions.

The main OpenLM supported features for IBM LUM include:

  • License inventory reporting.
  • License expiration alerts (from OpenLM v1.8).
  • Current license usage.
  • Usage reports and charts.
  • License billing for groups or projects.

Summary

IBM LUM (License Use Management) is the IBM product for technical software license management (analogous to FLEXnet, being Flexera’s  license management product). The OpenLM Utilizer fully supports the IBM LUM software, and provides a flexible architecture for complex configurations.

OpenLM supports unique features of IBM LUM such as versions for features. Advanced OpenLM features such as License Usage Billing, Usage Reports and Usage Charts are supported for IBM LUM.

Revision Date Author Notes
0.1 – Preliminary Nov27, 2011 Preliminary
1.0 May13, 2012 License expiration alerts:  from OpenLM v1.8.

Application Note 1000: OpenLM system structure overview

Posted on by

Application Note 1000: OpenLM system structure overview

Table of contents

OpenLM
OpenLM’s customer testimonials
The OpenLM solution
Components of the OpenLM system
Block Diagram
OpenLM Software Modules
OpenLM Server
OpenLM EasyAdmin
OpenLM Broker
OpenLM Alert
OpenLM Utilizer Agent
OpenLM Active Agent
OpenLM External Data Base (DB) Support
OpenLM Groups & Projects
OpenLM Role Based Security
OpenLM Option File Management
OpenLM Logs Uploader

OpenLM

OpenLM is a licensing management software company with an international install base. Companies that use OpenLM’s software range from global corporations and nation-wide companies to small offices. Our company’s commitment to innovation guarantees that our clients constantly receive updates with the most advanced technology.

OpenLM’s customer testimonials

Please review a partial list of OpenLM’s satisfied customers,

http://www.openlm.com/index.php/about-us-topmenu-3/customers

and their testimonials:

http://www.openlm.com/index.php/support/testimonials-topmenu-29

The OpenLM solution

OpenLM’s Software provides a comprehensive management solution for license management software such as FLEXlm, FLEXnet, Sentinel RMS, Sentinel HASP, RLM, IBM LUM and LM-X. The software provides productivity tools for system administrators, managers and end users. OpenLM’s software supports the major trends in the field of license management, e.g.: license consolidation, Usage charge back (usage billing), usage trend analysis etc. The software provides a comprehensive solution that combines the best of breed software, superior support, implementation and consulting services, in order to ensure your success.

OpenLM is proudly ISO9001:2008 certified by the ANAB (the U.S. accreditation body for management systems), and an ESRI business partner.

OpenLM’s solution is tailored according to specific customer needs, optimizing the licensing system and increasing software productivity.

Components of the OpenLM system

OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module.

In addition to these core components, the OpenLM Broker and the OpenLM Utilizer Agent modules are incorporated in the basic software package, but their installation is not mandatory; The Open LM system can function without the use of these two components.

The OpenLM software package also includes several optional modules / capabilities, which are commonly referred to as “OpenLM extensions”. These extensions provide additional functions such as:

  • OpenLM Active Agent (Active release of licenses)
  • External DB support
  • Groups and projects management
  • Role based security
  • Option file management
  • OpenLM Alerts
  • OpenLM Logs Uploader

The OpenLM Extensions are separately licensed:

  • Some of them are included within the OpenLM Server but require additional licensing
  • Others require the installation of an additional software module.

Block Diagram

Figure1 (below) shows a generalized block diagram of OpenLM’s license management solution:

OpenLM Software Modules

OpenLM Server

The OpenLM Server is the core element of the OpenLM system. It integrates the functionality of all other peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

The OpenLM Server is implemented as a Windows service and could be installed on any network machine. It enables monitoring and managing of multiple license servers, over LAN or WAN networks. Common OpenLM Server configurations may vary from one or more license managers nationwide to multiple license servers located worldwide, over different time zones.

OpenLM EasyAdmin

OpenLM EasyAdmin is the administrative interface of the OpenLM system. EasyAdmin’s control panel features a desktop interface that enables users to configure the OpenLM Server; OpenLM’s core component. Some of EasyAdmin’s main properties are listed below:

  • EasyAdmin Easily extracts statistical license usage information from all attached license servers.
  • EasyAdmin’s role-based security enables system administrators to grant varying degrees of access to different groups of users.
  • EasyAdmin can run on any standard web browser (e.g.: Mozilla FireFox, Microsoft Internet Explorer, Google Chrome) and be accessed from any machine in the organization.
  • EasyAdmin features a touch interface that is compatible with mobile operating systems like Android, IOS, Blackberry and Windows Mobile. The OpenLM EasyAdmin Mobile application is particularly useful for after-hours crisis management situations.
  • EasyAdmin’s streamlined user interface design promotes simple and effective use of its unique capabilities.

OpenLM Broker

The OpenLM Broker is an optional server component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server, and is required in order to provide advanced licensing information and sophisticated abilities.

The Broker’s main task is to extract License Manager Servers’ debug log information and to push it to the OpenLM server. This action facilitates reading of license servers’ log files. Other capabilities provided by the broker are:

  • Controlling license servers remotely (e.g. start / stop the servers)
  • Managing FLEXLM option files.
  • Generating denial reports and
  • Support of complex configurations, e.g. license servers that work over WAN networks.

The Broker is an independent java based software module that can run on any license server operating system: UNIX, Linux or Windows.

OpenLM Alert

The OpenLM Alert is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met. Alert service users can set complex alert conditions on multiple license servers. For example, if the combined usage of a certain feature on servers A and B is above a certain threshold, an email message will be sent, alerting those concerned to the situation. The Alert service also supports adjustable timing for alert checking and message sending. Alert destinations are also configurable; Alerts could be sent to the EasyAdmin interface, over emails, as SMS text messages, or directed to a system event log.

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system. It provides OpenLM users with the following capabilities:

  • Query license availability.
  • Check which users are holding required licenses.
  • View a user’s full set of details as they appear on the LDAP, and communicate with users regarding license availability.
  • Receive license availability notifications as soon as requested licenses become available.
  • Report the session’s active project (mainly for billing purposes).

OpenLM Active Agent

The Active Agent incorporates all the characteristics of the Utilizer Agent. On top of that, it supports an extension that enables system administrators to shut down open application either manually, or by defining a timeout policy. In this manner, system administrators can save, close, or suspend idle applications, in order to make more efficient use of licenses. The Active Agent features a user-friendly interface that enables users to quickly reopen closed applications, or resume suspended ones.

OpenLM External Data Base (DB) Support

This extension facilitates saving license usage information on an external Data Base such as an Oracle or MS SQL Server. By default, OpenLM uses an embedded DB. External DB support is recommended for management of large licensing systems.

OpenLM Groups & Projects

This extension enables collecting license usage information from Groups of users or projects. This capability is predominantly used by companies that charge back usage time to cost centers. The Groups & Projects extension synchronizes users’ data with its LDAP Data Base (Active Directory), keeping the data collection process fully automatic.

OpenLM Role Based Security

The OpenLM Server supports a role-based security feature that enables the implementation of customized access to OpenLM tools by setting access roles. This feature facilitates the implementation of OpenLM tools for diverse groups; e.g.: help desk, system administrators, managers and developers. The role based security system secures nearly all parts of the system entities, such as listed servers, fields and action buttons.

OpenLM Option File Management

The OpenLM Option File Management extension employs LDAP (Active Directory), to enable system administrators to manage Option Files easily from the EasyAdmin web based interface. This gives the system administrators easy control over the access of user groups and individuals to licenses.

OpenLM Logs Uploader

The OpenLM Logs Uploader extension enables loading of historical FLEXlm debug log files. This extension is essential for investigating historical license usage. Logs Uploader is also necessary for checking license usage in files received from customer sites, typically in order to charge per use.

Application note 1014: OpenLM support for the Sentinel HASP license manager

Posted on by

General

OpenLM versions 1.6 and higher feature the ability to monitor Sentinel HASP and Sentinel RMS license servers. OpenLM supports the full functionality of the system for HASP and RMS licenses:

  • License inventory reporting.
  • Managing active users.
  • License billing.
  • Statistics and charts.
  • End user productivity tools, and more

Along with the support for SafeNet Sentinel software, OpenLM also supports FLEXlm, FLEXnet, IBM LUM, RLM and LM-X.

OpenLM system requirements

OpenLM supports HASP versions 5.0 and higher. Versions 3 & 4 are not supported.

Adding a Sentinel HASP Server

Please follow the action list below to add a new HASP license server. Observe the following image for further clarification.

  • Open the OpenLM Server configuration tool, on the License Servers tab (1).
  • Click the “Add” button to create a new License manager entry (2).
  • Select HASP from the “Type” drop-down menu (3).
  • Server connectivity configuration (4):
    • Hostname: Type in the HASP server name or IP (e.g.: new_hasp_server).
    • Port: Type in the port of the “Sentinel Hasp Control Admin Center”. This value is by default 1947.
    • Is Triad Configuration: Click the check box according to the License server’s configuration.
  • Additional information (5):
    • Add an informative description of the License Server (e.g.: My HASP license manager).
    • Select the time zone.
  • Finalization (6):
    • Check the “Enabled” check box
    • Click the “Apply” button

HASP Server Settings

If the OpenLM Server is installed on the same machine as the HASP license serve, then no additional setting is required.
If OpenLM Server is installed on a different machine than that of the HASP server, Open the “Sentinel Hasp Admin Control Center” port (default 1947) on the firewall. Change the settings of “Sentinel Hasp Admin Control Center” to “Allow Remote Access to ACC”. See the image below for clarification.

OpenLM EasyAdmin display screenshots

OpenLM may display the Sentinel HASP License inventory (below):

As well as other license usage information, such as the currently active products (below):

Application Note 1011: Quick Installation guide for the OpenLM license management system.

Posted on by

Step 1: Installation

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:

And start by downloading the server:

When downloading is complete, double click the downloaded *.msi file and follow the standard installation instructions.

Step 2: Configuring License Servers

By the end of the installation process, The OpenLM Server configuration window appears.

1. Add in your license servers:

  • Click the ‘Add’ button,

  • Type in the License server’s host name or IP (e.g. lm10) and Port number (e.g. 27000)

  • Select the new License server’s type (e.g. FlexLM)

  • Type in an informative name (e.g. “lm10 – ArcGis server”)

  • Select the license server’s time zone (e.g. UTC+1)

The image below demonstrates a configuration of four license servers.

2. Select a license server and click the check button in order to ensure that OpenLM can retrieve information from that license server.

3. Repeat steps 1 & 2 for all license servers.

4. Click ‘Apply’ and close the configuration window. Changes and additional configurations can be made at any stage in the OpenLM Server configuration window.

You can find it on

Windows’ Start button → All Programs → OpenLM → Server → OpenLM Server Configuration

Step 3: The EasyAdmin Interface

The EasyAdmin web application is the main OpenLM users interface.
You can find it on:
Windows’ Start button → All Programs → OpenLM → OpenLM EasyAdmin2.

The OpenLM EasyAdmin opens. Click the start EasyAdmin start button to explore this application’s features.

 

The image above is an example of an EasyAdmin workspace. It features Administrative tools, License data, License usage data, Graphic usage representation, Roles and permissions’ assignment, and Active Agent capabilities.

Congratulations!

You now have an up and running OpenLM system.

For further information regarding the installation and preliminary configuration of the OpenLM system components, please refer to the “Application Note 1010: OpenLM license management system Complete Installation guide” document.

Revision table

Revision 1.1

Author: Orik

Date: June 2012

Remarks: Updated

Application Note 1005: Configuring OpenLM to close idle Licenses

Posted on by

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:

  1. An “Active Agent” is installed and running on these stations
  2. 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 by

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:

  1. Make sure that the server name and address are correct.
  1. Make sure that the port is open:
    1. Try disabling the firewall temporarily.
    2. Enter “Control Panel” → “System and Security” → “Windows Firewall” → “Advanced settings”.
    3. 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:

  1. Two modes of application closing
    1. 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.
    1. 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.
  1. Three configuration options for closing sessions of licensed software
    1. Automatic release: The administrator can set a time for a license to return to the license pool.
    1. 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.
    1. 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:

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