Siemens PLM license analysis and license monitoring

OpenLM supports license monitoring of a wide, and ever growing variety of license managers. Among those are Flexera FlexLM (Flexnet publisher), IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This group of license management utilities encompass a great variety of licensed products. One group of such licensed products is the Siemens PLM (formerly UGS) 3D & 2D Product Lifecycle Management (PLM) group.

The OpenLM tool provides high level of application usage management and optimization for PLM licenses, providing clear and valuable usage information for Managers, License Administrators and End Users.

Siemens PLM Common Licensing

Siemens PLM employs the “Siemens PLM Software Common Licensing” tool in order to deliver a consistent licensing implementation to all PLM products. It is based on the Flexera FlexNet license management tool, and has incorporated some unique characteristics:

  • The PLM Common Licensing toolkit has adopted the Siemens PLM Software-wide licensing vendor daemon ugslmd. Consequently, all Siemens PLM products gain access to common licenses utilize this same daemon.
  • The PLM Common Licensing toolkit employs a unified license file for all PLM products.
  • The default port for the PLM ugslmd vendor daemon is 28000. That was decided in order to avoid conflicts with other applications, using the default FlexLM port 27000.
  • Composite ID (CID): This is a 12 digit hexadecimal unique machine identifier that is used as part of Siemens PLM Software licensing to lock a license file to a machine. The CID is distinguished from a FLEXnet hostid by the keyword “COMPOSITE=”.
  • NX bundles and Suite Packages: These are packages that Siemens PLM Software has predefined to meet the general needs of customers at a lower cost than purchasing individual floating licenses.

For more information on Siemens PLM Software Common Licensing, please refer to this PDF.

The OpenLM advantage

The OpenLM license monitoring tool incorporates many advantages in PLM software maintenance for members of all positions in an organization. In a nutshell:

  • Managers get a clear picture of their Software assets.
  • System Administrators are freed from managing licenses.
  • End users enjoy improved PLM license availability.

Additionally, OpenLM v 1.8 Automatically sorts NX suites, to clearly display Siemens PLM application usage measuring in its true context.

Please follow and like us:

License borrowing in FlexNet (FlexLM) and Offline Concurrent licenses in IBM-LUM and DSLS

General

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 monitors borrowing of licenses on several LM types. This document presents the borrowing methods on three of these LMs: FlexNet (FlexLM), IBM-LUM and DSLS, and the OpenLM advantages in monitoring borrowed licenses.

Borrowing licenses in FlexLM

In order to enable license borrowing, the software publisher should issue a floating license file with a FEATURE or INCREMENT line that contains the BORROW keyword, for example:
INCREMENT 3d_to_2d_flattener ugslmd 27.0 06-nov-2012 1 SUPERSEDE \
DUP_GROUP=UHD user_info=”NX 2D Exchange” ISSUED=06-sep-2012 \
BORROW=2880 ck=194 SIGN=”code”
In the example above, the BORROW time was restricted tp 2880 hours = 120 days. The maximal value for borrowing licenses in FlexLM is 180 days.

A user specifies the expiration date a borrowed license is to be returned, which should be equal to or smaller than the BORROW parameter above. This expiration date is set by applying a value to the LM_BORROW environment variable. This is done either directly, or by running the lmborrow utility, or by setting it in the application (when available).

The user then runs the application while connected to the network which writes borrowing information on the client computer. The license server keeps the borrowed license checked out. If enabled by the software publisher, borrowed licenses can be returned early, prior to the borrow period expiration.

When the expiration period has elapsed, or after having returned the borrowed license early, the local borrowing data no longer authorizes the license checkout, and the license server returns the borrowed license to the pool of available licenses.

More information on Borrowing Flexnet licenses can be found here.

DSLS Offline licenses

