Application Note 1027_a: OpenLM Agent Installation and Configuration

OpenLM Utilizer Agent

The OpenLM Utilizer Agent is the end user tool of the OpenLM system. It completes the OpenLM license monitoring tool from the End user’s point of view. It provides end users the following capabilities:

  • Query license availability.
  • Check which users are holding required licenses.
  • View a user’s full set of details as they appear on the LDAP, and communicate with users regarding license availability.
  • Receive license availability notifications as soon as requested licenses become available.
  • Report the session’s active project (mainly for billing purposes).

OpenLM Active Agent

The Active Agent incorporates all the characteristics of the Utilizer Agent. On top of that, it supports an extension that enables system administrators to shut down open applications either manually, or by defining a timeout policy. In this manner, system administrators can suspend or save and close idle applications, in order to make more efficient use of licenses. The Active Agent features a user-friendly interface that enables users to quickly reopen closed applications, or resume suspended ones.

Installation

Download and save the Openlm Utilizer or Active Agent MSI installation file from the Download section of OpenLM’s site. Double-click it, and follow the instructions of the installation wizard.

When installing the Active Agent, the Extensions “OpenLM Extensions” dialog window appears.

The user may either:

  • Select to install the appropriate software extensions, thus ruling an idle application to be treated in the “Save and Close” method, or
  • Select NOT to install the appropriate software extensions, thus ruling an idle application to be treated in the “Suspend and Resume” method, even though it is an “Extension Supported” application.

For more information on Extension-Enabled applications, please refer to “Application Note 1005: Configuring OpenLM to close idle Licenses”.

At the end of the installation process, in the “Agent Configuration” dialog window, type in the OpenLM server with which the Agent is required to connect, and click the “Apply” button. The Installation is now complete, can be changed at any time (see below).

After installing:

The OpenLM Agent icon appears on the “system tray”.
OpenLM Agent in a connected state:
OpenLM Agent in a disconnected state:

Agent Configuration

  • Right click on the agent icon and select ‘OpenLM Agent Configuration’. The Agent configuration window opens.
  • Select the Agent’s language.
  • Type in the OpenLM server name or IP.
  • Type in the OpenLM server port. This is by default 7012.
  • Click the “Check connectivity to OpenLM server” button.

Advanced settings:

  • Logger Configuration File: Type in the location of the Agent Log File.
  • Logging Level: Adjust the Agent’s logging level.
  • Skip Double Instances Alert: This option either enables or blocks alerts when trying to open two agent sessions simultaneously. This option is set active by default.
  • Use Local Computer’s Proxy Settings: This setting may solve issues that originate using a proxy server. This option is set inactive by default.
  • Shut Agent when products Are inactive… : These parameters are relevant for VM servers. When OpoenLM closes a licensed application, the VM (e.g: Citrix) is kept in use by the workstation, unnecessarily consuming a license. This configuration shuts down the OpenLM Agent after INACTIVITY_TIME, thus releasing the VM license.

The OpenLM Java Agent window

The OpenLM Agent window shows the Feature usage status, per License Server, Vendor and User name. Individual user data is also available through the Agent; Just click a chart line to get more information on the user who is currently occupying the license.

Revision 0.1, Apr29 2012.

The OpenLM Forum returns !

After the previous OpenLM Forum has fallen victim to spam, we have decided to clean up the stables and start fresh.

The new Forum would be accessible for everyone to read, but posting priviledges would be manually granted to confirmed customers only.

We hope it would rise as a knowledge-base and a source for cooperation between OpenLM customers.


Application Note 1027: OpenLM Java Agent Installation and Configuration

General

The OpenLM Java Agent is an end-user tool that enables OpenLM to interact with the end user in order to promote license availability. System administrators are granted full control over any functions available to the end user.
The OpenLM Java Agent is a “lightweight” software component. It is apparent on screen as an icon, located on the end users “System tray bar”. The Java Agent facilitates the following abilities:

  • Query license availability, license users and full users details.
  • Receive license availability notifications.
  • Report any active projects.

This article elaborates the installation process of the Java Agent.
The OpenLM Java Agent can run on any Java supported system. It is primarily intended for UNIX or Linux OS. OpenLM provides a native Windows agent recommended for a Windows environment.

Prerequisite

It is necessary to have the Java Runtime Environment (JRE) version 1.6 (or newer) installed.

Installation

1. Unzip the Openlm Java Agent zip file and copy all files from the Agent directory to a folder.
Ensure that the target folder does not have “read only” permissions.

2. Run the software using a terminal on the Unix \ Linux workstation:
cd to the target folder, and run the command:
java -jar openlm_agent.jar &

If the following message appears, make sure that the Java software is in the system path or uses full path.

After installing:

The OpenLM Agent icon appears on the “system tray”.
OpenLM Agent in a connected state:      
OpenLM Agent in a disconnected state:

The OpenLM Agent may be set to start with your system; this setting is available in all UNIX/Linux systems.

Agent Configuration

  • Right click on the agent icon and select ‘OpenLM Agent Configuration’. The Agent configuration window opens.
  • Select the Agent’s language.
  • Type in the OpenLM server name or IP.
  • Type in the OpenLM server port. This is by default 7012.
  • Click the “Check connectivity to OpenLM server” button.

Advanced settings:

  • Logger Configuration File: Type in the location of the Agent Log File.
  • Logging Level: Adjust the Agent’s logging level.
  • Skip Double Instances Alert: This option either enables or blocks alerts when trying to open two agent sessions simultaneously. This option is set active by default.
  • Use Local Computer’s Proxy Settings: This setting may solve issues that originate using a proxy server. This option is set inactive by default.
  • Shut Agent when products Are inactive… : These parameters are relevant for VM servers. When OpenLM closes a licensed application, the VM (e.g: Citrix) is kept in use by the workstation, unnecessarily consuming a license. This configuration shuts down the OpenLM Agent after INACTIVITY_TIME, thus releasing the VM license.

The OpenLM Java Agent window

The OpenLM Java Agent window shows the Feature usage status, per Server, Vendor and User name. Individual user data is also available through the Agent; Mark a chart line and click the “Show Users” button to get more information on the user who is currently using the license. (See license usage information below)

Revision 1.1, Apr29 2012.

SECOPTENA and OpenLM exhibit in the Siemens PLM and GIS Talk conferences:

SECOPTENA and OpenLM exhibit in the upcoming Siemens PLM and GIS Talk conferences:

Siemens PLM Connection 201208.05.2012 to 09.05.2012

Lufthansa Training & Conference Center, Seeheim
http://www.plm-benutzergruppe.de/

Secoptena

 

GIS Talk 2012

22.05.2012 to 24.05.2012
Dolce Munich, Conference Center & Hotel
Unterschleißheim bei München
http://gistalk.de/

 

Come and meet us there.

ESRI ArcGIS 10 Service Pack 4

ESRI has announced the release of ArcGIS 10 Service Pack 4. The new service pack is now available for download from ESRI’s patches and Service Packs download site. Download and installation of the new service pack is straightforward, and the software update runs seamlessly.

As far as OpenLM is concerned, Service Pack 4 does not incorporate fixes to the ArcGIS License Manager. Hence, transition to the new Service Pack should be transparent to OpenLM as a monitoring tool of floating licenses.

Please note that previous Service packs have included fixes to the ArcGIS License Manager. Here is a full list of the issues that were addressed and solved in ArcGIS 10 Service Pack 4, as well as in previous Service Packs.

FAQ: Flexera lmgrd log file is very big


The lmgrd log file collects all license check out / check in activity. This log would continue to increase in size and as long as the licensed service is running.

The log is cleared when the licensed service is restarted.
This can be done via Flexera’s LMTOOLS UI.

On The “Services/License File” tab choose the licensed service. e.g.: Autocad.

On the “Config Services” tab – you can view the log (e.g: Autocad.log) and its path.

On the “Start/Stop/Reread” tab, use the marked buttons. This would clear the service log file (Autocad.log) and restart logging.

One of the advantages of the OpenLM system is that the accumulation of large amounts of data in this log file is made redundant. The OpenLM Broker is a component in OpenLM’s system which reads the licensed log file, and reports its content to the OpenLM server. There this information is processed and exhibited in a clear and negotiable manner.

 

 

OpenLM Maintenance Release Version 1.7.1.8

Version 1.7.1.8

Version 1.7.1.8 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.1.8:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.


What’s new in version 1.7.1.8 ?

OpenLM Server:

  1. Changes made to the Readme text, apparent during  the OpenLM Server installation.
  2. EasyAdmin: Fixed User Details for user names with special characters.
  3. Mobile: The OpenLM EasyAdmin Mobile application has been added to the installation files. The Mobile application enables system administrators to keep track of the license management systems, while being out of office.
  4. Working days computing error was fixed.
  5. EasyAdmin: Color selection problem on report charts was fixed.
  6. HASP: Errors in reading certain formats of the HASP license output files were fixed.

