FLEXlm Timeout Settings

What is FLEXlm?

FLEXlm is a license manager that manages software used by multiple end users on different computers. Notably, it allows companies to take advantage of floating licenses. A system employing floating licenses has a license pool on a host server from which end users check out licenses. When a user finishes using a software license, it is checked back into the pool, now available for another user to check out.

Further information on FLEXlm

What is FLEXlm license timeout?

FLEXlm license timeout is a feature that releases inactive licenses back to the license pool. Licensed software is determined to be inactive when a machine is completely idle, meaning no mouse clicks, keystrokes, modal dialog boxes are occurring. Its timeout settings determines how long such a period continues before licenses are freed up.

How to set FLEXlm timeout

License timeout settings can be configured for some or all the features, and are configured in the FLEXlm option file.

Further information on option files

Individual license key timeout is set by entering the variable “timeout” followed by the timeout period (in seconds).

Example: Setting AutoCAD to be timed out in 108000 seconds (3 hours)

 timeout AutoCAD 108000

License timeout for all license keys in the system is set by the variable “timeoutall,” followed by the timeout period.

Example: Setting all licenses to be timed out after 30 minutes of inactivity

timeoutall 1800

Limitations on license timeout settings

It is important to note that software vendors often impose limitations on the timeout period for their products; specifically, the minimum amount of time of inactivity after which licenses can be freed up. For example, whereas Autodesk licenses can be released after 15 minutes of inactivity, MathWorks licenses can only be released after 4 hours.

Autodesk 900 sec (15 minutes)

MathWorks 14,400 seconds (4 hours)

IBM 7200 seconds (2 hours)

Application

Customizing FLEXlm timeout settings is simple way to improve the efficiency of your company’s licenses, ensuring that end users aren’t slowed down by waiting for inactive, locked-up licenses.

 

Multiple Server license management constellations

Flexera’s FlexLM (Flexnet)Three Server Redundancy (Triad)

IBM’s High Availability Licensing (HAL)

Dassault Systemes DSLS cluster for “Failover” mode

Scope:

License management tools such as IBM and Flexera both a method of employing multiple license servers in a cluster as part of their attempt to assure a fault-free license management solution. This article summarizes the operative measures required for implementing each of these solutions, and attempts to compare them in terms of pros and cons.

The OpenLM Utilizer license monitoring tool supports both configurations. OpenLM is designed to extract license statistics from multiple servers over WAN. It has been tried and confirmed for Flexera’s Triad configuration. At the time of writing this revision (Rev 1.0), It has not yet been verified with the IBM LUM HAL.

Flexera’s Three Server Redundancy constellation

General:

The Flexnet constellation is consisted of Three license servers, all inter-connected by TCP/IP. These machines are adequately named “Primary”, “Secondary” & “Tertiary”. Any one of the two first machines (Primary or Secondary) may be defined as the “Master”; which is counter intuitive, as it gets to do all the work while the other two basically sit on their hands. All licenses are served by this Master machine, and the Report & Debug logs are also accumulated by it.

Upon system start-up, the three FlexLM license servers are started up separately according to their order, and the Master role is set according to this order or according to a designated flag: “PRIMARY_IS_MASTER”.

The  FlexLM license Servers inter-communicate by a “Heartbeat” messages over TCP/IP, using the same port number. A machine which fails to receive a response to its sent Heartbeats turns down the vendor daemon and can not serve licenses. When the Master server (Primary or Secondary) fails, the Master role is passed to the other (Secondary or Primary) server. The new Master assumes the license management role for all the FlexEnabled applications, and accumulates new Debug and Report logs.

Configuration of a Three Server Redundancy constellation:

  • First, a set of three stable machines needs to be identified, and reliable communication needs to be set between them.
  • The software vendor must receive the HostID and Host name of the machines that consist the Triad. In return, they should provide system – specific license server files. Some changes may need to be done in the license file according to this new information, such as the PRIMARY_IS_MASTER value, the communication port number and the HEARTBEAT_INTERVAL which is effectively the timeout for license servers to be knocked out of the triad.
  • The license server package needs to be copied to each of the three participating servers.

Limitations:

  • There should always be at least two machines up and running. If any two machines halt – then the Triad is stopped as a whole, and no “FlexEnabled” applications are served. This is quite an odd limitation, as the system basically employs a single machine at a time anyway.
  • The “Tertiary” machine never gets to play “Master”. I find this an odd planning, because this in effect renders this machine useless.
  • This configuration puts a strain on one machine at a time. It does not share the work, and is prone for errors especially in busy environments.


IBM’s High Availability Licensing (HAL)

General

The IBM HAL is based on the “License server Cluster” concept. A cluster is a group of 3 to 12 license servers, that jointly manage licensed applications. The management activity load is dynamically and equally shared among most of the servers, while one or two other servers remain on-hold, waiting to pitch in in case an active server becomes unavailable.
Network license servers that participate in a cluster can simultaneously serve server-bound licensed applications,  as well as cluster bound applications.

Configuring HAL

  • Select a set of interconnected license servers as cluster members. These members need to be stable machines, that stay on permanently. Network stability is also crucial in order to assure faultless system activity. It is recommended to maintain the machines in the same geographical vicinity, and that they all run the same operation system type.
  • Instal LUM on each of the license servers.
  • Create the cluster from one of the servers in the cluster. This may be done using the i4blt -H command or the GUI. In the following example, cluster ThisCluster was created, and it contains 3 servers: Server1, Server2 & Server3.
    • i4blt -H c -N ThisCluster -T 3 -n “Server1 Server2 Server3”
  • Activate each member of the cluster. The 1st member is already enabled by default following the cluster definition. This example enables Server2:
    • i4blt -H a -N ThisCluster -n Server2

In order to Deactivate a Server2, use

  • i4blt -H a -N ThisCluster -n Server2
  • Get a HAL Enrollment Certification File (ECF) from the license vendor. In order to do so, You must send him the “Cluster ID”. This ID can be obtained by typing in the status cmmad:
    • i4blt -H s -N ThisCluster.
  • Enroll the HAL ECF just like as for regular license servers, using the GUI or the i4blt command line. for example:
    • i4blt -a -n ThisCluster -f <ECF> -T <NumberOfLicenses>
  • Configure all clients to recognize all the cluster members.

Dassault Systemes DSLS

The DSLS license manager also implements a cluster structure, for “Failover mode”. Its characteristics are a mix of the two types mentioned above;

  • A server may not perform as part of a cluster AND as a stand alone server at the same time.
  • The number of license servers that participate in the cluster are exactly 3.
  • The OS on each server may be either Unix or Windows.
  • At least two machines should be up and running, and interconnected  in order to serve licensed applications.
  • There is no ‘Master’ here: all machines have the same role of license management.
  • The three machines each log the license activity independently. They update each other when usage conditions change.


Summary

It seems that the IBM LUM solution for multiple server constellations is more comprehensive than that of Flexera’s. Its main ‘Pro’ characteristics include:

  • Equal sharing of the workload.
  • Dynamic redistribution of license management as a function of server availability
  • Configurable amount of servers; a maximal 12 server constellation, in comparison to 3 (effectively 2) Flexera servers.

The main ‘con’ on the IBM LUM list is its lack of popularity in comparison to Flexnet (FlexLM). This has manifested in a trend of licensed application vendor’s migration from LUM to various other license management tools, e.g. FlexLM and DSLS.

 

Further Reading:

http://www-01.ibm.com/software/awdtools/lum/hal.html

http://kb.flexerasoftware.com/doc/DocumentRepository/Licensing/FLEXnet_Publisher/FLEXnet_Publisher_11.6/03_ISV/Product%20Manual/LicenseAdministration.pdf

http://communities.mentor.com/mgcx/servlet/JiveServlet/previewBody/2877-102-1-5407/licensing_bp_wp-10.8.pdf

http://pdir.technodat.cz/r21/install_v5doc/doc21/online/basil_C2/pdf/DSLS.pdf

OpenLM Maintenance Release Version 1.7.2.5

Version 1.7.2.5

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

Upgrading

In order to upgrade to version 1.7.2.5:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.2.5 ?

OpenLM Server:

  1. French version labels in EasyAdmin and OpenLM server corrected.
  2. Fix LM-X reading: Fix LMX multi-session reporting issue (Bug #415).
  3. Fix DSLS reading for SQLServer DB
  4. Add first name, last name to active products export (Bug #404)
  5. Correct OpenLM LightTPD path variable (Bug #396)

OpenLM Agent:

  1. Active Agent 1.7.1.1: Install extensions for every Autocad component on a workstation.
  2. Agent 1.7.1.2: Add updated French resources.

OpenLM Maintenance Release Version 1.7.2.1

Version 1.7.2.1

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

Upgrading

In order to upgrade to version 1.7.2.1:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.2.1 ?

OpenLM Server:

  1. Fix for logs uploader.
  2. Fix for DataExporter (timeout for http request).

OpenLM Agent (version 1.7.1.0)

  1. Fixed an issue that caused the software to close without showing a notification – in some cases.
  2. Fix localization issues for countries that use comma (,) as decimal point.
  3. Fix Portuguese configuration form (Bug #309).
  4. “License Usage Information” now shows available licenses.
  5. Improved “License Usage Information” & “Recently Closed Documents” windows loading time.

 

OpenLM Maintenance Release Version 1.7.1.6

OpenLM Maintenance Release Version 1.7.1.6

Version 1.7.1.6

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

Upgrading

In order to upgrade to version 1.7.1.6:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.1.6?

OpenLM Server:

  1. Sometimes Flexlm sends temporarily inaccurate license reports. In EasyAdmin, this was experienced as duplicate overlapping license draws. The problem was avoided by implementing a time-wise filter, to ensure that changes in the license are consistent for an hour. This change impacts the system’s operation:
    1. Momentary changes are ignored
    2. Latency of true changes’ display has increased.
  2. Two problems reading Option files; Option file may contain some unusual characters (like &) at the title. To fix that we also made a change at the OpenLM Broker. The second issue we had was in reading option file lines with a comment at the middle of the line.
  3. Fixed the repetitive “Please select time zone” bug in EasyAdmin, when running Internet Explorer IE8 & IE9. This bug stems from the limitation that these browsers impose on the amount and size of stored cookies. The workaround for IE8 & IE9 users is giving up on some of the cookies in IE8 & IE9; such as the ones that save the recent size and location of the window. Users of FF and Chrome are not impacted by this change. On the upcoming version 1.8, the the cookies mechanism would be replaced, and again there would be no difference in user experience between browsers.

OpenLM Broker (version 1.7.1.7):

  1. Add pane to installation , explaining about the configuration tool, to prevent confusion.
  2. Fix some type in configuration tool.
  3. Fix automatic detection of ports on windows 64bit. read the Wow6432Node registry key.
  4. Improved Option file reading. See item #2 in the OpenLM server section, above.

Application note 1017: Changing ports numbers in OpenLM

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

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.

OpenLM Maintenance Release Version 1.7.1.5

OpenLM Maintenance Release Version 1.7.1.5:

Version 1.7.1.5 (Broker version 1.7.1.6)

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

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

Upgrading

In order to upgrade to version 1.7.1.5:

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

New in version 1.7.1.5:

OpenLM Server:

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

OpenLM Broker (1.7.1.6):

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

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

Application note 1013: OpenLM Alerts

Scope

OpenLM Alerts is designed to assure the stability and availability of your licensing system. The system allows the system manager to define conditions and what will happen when these conditions are met. The system is able to handle complex conditions on multiple license servers and features and is able to send alert by email or SMS.

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

General

The implementation of OpenLM Alert system allows organizations to handle problems related to the licensing system even before the users experience the problems. The “OpenLM Alerts” tool provides the system administrator ability to closely monitor the licensing system through a set of predefined message rules.

These messages may be assigned different severity levels, i.e.: Alerts, Warnings and Notifications. The Alerts tool messages may be configured to be sent to the system administrator as an email, an SMS text message, as a notification in the EasyAdmin web application or redirected to an event log file.

OpenLM Alerts System Architecture

The Alerts system is implemented by a Windows service working in conjunction with the OpenLM Server.


The Alert Systems interface, OpenLM Alerts Editor allows the user to define a set of alerts that are written to an XML file. OpenLM Alerts service reads the alert and constantly checks the conditions against OpenLM Server.

When a condition is met, OpenLM Alerts checks the defined destinations and timelines, and sends the messages to the users using the SMTP and SMS gateway.

“OpenLM Alerts” is an optional component that requires additional licensing. It may be downloaded and installed for evaluation purposes for a period of up to 30 days. After that, a customer would have to contact sales@openlm.com for pricing.

Downloading and Installation

The Alerts tool can be installed on any Windows platform. It should be installed on the same machine as the OpenLM Server. The OpenLM Alerts installer requires .NET Framework 3.5.

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:

Roll down to the bottom of the page, and click the “Download” button under the OpenLM Alerts label. Follow the standard Installation wizard commands to go through the installation process.

Note: The OpenLM Alerts component monitors your license servers (FLEXlm, IBM LUM, and Sentinel RMS) and it should not be installed on the same server as your license servers. Otherwise, the OpenLM alerting system will also stop running along with FLEXlm in case of any hardware or software failure.

At the end of the installation process, the Alerts Configuration Form will be displayed.

The Alerts Configuration Form

Open the Alerts Configuration from. Its image is shown below:

Fill in the required information to configure the Alerts module:

  • OpenLM server: Type in the OpenLM Server name or IP. In the example above, the Alerts module was installed on the same machine as the OpenLM server, hence OpenLM server was defined as localhost.

  • Alerts Port and UI Port: These are the OpenLM server ports that interface with the Alerts module. These should be the same ports as defined in the “OpenLM server configuration”  form under the “Port Settings” label, namely the “Alerts server checking port” and the “User interface http server port” respectively.

Click the “Check connectivity to OpenLM Server” buttons to ensure that the Alerts module interfaces the OpenLM server on both these ports.

  • Configure mail / sms services: The OpenLM Alerts may be sent email or SMS text message. In order to configure the alert to be send as an email:

  1. Click the Configure mail/sms services button. The Configuration widow opens on the Email tab.

      

  1. Type in the required information, and click the “Test account” button. A test message would be sent to the configured account.

  2. Click the “OK” button to finalize this configuration.

In order to set the Alerts module to send SMS text messages:

  1. select the SMS tab on the Configuration window.

  1. Contact OpenLM Sales (sales@openlm.com) in order to receive your SMS username and password.

  2. Type in the required data, and press the “Test account” button. An SMS text message would be sent to the configured account.

  3. Click the “OK” button to finalize this configuration.

The Alerts editor window

The OpenLM Alerts System features a visual and easy-to-use Alerts Editor. In order to access the editor: Click the Windows “Start” button, and navigate to “OpenLM” → “Alerts System Service” → “OpenLM Alerts Editor”. The Alerts Editor window opens.

To add a new alert, follow these steps:

  1. Click the “Add” button. The “Conditions Editor” window opens.


  1. Enter the “Query Name” text.
  2. Click the “Severity” drop down menu, and select the required severity level to be Alert, Warning or Notice.
  3. Select the condition type: OpenLM Alerts system uses conditions to help organizations locate failures or inefficient usage of licenses. The condition types are:
    1. Feature threshold – Checks the usage level of a feature.
    2. Check duplicate licenses – Checks whether a user uses the same features on multiple workstations.
    3. OpenLM server is down.
    4. Feature Expiration – Alert that a feature license expiration date is coming up.
    5. Monitored license manager that OpenLM fails to contact
    6. Users without default group
    7. Users without default project
  1. Configure one or more Alert destinations:
    1. Click the “Type” drop down menu, to select the Alert destination type. The optional types are:
      1. Email
      2. SMS text message
      3. EasyAdmin web application
      4. Event log
    2. Type in the Alert’s destination in the “Destination” text box.
    3. To customize the number of times an alert could be sent, click the “Limit Send Times” button. The “Select allowed sending times” window opens. Customize the alert’s sending times on this window.
  2. Click the “Add” button. A corresponding Alert line is added in the “Query Definition” frame (see below).


  1. Configure each alert line separately and click “OK”. A new alert is added to the Alerts List on the “Alerts Editor” window.
  2. In order to edit an alert, select a Query Name (e.g.: my_new_alert) on the “Alerts Editor” window, and click the “Edit” button. The “Conditions Editor” opens again, and the necessary changes may be applied.

Alerts Timing

There is a method for setting up the Alerts’ timing (e.g.: If the system administrator is reluctant to receive SMS messages at 3:00 AM). In order to do so, please configure the “Select allowed sending times” window.

This window is accessible through the “Conditions Editor” window’s “Limit send times” button. Configuration of timing may be done in two methods: via the “User Interface” or the “Custom Pattern”.

User interface configuration

The example below shows an email alert pattern configured to each working day of the week, between 08:00 and 20:00. Note the Regular expression for this pattern is “* 8-20 * * 1-5”

 

Custom Pattern configuration

The user may also set the alert according to the Regular expression pattern, in order to obtain more complex alert timing patterns. For example: setting the alert for each working day of the week on every whole hour would create the pattern 0 */1 * * 1-5. In order to combine the two patterns mentioned above, i.e: have an alert for each working day of the week on every whole hour AND between 08:00 and 20:00, we need to superimpose the patterns, i.e:
“* 8-20 * * 1-5” + “0 */1 * * 1-5” = “0 8-20/1 * * 1-5”

Implementation Tips

  • Every Alert query consumes resources from the OpenLM system, hence a good alerts’ system should contain the minimum number of checks that would assure a stable and effective licensing system. The frequency of queries can be configured on the “Select Frequency” dialog box (Click the “Frequency” button in the “Alerts Editor” window to access this dialog box).

  • The “Limit Send Time” button in the “Conditions Editor” window allows you to direct the alert to the desired destination. For example, an alert may be sent to an email during work hours and to SMS after work hours.

Revision Table

Revision Date Author Notes
0.1 – Preliminary Nov 10, 2011 Orik Preliminary
1.0 Mar 23, 2012 Orik Added Alerts’ timing

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

 

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

Symptom

LUM licenses don’t show up in EasyAdmin.

Solution

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

Changing a single port’s configuration

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

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

Changing all ports’ configurations

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