In DSLS, Borrowed licenses are referred to as “offline licenses”. The operation of extracting licenses for offline usage is done by the Application’s “Offline Management” tab on the “Local License Management” dialog box. There, a user needs to select a license for extraction and set the duration period for offline extraction. Maximal license offline extraction is 30 days.
When querying the usage of licenses with the DSLicSrv command’s getLicenseUsage -all ,  Offline licenses should be reported similarly to the following example:
internal Id: <Workstation> …
granted since: <Time and date> <workstation> <Username> <Application full path> …
targetId: <targetId> licenseId: <licenseId> …
granted since: <Time and date> hold until: <Time and date>

IBM LUM Offline licenses

The IBM License Use Management (LUM) system also refers to borrowed licenses as “Concurrent Offline Licenses”. In order to implement license borrowing in LUM:
1. The user calls the application.
2. The application looks for an offline-nodelocked license in its nodelock directory.
If a license is found and is valid, the application runs.
3. If the application does not find a license in the nodelock directory and the
portable computer can reach a License Use Management network license server,
the application requests a concurrent-offline license from it.
4. The network license server checks if the license has an authorization for the
user, group, or for the target ID of the machine, and validates the password
provided by the user.
5. If the authorization is for a concurrent-offline license, the server creates an
offline-nodelocked license and copies it to the nodelock directory of the
portable computer. The license is marked as in use on the server.
6. The application checks that the nodelock directory contains a valid license and
the application starts. The application can now run without a connection to the
License Use Management network license server (that is, the application can
run on a portable computer).

Management of offline concurrent licenses is done in the IBM LUM windows UI:

  • The product authorization must be set to “All Allowed” to enable concurrent offline usage
  • The license offline extraction time is set. It is limited to 120 days.
  • A password is set for the license instance.

Similar options are available by the lumblt command line.
Further information on IBM LUM concurrent offline licenses is found here.

The OpenLM advantage

Borrowing a license is typically not the preferable method for license deployment. It is both expensive and hard to track:

  • As borrowed licenses are floating licenses that have been put to work perpetually, they can not be subject for license chargeback, and are more expensive than other concurrent license on the license pool.
  • Borrowed licenses are also hard to keep track of. They are no longer marked as part of the license pool. License administrators need to manually revoke such licenses as soon as they are not needed.

OpenLM monitors the usage of license managers, providing insight regarding users’ identity and the efficient license allocation. It thus presents several advantages for such license administrators:

  • Identify users who draw both borrowed and concurrent license from two different workstations, and alert upon such conditions.
  • Mark specific used licenses as borrowed, clearly presenting the user and workstation it is linked to.
  • Identify usage patterns, and advise an optimized license allocation policy.

 

Note: Please contact support at openlm.com for a list of supported license managers’ borrowed license monitoring.

Please follow and like us:

OpenLM: Concurrent license monitoring and optimization tool

What is OpenLM ?

OpenLM is a comprehensive license-management solution, designed to monitor and optimize the usage of concurrent (‘floating’) license software. OpenLM is capable of monitoring a wide variety of license managers, e.g.: FlexNet (FlexLM), Sentinel RMS, and DSLS.

Who was OpenLM Designed For?

Unlike other license management systems that only offer administration and license monitoring statistics, OpenLM also optimizes license usage in a unique manner that provides all personnel with useful license-related functions.

Organization managers:

  • Know what you have: License inventory.
  • Plan license maintenance and procurement of expensive licenses.
  • Charge projects or business units for software usage time.
  • Cut costs by dropping maintenance for licenses that are no longer in use.

Administrator view:

  • Real time usage management and troubleshooting.
  • Extract license usage statistics information and patterns.
  • Roles and Permissions: Grant licenses according to specific Users’ permissions.

End User View:

  • End users are not kept in the dark. They are informed about the status of denied licenses, and receive a License availability notification when a license becomes vacant.
  • Who is using the license I need, and what are this person’s contact details?

Supported features

License managers:

  • OpenLM interfaces a wide variety of license managers. Here is a list of them.
  • Concurrent monitoring of multiple license servers on multiple time zones.
  • Management of Floating, Node-locked and Borrowed licenses.
  • Detection of idle sessions, and retrieval of idle licenses.

Monitoring capabilities:

  • Easily review license inventory in real time.
  • Extract license activity reports (e.g. Flexnet report), with configurable resolution.