SECOPTENA is exhibiting OpenLM at the PlanetPTC Live 2011 conference in Stuttgart, Germany

SECOPTENA, exclusive OpenLM Distributor for Germany & Austria is exhibiting OpenLM at PlanetPTC LIVE 2011. The conference is taking place in Stuttgart, Germany, November 15 and November 16.

The OpenLM team is eager to meet you there. Just stop by or fix an appointment now!

Email SECOPTENA: info(at)secoptena.com or call SECOPTENA: +49 8151 77499-55

For more information:

Images from the PlanetPTC conference:

Application note 1014: OpenLM support for the Sentinel HASP license manager

General

OpenLM versions 1.6 and higher feature the ability to monitor Sentinel HASP and Sentinel RMS license servers. OpenLM supports the full functionality of the system for HASP and RMS licenses:

  • License inventory reporting.
  • Managing active users.
  • License billing.
  • Statistics and charts.
  • End user productivity tools, and more

Along with the support for SafeNet Sentinel software, OpenLM also supports FLEXlm, FLEXnet, IBM LUM, RLM and LM-X.

OpenLM system requirements

OpenLM supports HASP versions 5.0 and higher. Versions 3 & 4 are not supported.

Adding a Sentinel HASP Server

Please follow the action list below to add a new HASP license server. Observe the following image for further clarification.

  • Open the OpenLM Server configuration tool, on the License Servers tab (1).
  • Click the “Add” button to create a new License manager entry (2).
  • Select HASP from the “Type” drop-down menu (3).
  • Server connectivity configuration (4):
    • Hostname: Type in the HASP server name or IP (e.g.: new_hasp_server).
    • Port: Type in the port of the “Sentinel Hasp Control Admin Center”. This value is by default 1947.
    • Is Triad Configuration: Click the check box according to the License server’s configuration.
  • Additional information (5):
    • Add an informative description of the License Server (e.g.: My HASP license manager).
    • Select the time zone.
  • Finalization (6):
    • Check the “Enabled” check box
    • Click the “Apply” button

HASP Server Settings

If the OpenLM Server is installed on the same machine as the HASP license serve, then no additional setting is required.
If OpenLM Server is installed on a different machine than that of the HASP server, Open the “Sentinel Hasp Admin Control Center” port (default 1947) on the firewall. Change the settings of “Sentinel Hasp Admin Control Center” to “Allow Remote Access to ACC”. See the image below for clarification.

OpenLM EasyAdmin display screenshots

OpenLM may display the Sentinel HASP License inventory (below):

As well as other license usage information, such as the currently active products (below):

Application Note 1010: OpenLM license management system Complete Installation guide.

General:

This guide describes the process of Installing the OpenLM license management system version 1.7, and applying its basic configurations to get it running in a client company’s work environment. The setup process consists of the following stages:

  1. Selecting the system’s components according to the system’s requirements

  2. Installing the OpenLM components

  3. Configuring the OpenLM components

  4. Setting up the OpenLM database

  5. Running OpenLM 1.7, checking its proper functionality

Components of the OpenLM system

OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module. In addition to those, further optional components are available. These optional components are:

  • OpenLM Broker

  • OpenLM Agent

  • OpenLM Alerts

  • Log file Uploader

The OpenLM software package also includes extensions, which provide additional functionality such as:

  • OpenLM Active Agent

  • External DB support

  • Groups and projects management

  • Role base security

  • Option file management

The image below depicts a generalized block diagram of OpenLM’s license management solution:

OpenLM Server

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.

OpenLM EasyAdmin

OpenLM’s EasyAdmin is the administrative interface of the OpenLM system. EasyAdmin’s control panel features a desktop interface that facilitates:

  • Configuration of the OpenLM Server, OpenLM’s core component

  • Management of license servers

  • License usage data extraction for Investigative and statistics purposes.

OpenLM Broker

The 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 Alert

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

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system.

OpenLM Active Agent

OpenLM’s Active Agent extension allows system administrators to define a timeout policy. In this manner, system administrators can save, close or suspend idle applications, in order to make more efficient use of licenses.

OpenLM External Data Base (DB) Support

This extension enables OpenLM to save license usage information on an external database such as an Oracle or MS SQL Server. By default, OpenLM uses an embedded DB. External DB support is recommended for management of large licensing systems.

OpenLM Groups & Projects

This extension enables OpenLM to collect license usage information from groups of users or projects. The Groups & Projects extension synchronizes users’ data with its LDAP database (Active Directory), keeping the data collection process fully automatic.

OpenLM Role Based Security

