Serve OpenLM EasyAdmin using Microsoft IIS 6

Serve OpenLM EasyAdmin using Microsoft IIS 6

OpenLM Software is delivered with a built-in web server that starts as a service. Users can continue and use the built-in web server or use a standard web server such as Microsoft IIS 6.
These guide explains how to configure OpenLM EasyAdmin to work with Microsoft IIS 6.

1. Create easyadmin site in IIS

Open “Control Panel–>Administrative Tools–>Internet Information Services”
Right-Click “Default Web Site” and select “New–>Virtual Directory…”:
Press “Next” on the wizard:
For Alias use “easyadmin” and press “Next”:
Set directory to easyadmin path, typically “C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2” and press “Next”:
Add “Execute (such as ISAPI applications or CGI)” to the allowed access permissions and press “Next”:
Click “Finish”:

2. Config easy admin to use proxy.exe

Navigate to easyadmin directory, typically: “C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2”
Edit file “Config.js” and change “proxy.cgi” to “proxy.exe” as seen here:

3. Delete old log files

The log files are located in %ALLUSERSPROFILES%\Application Data\OpenLM\openlm_proxy.log (typically “C:\Documents and Settings\All Users\Application Data\OpenLM\openlm_proxy.log”)

4. Check that easyadmin is working

Open web browser and browse http://<web server>/easyadmin/index.html

Additional steps necessary for Windows 2003 Server (after creating the virtual directory)

Right-click the new “easyadmin” virtual directory and select “Properties”:

At the properties form click “Configuration…” button:

Click “Add…”:

At “Add/Edit Application Extension Mapping” click “Browse…” and navigate to “cgi-bin” directory (Typically in C:\Program Files\OpenLM\OpenLM Server\WebApps\EasyAdmin2\cgi-bin)

Change filter type to “CGI exe files (*.exe) and select “proxy.exe”

You need to add double quotes to the file path and set “exe” as Extension

Click “OK”.

Navigate to “Web Service Extensions”, select “All Unknown CGI Extensions” and click “Allow”:

Q&A guide for OpenLM (FAQ)

OpenLM Version 1.6.0.1 – Maintenance release

Version 1.6.0.1 is a small maintenance release fixing small problem found by our customers that upgraded to version 1.6. We recommend all users of version 1.6.0 to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.0.1?

  1. Fixed a  problem with HASP date.
  2. Active Directory syncronization doesn’t synchronize disabled users now.
  3. Narrowing license output chart when the date overlaps from one month to another.
  4. Report Tab clear filter does not clear all fields.
  5. Fixed OpenLM Broker configuration tool startup script for Windows Server 2003 and Windows XP.
  6. OpenLM Broker – when adding a new port, the default configuration will be “Periodic”.
  7. Fix OpenLM Broker installation problem when Java does not exist.
  8. Easyadmin Control Panel – Feature usage status window – make numeric columns sortable.
  9. OpenLM Agent install error on pre-vista OS’s (XP and Server 2003) solved.

Managing autodesk network licenses using OpenLM Software

General

OpenLM Software provides management tools for FLEXlm licensed Autodesk licenses. Many sites that use Autodesk software are also using OpenLM software for managing the use of Network Licenses (ADLM) also called concurrent or floating licenses.

OpenLM is not only a management software, it actively helps CAD managers and system administrators to get more usage out of their existing pool of Autodesk Network licenses.

The software functionality

OpenLM provides the full set of management tools required by CAD managers and system administrators for managing Autodesk network licenses.

Some of the common tasks in license management are:

  • Managing the existing license inventory.
  • Checking existing active sessions.
  • Removing hang-up licenses and releasing idle sessions.
  • Collecting usage time for users, groups and projects.
  • Generating usage reports and charts.
  • Planning future purchase of licenses.
  • Helping users to get the licenses they need.

A good license management software will allow the user to perform this functionality. A very good software does more:

  • Provides a friendly interface that runs on any standard browser.
  • Allows a system administrator to save and close an Autodesk software remotely.
  • Allows the synchronization of users and groups information with Active Directory.
  • Support billing policy for groups or projects.
  • Allows the editing of FLEXlm option files using a graphical UI.
  • Automatically detects and closes idle licenses when licenses are needed.
  • Provides “License Availability Notifications” for users that were denied of licenses.
  • Empowers end users to help themselves and by that save administration hours.

Why is it important to close idle sessions of Autodesk software

Users tend to grab an Autodesk network license from the license pool, for example, Autodesk Autocad, Autodesk Revit or other licenses. They may use it for while and then use other applications or leave their workstation and go away.

OpenLM constantly monitors the license usage of the Autodesk network licenses. When the requirement for license is high OpenLM starts closing idle licenses in order to assure that every user will receive the license he needs.

From our experience, organizations can achieve 40% more usage out of their existing license pool using this functionality.

How can I get OpenLM for Autodesk software?

The fully functional software can be downloaded from OpenLM website.

Which Autodesk software is supported?

AutoCad, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD MAP 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Inventor, AutoCAD Navisworks, AutoCAD Revit and more.

“OpenLM Enable” your custom application using Floating Licensing

General

Software companies provide developers the ability to incorporate their functionality in custom application. When these components use floating licensing there is a need to assure that the software uses the licenses in a smart way.

OpenLM provides a technology that allows companies to get more out of their existing license pool. The principal is that the license is automatically released back to the license pool when the application is not in use. OpenLM provides a ready made solution for software systems such ESRI ArcGIS and Autodesk software. Integration of OpenLM functionality into custom application based on components from these companies is easy and provides huge benefits.

How does it work

OpenLM is a modular software that was designed in several layers. The most significant layers are:

  • OpenLM Server
  • OpenLM Agent
  • OpenLM Extension

OpeLM Server is the mastermind that holds the brains of the software. It is the coordinator between the license manager and all other components of the OpenLM application (such as easyadmin, OpenLM,Agent, OpenLM Broker etc..).

OpenLM Agent is the the agent that resides at the end-user’s workstation and it is in charge of the communicating channel with OpenLM Server. The agent connects periodically with the server and receives instructions according to the policies that were defined at the server’s console.

OpenLM Extension is a piece of software that is attached to the software that is monitored by OpenLM. An example to such software can be ESRI Desktop ArcGIS (also ArcEngine applications) or Autodesk Autocad. The extension inspects the activity of the monitored software and reports it to OpenLM Server by using OpenLM Agent communication services.

Openlm Extension reports parameters like software idleness or CPU consumption. It also responds to server originated orders like “Shut down”. When the monitored software is idle and the licence  it consumes is required, The server sends shutdown command which the Extension needs to carry on.

What do I need to do in order to incorporate OpenLM’s capabilities in my software?

In order to “OpenLM enable” your software, you need to create your own Extension. It is much simpler than you may imagine since you only need to implement the top layer of the Extension.
As mentioned before, OpenLM software is modular and the Extension is also built as several layers:

  • Communication layer – in charge of communication with OpenLM Agent.
  • Monitoring layer – measures the software’s status (IO, CPU, idleness).
  • Janitor layer – provides system data (like software name and provider names) and performs instructions that are sent from the server (such as: “Save and shutdown current state”).

The first two layers already exist. You need to implement only the Janitor layer.

In code, it is much simpler:

  1. Reference “OpenLM_Extension” dll.
  2. Create a class that implements “OpenLM.Extension.IOpenLMExtension” interface. The main function to implement is “ShutDown” function which is in charge of closing the software.
    Note: the developer can override the Server’s ruling and decide against OpenLM Server advice.
  3. Instantiate this object on application startup.

Code samples for ESRI Desktop ArcGIS versions 9.3 and 10 (with FLEXnet FLEXlm license manager) can be found on our website downloads area.

Upgrade guide of OpenLM Version 1.5 to Version 1.6

OpenLM version 1.6 includes significant changes at the database structure and other aspects and because of that we recommend our customers to perform a preliminary upgrade test before actually performing the upgrade on the production environment.

The level of the preliminary check depends on the organization’s requirements. If the requirement is to provide a 24/7 service then a full check is recommended that includes an installation of a test system and a fully upgrading and testing of the test system. If down time is acceptable then a short DB upgrade test may be sufficient. OpenLM customers are welcomed to contact our support team and consult with us about upgrade issues.

Considering the upgrade process, the changes relevant to the installation included in this version are:
  • DB structure change.
  • The Agent software is also highly upgraded, its performance is better and it visually provides a better interface. Older versions of the agent are not compatible with the new server version so the upgrade of the agent is a must.
  • OpenLM Server configuration settings moved into the DB (older versions stored it in an XML file).
  • OpenLM Users Management software is obsolete now. All its functionality was moved to OpenLM EasyAdmin interface. The new interface is better, easier to use and faster. Group management is still a part of the Groups & Projects extension and requires additional licensing.
  • OpenLM Broker was significantly upgraded to support the advanced functionality of OpenLM version 1.6. We highly recommend to also upgrade OpenLM Broker but this can be done on a second stage, after upgrading the server.

Two different procedures are outlined in this document. One for installations that use the embedded Firebird database and another one for installations that use external database (Oracle, MS SQL Server or Firebird Server – requires additional licensing). These two procedures are also divided to two, a full and a preliminary check procedure.

Short preliminary check procedure for embedded database configuration

First stage: Backup your database file!

Navigate to the location of your OpenLM Server database file, typically: C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB and backup the database file.

Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file is risking your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation  (XP, Vista, Windows 7) and take the following steps:

  • Install OpenLM Server version 1.6 on a workstation.
  • Stop “OpenLM Server” windows service (on the workstation).
  • Copy of your production database C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB to the test workstation.
  • Navigate to C:\Program Files\OpenLM\OpenLM Server\bin and execute DBUpgrade.exe.
  • Upgrade your database and make sure that no errors are reported.

Now you can upgrade your production system.

Short preliminary check procedure for external databases

First stage: Backup your database!

Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file is risking your data.

Second stage: Upgrade your database

  • Download the appropriate database upgrade script from OpenLM Downloads area.
  • Stop OpenLM Server service and then Run the appropriate upgrade script in order to upgrade the database.
  • Make sure that no error messages are reported.

Now you can upgrade your production system.


Full Upgrade procedure with preliminary check for embedded database configuration

First stage: Backup your database file!

Navigate to the location of your OpenLM Server database file, typically: C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB and backup the database file.

Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file is risking your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation  (XP, Vista or Windows 7) and take the following steps:

  • Install OpenLM Server version 1.5.6 (the exact version you currently use) on a workstation (XP, Vista or Windows 7).
  • Stop “OpenLM Server” windows service (on the workstation).
  • Replace the database with a copy of your production database C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB.
  • Start “OpenLM Server” windows service.
  • Upgrade the system by installing OpenLM Server 1.6 on the workstation.
Test the new installation.

Third stage: Make sure your database backup is in safe place and upgrade your production system.

Upgrade is simple – install the new 1.6 package on your production server. It will update the software and upgrade your database. OpenLM service will not be available during the upgrade process.

Forth stage: Update OpenLM Agents.

Older OpenLM Utilizer Agent versions are not compatible with OpenLM Server 1.6. You must upgrade OpenLM Agent software on all workstations.
OpenLM Utilizer users are licensed to download and install OpenLM Utilizer on every workstation using floating licenses.
OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are licensed to download and install OpenLM Active Agent.
OpenLM supports different distribution methods: Start up scripts, Network management systems like CA Unicenter, Microsoft SMS or others. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on the any FLEXlm server managed by OpenLM.

If OpenLM Broker is not already installed yet then download OpenLM Broker and install it on each license server. Using OpenLM Broker highly enhance the capabilities of OpenLM Software.
We also recommend to upgrade existing OpenLM Broker installations.

Full Upgrade procedure with preliminary check for sites that use external database

This procedure is relevant to users that configured an external database with OpenLM Server. OpenLM Server supports Oracle, Ms SQL Server or Firebird server.

First stage: Backup your database!

Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file is risking your data.

Second stage: Upgrade your database

Download the appropriate database upgrade script from OpenLM Downloads area.
Stop OpenLM Server service and then Run the script in order to upgrade the database.

Third stage: upgrade your production system.

Upgrade is simple, install the new package 1.6 on your production server. It will update the software while preserving all your settings. OpenLM service will not be available during the upgrade process.

Test the system!

Forth stage: Update OpenLM Agents.

Older OpenLM Utilizer Agent versions are not compatible with OpenLM Server 1.6. You must upgrade OpenLM Agent software on all workstations.
OpenLM Utilizer users are licensed to download and install OpenLM Utilizer on every workstation using floating licenses.
OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are licensed to download and install OpenLM Active Agent.
OpenLM supports different distribution methods: Start up scripts, Network management systems like CA Unicenter, Microsoft SMS or others. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on the any FLEXlm server you may have.

If OpenLM Broker is not already installed yet then download OpenLM Broker and install it on each license server. Using OpenLM Broker highly enhance the capabilities of OpenLM Software.
We also recommend to upgrade existing OpenLM Broker installations.

Please report problems to OpenLM Team!
Email: support@openlm.com
OpenLM Site contact form.

OpenLM Version 1.6 – What is new in details

OpenLM Version 1.6 – What is new in details

Version 1.6 of OpenLM is a major release with overall improvements in many aspects of the software. This document provides an overview of the new and improved functionality of in OpenLM software.

Support for additional license managers

OpenLM now supports many more license managers:
FLEXlm (FLEXnet)
IBM LUM
Sentinel RMS
Sentinel HASP
RLM
LM-X

The support level for each license manager vary but the basic functionality is supported for all license managers.

Support for different sample intervals for each license server

System administrator can now add license managers with different license sampling interval. Sampling interval is set in seconds and provides more functionality in the system configuration.

Halting/Starting license servers

A Halt/Start button for license servers was added to the license servers screen. This ability allows system administrators to temporally halt a server sampling without removing the server from the server list.

System settings were moved to OpenLM DB

By moving the system settings into the database OpenLM allows system administrators to easily move the system from one server to another without losing the system settings. Moving or duplicating the system to another server now involves a configuration of the DB connection which is done by using the new DB configuration tool.

Exporting and Importing OpenLM Server configuration

OpenLM Server configuration tool also allows system managers to export OpenLM Server settings to XML file. The settings can also be easily imported into another installation of OpenLM.

This functionality allows system administrators to easily build and configure OpenLM Servers for testing.

Integrated authorization and role based security was added to OpenLM

A new extension to OpenLM Software now adds the following functionality:
Authorization –  Users logging into EasyAdmin need to provide a username and password.
Role based permissions – A specific set of permissions can be assigned to roles.

The new functionality allows organization to grant different access levels  to OpenLM EasyAdmin, according to the user role. For example, a dedicated role can be created to helpdesk users. Helpdesk users will be able to access limited functionality that will allow them to assist floating license users.

The new extension allows the creation of very granular set of permission for each role. The permission starts at the level of logging, tabs, and all the way to fields and buttons.

Access permissions can also be granted to specific license managers. This way, limited access can be granted to local system managers or to power users.

Compliance with the German privacy laws

OpenLM is now compatible with the German privacy laws. When set, OpenLM won’t save user names for sessions. Even when German privacy laws are set, the system is still able to collect usage information for Groups and Projects.

OpenLM Server Configuration form also allows system administrators to “Fix” this setting. After fixing this option a future change of this setting will not be possible from the server configuration form.

Support for usernames with spaces

OpenLM now supports usernames with spaces, for example: “Jack Smith”. This is not a common methodology to use spaces in usernames but it’s supported by Microsoft.

Note: This option works only when Active directory synchronization is enabled.

Managing FLEXlm Option files from EasyAdmin Interface

OpenLM now allows users to edit their FLEXlm option file interface directly from OpenLM EasyAdmin interface. This revolutionary functionality creates integration between OpenLM and Active Directory (LDAP). Users can synchronize groups of users with Active Directory, set the desired limits in EasyAdmin and save the changes to their FLEXlm option file. All this can be done without accessing the server and without editing a single line in the option file.

FLEXlm users that maintained OpenLM in the past know what a tedious task it is to maintain such a file. OpenLM now provides a menu driven interface that can save organizations expensive work hours and a better usage of the available options.

Support for multiple domain in OpenLM Active Directory integration.

OpenLM is now able to synchronize Users and Groups with multiple domains. This provides better support for international organizations and complex LDAP forests.

We have also added the ability to limit synchronized users to the ones that use licenses. This important for large organization that has many users listed in AD.

Another group synchronization method was added, “Fixed”. This method is very useful for organizations with large AD forests (International companies with subsidiaries, for example).

More effective Active Directory (LDAP) synchronization

The synchronization process between OpenLM and Active Directory (LDAP) is much more effective. It now supports huge domains that keeps a 6 digits number of objects.

Controlling the frequency of notification from OpenLM Server

OpenLM Server now allows system administrators to limit the number of alerts they get when new version of OpenLM are available.

The user can now select one of these options: Once, Twice or Weekly frequency.

An enhanced menu for the configuration of license manager tools

OpenLM now provides and enhanced and easy to use configuration menu for license managers tools and settings.

User, Groups and Project management functionality is now available in EasyAdmin

Until version 1.6 the management of Users, Groups and Projects was done by using OpenLM Users Management software. In version 1.6 we moved this functionality to OpenLM EasyAdmin.

EasyAdmin interface is faster and integrated with the main interface that OpenLM provides.

Many additional conditions were added to OpenLM Alerts

OpenLM Alert is an extension to OpenLM that was first  declared in version 1.5.4 of OpenLM. This module allows system administrators to define conditions and receive notification when these conditions are met.

For example, one can define a condition that checks if license usage rate is above a certain threshold. The notification can be written to OpenLM EasyAdmin Alerts window, email addresses, mobile phones by SMS or to the server event log.

Sending times of the alert can be limited by date and time using a sophisticated but friendly configuration tool.

The conditions available in version 1.6 of OpenLM Alerts:

  • Feature Threshold.
  • Duplicate license in use.
  • OpenLM Server Down.
  • Feature expiration.
  • License server is down.
  • Users without default group.
  • Users without default project.

EasyAdmin quick charts for license denials

Quick charts tool was added to license denial tab. It allows the user to immediately generate charts, using the license denial information. The module supports any of the columns and three types of charts: line, bar or column.

The ability to chart the the license usage information in EasyAdmin provides a valuable tool to understanding the license usage.

EasyAdmin interface to manage packages and products names

In older versions of OpenLM packages and products name were managed in XML files. End users were able to edit these files in order to add packages or new products. Version 1.6 of OpenLM features a new menu driven interface integrated into OpenLM EasyAdmin ->Control Panel tab.

Integration of detailed user information in EasyAdmin

OpenLM now integrates detailed user information. The first name and last name columns can be added to most tabs.

This image shows how these fields are integrated in EasyAdmin->License TAB

EasyAdmin users can also click the user name and get additional user information:

Better Performance and improvements in EasyAdmin

OpenLM EasyAdmin performance is highly improved compared to version 1.5.6. Performance improvements include: better date retrieval time, faster queries and more.

OpenLM Server performance improvement

OpenLM server has undergone through a major performance tuning process. New algorithms were implemented and every DB query was tuned. The result is a very significant improvement in EasyAdmin performance. Many more license servers can be monitored while lowering the load on the server.

OpenLM Broker – new interface. New possibilities

OpenLM Broker is component we recommend to install on each monitored server. In older versions its functionality was limited to reading the FLEXlm debug log files and to sending usage information to OpenLM Server.

In version 1.6 OpenLM Broker is closely integrated into OpenLM Server and provides a wide range of services to the system.

The system now supports the following functionality:

  1. All FLEXlm commands such as: Starting, Stopping, Rereading and more.
  2. Fully controlling the FLEXlm option file.
  3. Reading log files.
  4. Support for multiple license servers (IBM LUM, Sentinel HASP, Sentinel RMS, RLM and more)

OpenLM Broker is a Java software, and as such, it can run on any platform running a supported license manager (Windows, Linux, UNIX or MAC OS). Previous version also required .NET Framework for the installation stage. This version is fully implemented using Java, including the software installer.

The setup of the the new version is easier. It also features an automatic license recognition system that saves administration time.

A graphical redesign of the software

The software also features a new design and graphics. New 3D icons are integrated and the software forms look better.

OpenLM Agent – General improvements and a better license status Window

OpenLM License Usage Information window now supports sorting according to each of the grid columns. The information can be sorted by each of the column.

General improvement to OpenLM Agent: graphics, functionality and security compatibility with Windows UAC (User Account Control).

OpenLM Software is now digitally signed

All OpenLM software files are digitally signed by Comodo. This provides a better security when implementing OpenLM Software in organizations.

New EasyAdmin Window – Feature Usage Status

The new Feature Usage Status window allows system administrator to select a set of important features and monitor them. The new window provides a quick view for the selected features with links to charts for immediate charting.

OpenLM Timeout support for Autodesk Software

OpenLM for Autodesk now supports OpenLM timeout functionality for Autodesk software such as: AutoCad, AutoCAD Archiecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD MAP 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Inventor, AutoCAD Navisworks, AutoCAD Revit and more.

Previous versions of OpenLM provided this functionality to ESRI ArcGIS Desktop products such as ArcInfo, AecEditor and ArcView. The implementation of OpenLM timeout functionality in ESRI sites provided at least 40% more usage from same amount of licenses, a very significant saving.

This functionality is now available to organizations using Autodesk software.

What’s new in version 1.6 of OpenLM

OpenLM is proud to announce the release a new major version of OpenLM – version 1.6. The new version  features an overall change in OpenLM software. The new version is much more capable, fast and built for the enterprise.

These are some of the new features included in version 1.6:

  1. Support for additional license managers (IBM LUM, Sentinel RMS, Sentinel HSAP, RLM, LM-X).
  2. Support for multiple domains in OpenLM Active Directory integration.
  3. A complete rule based permission system added to OpenLM.
  4. Flexera FLEXlm/FLEXnet Option file editing in EasyAdmin.
  5. Improved performance in OpenLM Server.
  6. Users, Groups and Project management was added to EasyAdmin interface.
  7. Many additional conditions were added to OpenLM Alerts.
  8. Support different sample intervals for each license server.
  9. Compliance with the German privacy law.
  10. EasyAdmin quick charts is now available for the license denials tab.
  11. EasyAdmin interface to manage products names and packages.
  12. Integration of detailed user information in EasyAdmin.
  13. Better performance and many improvements in EasyAdmin.
  14. OpenLM Broker – new interface and new capabilities.
  15. Suspend and Resume a license server monitoring from OpenLM Server configuration.
  16. OpenLM EasyAdmin now also provides workstations IP addresses, if needed.
  17. Ability to ignore very short sessions for Flexera FLEXlm and FLEXnet licensed systems.
  18. Filter saving was added to EasyAdmin screens (Licenses, Active Products, Workstations, etc…).
  19. Exporting and importing server configuration allows easier transfer of OpenLM setting.
  20. OpenLM for Autodesk now supports OpenLM Timeout for Autodesk software.

A more detailed list is available in our blog. The software is available for download and evaluation on OpenLM Website.

For more details contact OpenLM Sales team:
sales@openlm.com
OpenLM Contact form.
USA Toll Free: +1-206-203-2191

OpenLM – LM-X license server support

OpenLM version 1.6 supports the LM-X license manager. The configuration of LM-X license managers is as easy as adding FLEXlm servers.

There is a known issue with version 3.5 of lmxutil, it does not detail users in the license output. When OpenLM is monitoring a software licensed using LM-X version 3.5 it will only report licenses, not users.

This bug is fixed in version 1.6 of LM-X. Software systems using version 1.6 of LM-X are fully supported in OpenLM.