OpenLM monitoring of Aveva PDMS and Aveva Marine licenses.

Aveva PDMS and Aveva Marine environments

Aveva Marine is a comprehensive suite of software modules for offshore and shipping construction projects. It integrates several views and disciplines into a single project space for superior visualization and integrity between the project components.

Aveva PDMS provides similar capabilities for 3D plant designing. Users are able to select, place, assemble and check the integrity of complex 3D plant schemes.

Aveva licensing

  • Prior to the 12.1. series’ version, AVEVA Marine and AVEVA Plant (PDMS) employed the Flexera Flexnet manager (FlexLM) concurrent license manager to dispense and keep track of floating Aveva licenses. OpenLM fully supports FlexLM license monitoring.

  • In the 12.1 series, Aveva has drifted from the FlexLM solution to the Sentinel RMS license management tool to manage their floating licenses. They still kept the lmutil tools within their installation folders, but from our experience – running these lmutil lmstat commands produced empty results.

  • Instead, license usage information could be obtained by the Sentinel RMS command:  lsmon.exe (In fact – we needed to upgrade the lsmon.exe version to “Sentinel RMS Development Kit Application Monitor” in order to match our Aveva version). OpenLM fully supports Sentinel RMS license monitoring.

  • Another surprise Aveva 12.1 had stored for us was the license file, which was a type of hybrid between FlexLM and RMS. It was in XML format and contained the following headers:

<?xml version=”1.0″ encoding=”utf-8″?>

<CompositeLicenseFile xmlns:xsi=”” xmlns:xsd=””>

<Hostname> … </Hostname>

<RMSlicenseFile> … </RMSlicenseFile>

<FlexLicenseFile> … </FlexLicenseFile>

<ProductFeatureMappingFile> … </ProductFeatureMappingFile>


<RevokeList> … </RevokeList>


Monitor ESRI ArcGIS borrowed licenses with OpenLM


License Borrowing is a method of linking a specific workstation to a single license instance from within the license pool. This procedure marks a license as being perpetually used on the license manager (LM), enables users to borrow a product license for a designated time period, and to operate the licensed application without connecting to the license manager.

OpenLM presents the identity of users who have borrowed ESRI licenses.

ESRI license administrators have long noticed that license borrowers are not identified by license server querying, i.e. by running lmutil -lmstat commands. Instead, the borrowed user is identified as “Activated License(s)”, which isn’t very helpful in understanding who is taking the license you need now.

Audit log information

By combining information from multiple sources, the OpenLM Server is able to determine the identity of license borrowers: Usage information is provided by License server querying, while the cross reference between the borrowed license and the user identity is provided by the ESRI Audit log.

The OpenLM Broker

The OpenLM Broker is an optional component which is run on the license server machine. It provides a degree of robustness to the data flow from the license server to the OpenLM server,  and also complements the information gathered by the OpenLM server.

Examples for such additional information provided by the Broker are license denials statistics, and feature packaging information. In its latest released version 1.8, OpenLM has enhanced the broker to read ESRI Audit logs, and extract usage information for borrowed licenses.

The following image demonstrates the naming of a borrowed license:  

This is yet another unique capability provided by OpenLM for Monitoring, Managing and Optimizing the usage of ESRI ArcGIS licenses.

For more information about the OpenLM Broker, and OpenLM benefits for ESRI users, please refer to these articles:

Application Note 2000: OpenLM system structure overview v1.8

Application Note 2004a: OpenLM Broker Quick guide version 1.8

Application Note 2004b: OpenLM Broker Comprehensive guide version 1.8

Application Note 2036: Set ESRI ArcGIS licensing Level