The OpenLM Server supports a role-based security feature that enables it to implement customized access to OpenLM tools by setting access roles.

OpenLM Option File Management

The OpenLM Option File Management extension enables system administrators to manage Option Files easily from the EasyAdmin web based interface.

OpenLM Logs Uploader

The OpenLM Logs Uploader extension enables loading historical FLEXlm debug log files. This extension is essential for investigating historical license usage.

System Requirements

OpenLM has published the system requirements for the new version 1.7. Please observe these requirements and ensure the system is compliant to it.

http://www.openlm.com/index.php?option=com_content&view=article&id=20&Itemid=26

You may also find this OpenLM FAQ guide useful.

Installing the system components

The OpenLM System components are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.7 section:

OpenLM Server

Start the installation process by installing the latest OpenLM server version.

If this is not a new installation, the production database file must first be backed up: Copy the “OPENLM_DB.GDB” file (typically located under “C:\Program Files\OpenLM\OpenLM Server\db”) onto a different directory.

Continue the installation process:

1. Download the OpenLM Server package to its designated machine.

2. Read the license agreement and the subsequent information page.

3. Follow the standard installation instructions. The OpenLM Server configuration tool opens on the “License Servers” tab.

4. Add a new license server:

  • Click the ‘Add’ button.

  • Type in the License server’s host name or IP (e.g. lm10) and Port number (e.g. 27000) Default Port numbers per license server type are elaborated here.

  • Select the new License server’s type (e.g. FlexLM) Please also refer to Server type respective Application Note: FlexLM, Reprise RLM / IBM LUM / Sentinel RMS / Sentinel HASP / DSLS.

  • Type in an informative name (e.g. “lm10 – ArcGis server”)

  • Select the license server’s time zone (e.g. UTC+1)

  • Check the “Is Triad” according to the License managers redundancy layout.and whether

  • Check the ‘Enabled’ check box.

5. Click the “Check” button, to check connectivity with the license server.

The image below demonstrates a configuration of four license servers.

Repeat steps 4 & 5 for all license servers.

6. Click ‘Apply’ and close the configuration window. Changes and additional configurations can be made at any stage in the OpenLM Server configuration window.

You could find it on

Windows’ Start button → All Programs → OpenLM → Server → OpenLM Server Configuration

7. Register the OpenLM server tool, and finish the installation.

The EasyAdmin Interface

The EasyAdmin web application is the main OpenLM users interface.

You could find it on:

Windows’ Start button → All Programs → OpenLM → OpenLM EasyAdmin2.

The OpenLM EasyAdmin opens. Click the start EasyAdmin start button to explore this application’s features.

The image above is an example of an EasyAdmin workspace. It features Administrative tools, License data, License usage data, Graphic usage representation, Roles and permissions’ assignment, and Active Agent capabilities.

OpenLM Broker

Download the OpenLM Broker and install it on each license manager machine in the system. Select the download version according to the operating system that runs on the License manager machine: Windows or Unix/Linux.

Please refer to the “OpenLM Broker Quick start guide – Application note 1004” document for detailed information regarding the installation and configuration of the OpenLM Broker.

OpenLM Utilizer Agent (Windows)

Download the OpenLM Utilizer Agent tool, and install it on each end – user workstation that would run applications managed by the OpenLM Server.

Please refer to the Agent Installation Guide for more information. A silent installation option is available for the Utilizer Agent. Please read about this option here.

OpenLM Active Agent (Windows)

Download the OpenLM Active Agent tool, and install it on each end – user station that would run applications managed by the OpenLM Server.

Please refer to the “Agent Troubleshooting Guide – Application note 1002” for more information on Agent installation and further OpenLM extensions’ capabilities.

OpenLM Java Agent (Unix/Linu)

The OpenLM Java Agent is the equivalent of the OpenLM Utilizer Agent for Linux / Unix systems.

OpenLM Alerts system

Download the OpenLM Alerts tool, and install it on the OpenLM server machine. Please refer to the “OpenLM Alerts: Application note 1013” document for more information on OpenLM’s Alerts installation and configuration.

Setting up the OpenLM database

OpenLM uses a relational database in order to store its configuration information and license usage information. Please read this document for more details regarding OpenLM data storage. Configuring the database is done via a designated form. Please read the OpenLM Database Configuration Form document for more information on that.

Revision table

Revision

Author

Date

Remarks

0.1 – Preliminary

Orik

Oct 17,  2011

Preliminary

1.0

Orik

Oct 30, 2011

Revised.

1.1

Orik

Jun28, 2012

Revised.