07/05/2019 – Get Notified & Control Usage Webinar

The OpenLM Alerts module is designed to ensure the stability and availability of the organizations licensing system. It enables system managers to define alert conditions, and consequent actions that will be taken when these conditions are met. The system can…

07/05/2019 - Get Notified & Control Usage Webinar



The OpenLM Alerts module is designed to ensure the stability and availability of the organizations licensing system. It enables system managers to define alert conditions, and consequent actions that will be taken when these conditions are met. The system can handle complex conditions over multiple license servers and features. When a condition is met, the system could present alert messages on the EasyAdmin ‘Alerts’ window, on in log file or send alert messages to predefined email or SMS accounts. This document presents the OpenLM Alerts’ functionality and configuration options.

OpenLM App Manager is an extension to OpenLM for Engineering Licensing; it cannot be run without OpenLM for Engineering Licensing. OpenLM for Engineering Licensing tracks and monitors the license managers whereas Application Manager tracks and monitors applications installed on the workstation.

The usage information collected by Application Manager is presented in OpenLM reports under the license server ‘App Manager’. When the same application is monitored simultaneously both by OpenLM at the license manager and by Application Manager at the workstation, the usage data is shown only for the license manager.

Identification of pirated software usage.
Self-defined central policy for the running of software in your organization. Can permit/deny the running of applications or services according to user, application, vendor, IP and time.
Added control over the use of software already controlled by a license manager.
Restrict the number of instances of an application in concurrent use on the network.
Measurement of software consumption so you can compare it against vendor billing.
Central control of permissions to applications.
Identify instances of engineering applications that are expected to run via license manager but are in fact run independently on the workstation. Including cases of non-network licensed applications and running of unauthorized applications.
Metering actual usage of applications (active and idle periods) that are not managed by license managers (requires the OpenLM Actual Usage extension)
Built-in support for Bentley applications. Can restrict the usage of Bentley software, to a maximum number of concurrent instances in use according to the licensing terms (term license etc).
Integrates with OpenLM and is handled just like any other license manager, including reports. A single instance of OpenLM can contain App Manager and other license managers together.
Can prevent simultaneous usage of multiple application versions by a user .This solves a common problem with Autodesk that when a user executes two or more different versions of a product at the same time, a license is allocated for each one.

FLEXlm ( FlexNet publisher ) Options files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, as well as Hosts, IPs, and Host Groups according to the Options file setting.

Employing FLEXlm Options file, the license administrator can:

1. For concurrent (floating) licenses:

Allow the use of features
Deny the use of features
Reserve licenses
2. For all license types:

Restrict the number of licenses available
Control the amount of information logged about license usage
Enable a report log file
Control the automatic rereading of licenses
FLEXlm Options files are implemented as text files, located on the license server. Although this method fits the licensing requirements well, the process of creating and maintaining Options files is error-prone and difficult to maintain.

The OpenLM solution incorporates synchronization of License administration tools with the organization’s LDAP (Active Directory), keeping the FLEXlm Options file up-to-date as users leave or join the organization, or move between groups.

Creating an Options File
1. The Options file should be placed under the same directory as the vendor daemon file, in order to enable FLEXlm to read it automatically. Locating the Options file in a different folder is possible, but this requires FLEXlm to be configured to search for it in that particular location.

2. The recommended name for the Options file is vendor.opt, where vendor is the vendor daemon name ( e.g.: for the ESRI ArcGIS vendor: arcgis.opt is recommended). Note: The name should not contain any blank spaces. Use an underscore ‘_’ to create a separation between words, otherwise name will not register. i.e.: “Vendor name.opt” is not recognized.

FLEXlm Options file editing
When configuring the Options file using OpenLM, the configuration data is presented to the OpenLM Server, and forward by it to the OpenLM Broker, located on the license server machine. The OpenLM Broker updates the Options file.

0 / 5. 0

Leave a Reply

Your email address will not be published. Required fields are marked *