Infrastructure

  • Operational over WAN and LAN networks.
  • Interface license managers that run on UNIX, Linux, or Windows’ Operating systems.
  • Web-based user interface, applicable on any major browser.
  • Mobile interface application enhances monitoring abilities for system administrators.
  • OpenLM supports both external and embedded databases.

What does “Open” in “OpenLM” stand for?

OpenLM provides a set of open and documented APIs that enable customers and business partners to develop applications that integrate OpenLM software capabilities.

OpenLM Screenshots

Watch the OpenLM EasyAdmin screenshots on the OpenLM site.

Want to evaluate the software ?

You can get the most updated version of OpenLM from our OpenLM downloads area. After filling in your name and email – you’d be directed to the downloads’ section. The Installation process is easy and straightforward, but if you still need any assistance – please send an email to support at openlm.com, and we’ll be glad to help.

Please follow and like us:

Trouble Shoot Form: Database Item 001 (Connection to SQL Server Database failed)

Trouble Shoot Form: Item 02.001

Title Connection to SQL Server DB failed.
Category Data Base
Date Sep 26, 2011
Handled by Rachel.
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet Publisher, IBM LUM, HASP, RLM, Sentinel RMS, DSLS, LM-X
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer reported failure to connect to a new SQL Server through EasyAdmin. Succeeded in connecting it via the Configuration form “Check” button. Customer succeeded in connecting to old FB Server through EasyAdmin.
Observed during investigation Log contained fatal error:
Login failed for user ‘DPI\ORANTESTSPATIAL$’
Trouble shoot process Credentials issue
Solution Found (Options: Found/Pending/Known Issue)

Symptoms

Customer reported a failure in connecting to an SQL Server.
The “Check” button worked OK in the “OpenLM Database Configuration” dialog box, but EasyAdmin couldn’t connect to the SQL Server. See customer’s image below.

Observed during investigation

1. The customer defined the OpenLM Server (in the “OpenLM Database Configuration” dialog box) to work with SQL server using “Windows Authentication”. This means that logging to the SQLServer was done using windows credentials.

2. The customer clicked “Check” on the “OpenLM Database Configuration” dialog box, and it worked OK because the process worked fine with these windows credentials.

3. Then he started the “OpenLM Server”. It didn’t work because it had other credentials.
The customer sent a log containing these lines:

FATAL 2011-09-26 12:11:14,276 [thread 11]  SessionProducer CreateFactory – Can’t map nhibernate domains
System.Data.SqlClient.SqlException (0x80131904): Login failed for user ‘DPI\ORANTESTSPATIAL$’.

This means that a user named DPI (on server ORANTESTSPATIAL) could not login to the SQL Server, hence the system halts (FATAL error means that the application could not recover).

Trouble shoot process

  1. The “Database credentials” dialog box may be configured wrong, e.g.: check the “Embedded” check box in the window for Databases that are located on local drives.
  1. OpenLM Service credentials: In the “Windows Services” window, Select the “OpenLM Server” item. The “OpenLM Server Properties” dialog window opens. Select the “Log On” tab.

Here you can see under what credentials the service runs. By default we install it with “Local System Account” but some users change it.

We suggest acting according to one of these options:

1. Change the OpenLM Service credentials to that of a user who has both administrative permissions and a permission to login to the SQL server.

2. Another option is not to use the “Windows Authentication” (but “SQL Server Authentication”).

Please follow and like us:

Trouble Shoot Form: Agent Item 002 (All license usage information on the Agent is blocked)

 

Title License usage reporting information on the Agent is blocked
Category Permissions and Roles.
Date Jul 6, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Following the creation of an admin account in the OpenLM Server Configuration, all license usage information on the Agent is blocked
Observed during investigation
Trouble shoot process 1. Create a role.
2. Assign all the necessary resources, that will allow viewing details, to the new role.
3. Add users as members of this role.
Solution Found (Found/Pending/Known Issue)

Symptoms

The customer complained: “Every time I go to add an admin account in the OpenLM Server Configuration it blocks all license usage information on the Agent?  I’d like to password protect the EasyAdmin web application but still allow users to see the license usage through the agent. Is there a way to do this?”

Observed during investigation

An admin account on the OpenLM Server Configuration window was created. This can be done by unchecking, and then rechecking the “Enable permissions” highlighted checkbox. A small dialog box subsequently appears, requiring a name & password for the new user (e.g.: User name: admin, Password: admin).

Troubleshooting

When you enable permissions, users need to be assigned with a set of permissions that will allow them to view license servers’ details

1. Create a role: Login to EasyAdmin with the “admin” account. follow the steps described in the “Creating a new role” section of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

2. Assign resources to the new role: After you save the new role, the “Resources” tab will become enabled. Navigate to that tab. Note that it is assigned with one default resource. Now you need to add all resources that have this name pattern “server_servername” e.g. server_srv1 (where srv1 is the name of the server that you will grant access to). In order to do so, Follow the description in section “Adding resources to a role” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

3. Assign the new role to the “admin” user: In order to do so, Follow the description in section “Assigning roles to a user or group of users” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

 

Please follow and like us:

Trouble Shoot Form: Database Item 003 (Following data migration from SQL to FB, EasyAdmin doesn’t show any logging)

 

Title Following data migration from SQL to FB, EasyAdmin doesn’t show any logging
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer complained that EasyAdmin does not show any stats.
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

A customer complains that: “I have successfully connected the new database, BUT nothings seems to be logging. I have no stats showing on the EasyAdmin screen.”

Trouble shoot process

1. Make sure the license servers list is defined at the “OpenLM Server Configuration Form”
2. All settings of OpenLM are saved in the database. When you migrate to a different database (e.g.: from SQL to FB), you need to re-enter the license servers list.

  1. Switch to Firebird.
  2. Open “OpenLM Configuration Form”, navigate to “Advanced” panel, click “Export…” button and save the settings to a file.
  3. Close “OpenLM Configuration Form”.
  4. Switch to SQLServer.
  5. Open “OpenLM Configuration Form” again and you will see that servers list is empty.
  6. Navigate to “Advanced” panel, click “Import…” and import the file you saved earlier.
  7. Click “Apply” and restart OpenLM server.
  8. Check EasyAdmin.
Please follow and like us:

Trouble Shoot Form: Database Item 002 (Data migration from SQL to FB)

Trouble Shoot Form: Item 02.002

Title Data migration troubles, from SQL to FB.
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Symptoms Customer reported failure to import the SQL database to FB At first.
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

Customer reported failure to import the SQL database to FB.

Trouble shoot process

 

  1. Make sure the “Data Migration” tool version is compliant to the OpenLM version.
  2. A special version of the data migration tool is required for 64 bit computers.
  3. Migration of a database over to a new database that is not empty may result in failure to migrate certain tables. This is indicated by the following message: 

If this is the case, create a clean database again, and run the OpenLM_SQLServer.SQL” script to build the tables and try to migrate again.

Please follow and like us:

Application Note 1003_a: OpenLM Groups License Activity Report tool

The OpenLM Groups License Activity Report tool provides the ability to present an historical account of groups’ license usage sessions.

More details:

OpenLM provides an easy interface for monitoring software license usage. It does so for a constantly expanding variety of concurrent license manager types, e.g. FlexLM / Flexnet, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc.

OpenLM is capable of reporting usage according to Users, User groups, Hosts, Host groups, Organizational Units and Projects. OpenLM’s web application – EasyAdmin – presents users’ accumulated data in a variety of real-time windows (e.g. “Active Products” and “Feature Usage Status” windows), and historical usage tables (e.g. “License usage” and “License activity” windows). See the OpenLM screenshots document for more information.

At the time of writing this revision, the current OpenLM version (1.8.1.17) is not yet capable of presenting an historical account of groups’ license usage sessions (i.e. the groups’ equivalent of single users’ “License activity” window).

The OpenLM Groups License Activity Report tool provides this ability.

OpenLM License Activity

The EasyAdmin “License activity” window provides an account for all ended sessions on license managers that are monitored by OpenLM. This window contains columns for the user name, Feature name and Session start & end times. (Some items on the image below have been deleted for privacy considerations)

The users who populate this list are members of groups in the OpenLM database. These groups may be introduced either manually, or by means of LDAP (Active Directory) synchronization.

Please refer to these Application notes:

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

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

And this video:

Synchronize Active Directory, and add users manually

for more information on OpenLM Groups.

In the image above, the ‘Engineering’ group has been selected for the time period from 22/10/2012 until now. In order to provide information for the Groups reporting tool, the information needs to be exported to a CSV file, using the green arrow icon (marked by a red rectangle).

OpenLM Groups reporting tool

Once the License Activity information was exported to CSV, the OpenLM Groups reporting tool may be employed:

  • Open the OpenLM Groups reporting tool.

  • Type in the exported file path.

  • Select the Date time format (in the example above it is dd/MM/yyyy)

  • Click the Start button.

After the tool is run, a CSV format file should be created and its directory presented on the desktop. This file’s default name is OpenLMGroups.csv, and it contains an historical account of OpenLM groups’ license usage

The default location for the output CSV, as well as for Log files is

For post-Vista Windows’ version:

C:\Users\<username>\AppData\Roaming\OpenLM\OpenLMGroupsReport_Log.txt

C:\Users\<username>\AppData\Roaming\OpenLM\OpenLMGroups.csv

For pre-Vista Windows’ version: this would be at:

C:\Documents and Settings\<username>\Application Data\OpenLM

Please follow and like us:

Application Note 1032: Monitoring FlexLM license denials

General:

OpenLM monitors and optimizes the usage of various license managers (e.g.: FlexLM / Flexnet publisher, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc).

As part of FlexLM license monitoring, OpenLM also produces license denial reports, i.e.: an account of instances where the vendor daemon has declined an application’s license request. License denial is a key parameter in license maintenance and in the planning of additional license procurement.

The Denials report window

License denial information is clearly presented in the OpenLM EasyAdmin web interface, in the Reports → Denials window. It includes the details of the denial event (Denied user, Denied workstation, Time, License Server, Denied Feature, and vendor) as well as the cause for denial (e.g.: limit of available licenses reached or User on Option file exclude list)

Set up OpenLM to monitor license denials

In order to produce denial reports for monitored licenses, please:
1. Set up the OpenLM Server to monitor the License server. In this case, the host is vmw_win2008_64, its type is FlexLM, the Server port is 27000, and the time zone is Central:

2. Install the OpenLM Broker on the License server machine:
Application Note 1004: OpenLM Broker quick start guide
Make sure that the License server name is exactly (case sensitive) the same as configured in the OpenLM server configuration tool (e.g.: vmw_win2008_64). The OpenLM server in this example resides in 102.101.100.135. The Broker communication port is (by default) 7016.

3. Set the OpenLM Broker to read the Denials’ information from the Monitored application’s debug log file: Type in the filename and click the ‘Enabled’ check box in the image below. Click ‘Apply’ and “Restart Broker” to finalize the configuration.

4. Make sure the Broker indication in the EasyAdmin “License Servers” window turns green. Note the green rectangle adjacent Server name vmw_win2008_64 in the image below. If it isn’t so – wait a while and refresh the “License servers” window. If it is still red – recheck your configuration, and check for alerts in the Easy Admin → Start → Management → Alerts window.

License number surpassed: Case study

In case the number of licenses has been surpassed – the vendor daemon would deny the license request, and a license denial notification will be produced. In the case of AutoCad: this is Network license error -96.

The debug log file shows this too as a string
Licensed number of users already reached. (-4,342)
Note the last denial report at 4:12:22 (Central time US):

It would also be apparent on the EasyAdmin Denial reports window at 11:12:22, according to the difference in time zones between the location of the OpenLM Server (Europe) and the AutoCad License server (Central time, US).

This same information can be presented as a column or pie chart, according to Users, Servers, Vendors, Features or time of occurrence.

Troubleshoot: Denials do not appear in the Flexnet debug log

Denial reports may not appear in the FlexLM debug log if the application’s option file contains a NOLOG line, with a DENIED flag. If this is the case, edit the option file to exclude this flag, and restart the license server. See this document for more information.

Document Revision Table

Version Author Date Changes
0.1 – Preliminary Orik Oct 25, 2012 Preliminary
1.0 Orik Dec 17, 2012 Added troubleshoot

 

Please follow and like us:

Get more out of your floating licenses

OpenLM is a complete floating license management solution designed to optimize the use of licensed software: more production for lower cost.
OpenLM is made to harvest idle licenses, and improve license utilization of any organization: big or small.

Who was the OpenLM Utilizer Designed For?

Unlike other license management systems that only offer administration and license monitoring statistics, the OpenLM Utilizer optimizes license usage in a unique manner that provides all personnel with useful license-related functions.

Organization managers:

  • Know what you have: Inventory.
  • Plan license maintenance and procurement of expensive licenses.
  • Charge projects or business units for software usage time.
  • Cut costs by dropping maintenance for licenses that are no longer in use.

Administrator view:

  • Real time license usage management
  • Alerts – Real time troubleshooting
  • Extract usage statistics information and patterns as reports or charts.
  • Roles and Permissions: Grant licenses according to specific Users’ permissions. Enforce concurrent License restriction.

End User View:

  • End users are not kept in the dark. They are informed about the status of denied licenses.
  • Receive a License availability notification when a license becomes vacant.
  • Who is using the license I need?
  • What is this person’s contact details?

Supported features

License managers:

  • OpenLM interfaces a wide variety of license managers, e.g.: FLEXlm / Flexnet, IBM LUM, Sentinel RMS, Sentinel HASP, RLM, DSLS and other leading license managers.
  • OpenLM supports Concurrent monitoring of multiple license servers on multiple time zones.
  • OpenLM supports management of Floating, Node-locked and Borrowed licenses.

Monitoring capabilities:

  • Easily review license inventory in real time.
  • Extract license activity reports, with configurable resolution.
  • Receive FLEXlm reports, statistics and charting (FLEXnet reports).
  • Receive Billing reports for any time period, per user or software (FLEXbill capabilities).

Infrastructure:

  • OpenLM may work over WAN and LAN networks.
  • OpenLM employs a web-based user interface that works with any supported browser.
  • A Mobile interface application enhances monitoring abilities for system administrators.
  • OpenLM may interface license managers that run on UNIX, Linux, or Windows’ Operating systems
  • OpenLM supports both external and embedded databases.

Proactive capabilities:

  • Release orphan licenses with a single mouse click.
  • Query users and licenses from any workstation.

Other features

  • A customizable alert system
  • An open, detailed API

OpenLM Architecture

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 Broker, OpenLM Alerts module and the OpenLM Utilizer Agent modules are also incorporated in the basic software package.

The OpenLM Server

is the core element of the OpenLM system. It integrates the functionality of all other peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. The OpenLM Server is implemented as a Windows service and could be installed on any network machine.

OpenLM EasyAdmin

An HTTP based application that can run on any machine in your network. EasyAdmin is the reporting and management interface of OpenLM. It facilitates extraction of lisence usage statistics, and usage repots, as well as the control and optimization of license usage.

OpenLM Agent

An optional component that can be installed on any machine on the network. The Agent enables end users to query license availability and find who is using the license they need at any point in time.

OpenLM Alerts

is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met.

OpenLM Broker

is an optional server component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server, and is required in order to provide advanced licensing information and sophisticated abilities.

OpenLM Screenshots

Watch the OpenLM EasyAdmin screenshots on the OpenLM site.

Want to evaluate the software ?

You can get the most updated version of OpenLM Utilizer from our OpenLM downloads area. After filling in your name and email – you’d be directed to the Downloads section. The Installation process is easy and straightforward, but if you still need any assistance – Please send an email to support@openlm.com, and we’ll be glad to help.

Please follow and like us: