FlexLM License file format

General

FlexLM license files are in effect an agreement between the license vendor and the end user; They elaborate the number of available licenses, the check – out policy for each license, validity and expiration date of each license etc. The FlexLM License Manager Daemon (lmgrd) interprets the license file to dispatch license requests to different license vendor daemons.

This document is a short account of the format and syntax of the license file, and its effect on licensed applications’ utilization.

SERVER line

License files usually begin with a single SERVER line, or three SERVER lines for Server triad configurations. The SERVER line specifies the license server’s

  • Hostname

  • Hostid (MAC address) of the and

  • TCP/IP port number of the license manager daemon (lmgrd). If no port is specified then the first available port in the range 27000 to 27009 will be used.

Syntax

Server line syntax is as follows:

SERVER <server name> <host id> <lmgrd port>

Example

SERVER my_server 001122334455 27000

USE_SERVER

VENDOR line

The VENDOR line specifies the

  • Vendor daemon name and path. lmgrd uses this line to start the vendor daemon.

  • Options file path

  • Vendor daemon TCP/IP port number (default 2080).

Syntax

VENDOR vendor [vendor_daemon_path][[options=]options_file_path] [[port=]port]

Example

VENDOR adskflex adskflex.opt port=2080

FEATURE / INCREMENT line

FEATURE / INCREMENT lines describe specific licenses. A single FEATURE (or INCREMENT) line may be followed by several INCREMENT lines, creating separate license pools.

Syntax

{FEATURE|INCREMENT} feature vendor feat_version exp_date num_lic SIGN=sign [optional_attributes]

Example

FEATURE MayaUnltdf sgiawd 7.000 17-aug-2005 2 001122334455

PACKAGE Lines

PACKAGE lines provide an outline to licensing product SUITEs, and facilitate distribution of features which largely share the same FEATURE line arguments. PACKAGE lines are ineffective on their own account; they require FEATURE / INCREMENT lines to effectively activate these licenses.

Syntax

PACKAGE package vendor COMPONENTS=pkg_list SIGN=pkg_sign

Example

PACKAGE suite_example vendor_name version SIGN=12345 COMPONENTS=”feature_1:version_1:3 feature_2:version_2:4″

FEATURE suite_example vendor_name version issue_date 2 SIGN=54321 SN=123

In this case, checking out either feature_1 or feature_2 will also check out the suite_example suite. The total number of available licenses is 3×2=6 for feature_1, and 4×2=8 for feature_2.

Please visit www.openlm.com for more information about software license management.

Please follow and like us:

What is new in OpenLM version 1.8

OpenLM 1.8 is out !

The release of this milestone version is a big deal for us here in OpenLM, and we are sure you will feel the same when you start working with it.

Note for OpenLM veterans:

At this stage we recommend not to upgrade OpenLM 1.7 production systems to 1.8, but rather to install it at a sandbox, side by side with the 1.7 production server. This is in order to ensure that full functionality has been maintained in your environment, and to familiarize yourself with the new version.

This document goes over the main features that have been added or enhanced in this version, and the list is quite long:

  • OpenLM Server engine
  • EasyAdmin: Personalization, New reports, Enhanced report windows,
    Moving configuration options to EasyAdmin
  • Support of License management tools
  • Active Directory
  • Named Users support
  • Packages
  • Projects
  • Permissions
  • License Usage
  • License Procurement table
  • License Usage Efficiency report window
  • Licenses not in use report window
  • Recent Feature Denials report window
  • License Servers
  • Session Idle time measurement
  • Database manipulation
  • ArcGIS Borrowed Licenses issue
  • OpenLM Broker
  • OpenLM Agent
  • ArcGIS Set Licensing level tool
  • Installation Process
  • Logs uploader

OpenLM Server engine

The OpenLM server integrates information from various sources in order to create accurate and coherent license usage information. All processing algorithms were reviewed and rewritten as needed in order to improve accuracy and processing speed.

EasyAdmin

The EasyAdmin web application has undergone facelift surgery, is more user friendly, and generally looks nicer. Some graphic presentation windows have been added, and others have been improved in both clarity and robustness.

Personalization:

EasyAdmin windows’ configuration and user settings are now maintained by the OpenLM database, not on the browser’s cache memory (as was in version 1.7). This provides the ability to personalize the EasyAdmin appearance, and get the same user’s view on different computers.

New reports

The new reports are hereby listed. Elaboration on each of these windows is provided below:

  • The License denial widget.
  • Procurement table: Shows licenses’ procurement path, providing detailed expiration information.
  • License usage efficiency report: Histogram per single feature, showing how much of the time have N licenses been used.

Enhanced report windows

Report windows have also been enhanced. It is now possible to:

  • Export chart images or PDF documents and
  • Set report window refresh period


Moving more configuration options to EasyAdmin

Several configuration options were moved from the OpenLM server configuration tool to the EasyAdmin web application, making them accessible from anywhere. One such option is the usage logging according to projects, as depicted below:

Support of License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 now supports the following concurrent license servers: FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy. In addition to that, support of some license management tools was enhanced. Here are some of these enhancements:

  • FlexLM: Asset Info information, which is unique per license pool is now monitored. Hence, it is now possible to follow user and group license check out per license pool.
  • FlexLM: Software packages are automatically recognized, and populated by the respective software products. Single features can be associated with different software packages.
  • IBM_LUM license manager monitoring has been added expiration date.
  • IBM_LUM Offline Licenses indications.
  • IBM_LUM HAL (High Availability Licensing) configuration support.
  • DSLS has been fully integrated into the OpenLM 1.8 system.
  • DSLS License borrowing is reported.
  • BetaLM has been introduced in the 1.8 version.
  • BetaLM Cluster configuration is supported.
  • RMS: License versions’ reporting was added.
  • Easycopy LM has been fully integrated into the OpenLM 1.8 system.
  • Matematica (MathLM) has been fully integrated into the OpenLM 1.8 system.

Active Directory

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP (Active Directory) to combine license management with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

In version 1.8, Active Directory synchronization has been profoundly improved, to support versatile and complex Active Directory environments. As a bonus, a preview of the impending synchronization scheme is now available. For more information please refer to these documents:

Application Note 2029_a: LDAP (Active Directory) Synchronization. Basic guide v1.8

Application Note 2029_b: LDAP (Active Directory) Synchronization. Comprehensive guide v1.8

Version 1.8 now allows system managers to easily synchronize very complex structures of LDAP. In EasyAdmin the user can now control the execution of the synchronization, exclude groups and users from synchronizing and understand why each synchronized entity was generated.

EasyAdmin incorporates new administrative tools for LDAP synchronization. These provide a better view of the synchronization definitions and the relations between synchronized entities. Group and Users entities are interconnected by hyperlinks, to facilitate the browsing through LDAP synchronized data.

Named licenses support

FlexLM gets its licensing information from the license file, option file and other resources.

The License file contains the asset info information which is unique for every license pool.

The License file also contains asset info associated with groups. OpenLM Version 1.8 can be configured to read Flexnet publisher license files, and hence can report which user takes licenses from which pool.

License Suites and packages

OpenLM 1.8 is capable of integrating more information from FlexLM license files. One of the benefits of that is the capability of arranging licensed features within their respective license packages. The user does no longer need to configure packages’ members manually.

In addition to that, OpenLM 1.8 supports licensing schemes in which single features are associated with two different packages.

Projects

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some major modifications have been made:

  • The configuration of Project monitoring was shifted from the OpenLM Server configuration tool to the EasyAdmin web application.
  • Administrative capabilities have been added, such as Enabling / Disabling a project, assigning it a priority and expected duration, and marking the project’s completeness percentage.
  • Projects can now be assigned to user groups (not just to individual users).
  • Projects can also be introduced by end-users via the OpenLM Agent module. Please see the ‘Agent’ section below for more information on that.

For more information on monitoring licenses according to projects in OpenLM 1.8 please refer to this document:

Application Note 2030: OpenLM license usage monitoring according to projects – v1.8.

Permissions

New users are automatically associated to the “Everyone” group. After being synchronized (or associated manually) to a different group – the new group becomes the default group.

License Usage

The central “License Usage” window’s graphic presentation was improved, and now employs a cleaner GUI, with a zoom-in option.

License Procurement table

Shows comprehensive license information, as appears in the license file: Licensed packages and their member features, issuing and expiration dates, Asset info etc.

License Efficiency report

A new window that provides a histogram of usage for a single feature, showing how much of the time have N licenses been used. The image below clearly demonstrates ineffective usage of the pool of licenses:

Licenses not in use report

Single out licenses that have not been used for a predefined period of time.

Recent Feature Denials report

A graphic presentation to show a comparative chart of the number of license denials over predefined periods of time: recent and long term.

License Servers

Reported license servers’ information has been enhanced to include:

  • License server timezone
  • Status of the OpenLM broker installed on the license server machine
  • Host availability indication


Session Idle time measurement

Graphical waveform presentation of the Active / Idle ratio for currently and historical sessions.

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database. It is now possible to

  • Archive or delete old data.
  • Extract irrelevant users and
  • Delete unnecessary groups.

ArcGIS Borrowed Licenses issue

We previously reported an issue pertaining to the upgrade of ArcGIS to the newer FlexLM version. This issue manifested in erroneous reporting of license borrowing. OpenLM 1.8 bypasses this issue and shows the actual borrowing user.

OpenLM Broker

The OpenLM Broker has undergone important changes. These include:

  • Enhanced robustness
  • Enhanced compatibility with a wide array of license managers
  • Ability to read FlexLM license files and Audit logs, in addition to Option files.
  • Implementation of buffers for Broker messages, providing the ability to overcome limited network connectivity failure and continues usage reported even if the OpenLM Server machine crashes for long period of times.

OpenLM Agent

The OpenLM Agent has changed skin and looks much nicer now.

It also integrated the improvements for the following features:

  • Restoring of closed sessions
  • Searching and sorting of the license usage list
  • Selectively hiding or showing specific features
  • ArcGIS licensing level determination (see below).
  • As mentioned above, projects can be introduced by end-users via the OpenLM Agent. Just click the “Create New Project” menu item in the OpenLM Agent interface:

The “Create new Project” window opens. Users can then create new projects and associate their working hours to these projects.

For more information please refer to this document:

Application Note 2030: OpenLM license usage monitoring according to projects – v1.8.

ArcGIS Set Licensing level tool

ESRI implementation is unique in the sense that you can activate the ArcMap software in three different licensing levels:

  • Basic (Previously called viewer or ArcView)
  • Standard (Previously called ‘ArcEditor’)
  • Advanced (Previously called ‘ArcInfo’)

ArcGIS end users can set the licensing level before activating the software. If such a license is available, the software will start. OpenLM has provided this capability since version 1.6 of the software. In version 1.8 we have highly enhanced it:

  • It is now possible to set the licensing level according to available licenses, and
  • The user can choose whether to save the ArcGIS licensing level to the Registry, to do it on a user level, or on a system level (for all users – requires administrative permissions).

Installation Process

The OpenLM installation process has been standardized, and is more coherent on OpenLM version 1.8.

Logs uploader

The Logs uploader has been rewritten, and its robustness has been improved.

Please follow and like us: