OpenLM Agent Maintenance Release Version 2.0.0.9

OpenLM Agent version 2.0.0.9

OpenLM Agent version 2.0.0.5 is a maintenance release to version 2.0. It contains some bug fixes to problems found in previous versions. We  recommend that users that the resolved issue may be relevant, to consider to upgrade their system to this version.

What’s new in OpenLM Agent 2.0.0.9 (February 10th, 2015)

 

  • OTRS 2015012610000108 — OpenLM Agent Extensions are not installing with ArcGIS 10.3

 

Upgrading the OpenLM Agent

The OpenLM Agent can be silently deployed over the organization’s workstations. Please refer to these documents for more information:

Application Note 3023: OpenLM Agent Silent installation

Application Note 2023a: Customizing OpenLM Agent deployment via GPO

 

Please follow and like us:

OpenLM Agent Maintenance Release Version 2.0.0.5

OpenLM Agent version 2.0.0.5

OpenLM Agent version 2.0.0.5 is a maintenance release to version 2.0. It contains some bug fixes to problems found in previous versions. We  recommend that users that the resolved issue may be relevant, to consider to upgrade their system to this version.

Upgrading the OpenLM Agent

The OpenLM Agent can be silently deployed over the organization’s workstations. Please refer to these documents for more information:

Application Note 3023: OpenLM Agent Silent installation

Application Note 2023a: Customizing OpenLM Agent deployment via GPO

What’s new in OpenLM Agent 2.0.0.4 (September 10th, 2014)

OTRS 3324#27014 – Do not show temporary projects
2202: [Extensions] Suspended process not shown in “Recently Closed” hence can’t be resumed
Please follow and like us:

OpenLM Agent Maintenance Release Version 2.0.0.4

OpenLM Agent version 2.0.0.4

OpenLM Agent version 2.0.0.4 is a maintenance release to version 2.0. It contains some bug fixes to problems found in previous versions. We  recommend that users that the resolved issue may be relevant, to consider to upgrade their system to this version.

Upgrading the OpenLM Agent

The OpenLM Agent can be silently deployed over the organization’s workstations. Please refer to these documents for more information:

Application Note 3023: OpenLM Agent Silent installation

Application Note 2023a: Customizing OpenLM Agent deployment via GPO

What’s new in OpenLM Agent 2.0.0.4 (August 6, 2014)

2159: [Extensions] Extensioned products don’t always report to recently closed docs – resolved.

 

Please follow and like us:

OpenLM Agent Maintenance Release Version 2.0.0.3

OpenLM Agent version 2.0.0.3

OpenLM Agent version 2.0.0.3 is a maintenance release to version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We  recommend that users of previous 2.0 versions to upgrade their system to this version.

Upgrading the OpenLM Agent

The OpenLM Agent can be silently deployed over the organization’s workstations. Please refer to these documents for more information:

Application Note 3023: OpenLM Agent Silent installation

Application Note 2023a: Customizing OpenLM Agent deployment via GPO

What’s new in OpenLM Agent 2.0.0.3 (July 24, 2014)

2028: [General] NX- suspension not working: lmremove executed, but Server does not suspend

Please follow and like us:

Application Note 1030: OpenLM license usage monitoring according to projects – v1.8.

General

OpenLM is able to record information about the usage of various licenses and allocate them to different company projects. This ability facilitates license allocation according to organizational projects, and can also serve as a mean to effectively charge-back license usage expenses according to these projects.

This ability complements OpenLM’s license monitoring capabilities; integrating license usage optimization with Active directory synchronization, Project assignment, and monitoring a variety of  license managers such as FlexLM (Flexnet), Sentinel HASP, Sentinel RMS, RLM, DSLS, LM-X, IBM LUM, and MathLM.

Scope

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some modifications have been made:

  • The configuration of Project monitoring was shifted from the OpenLM Server configuration tool to the EasyAdmin web application.

  • Administrative capabilities have been added, such as Enabling / Disabling a project, assigning it a priority and expected duration, and marking the project’s completeness percentage.

  • Projects can now be assigned to user groups (not just to individual users), and

  • Projects can be introduced by end-users via the OpenLM Agent module.

This Application Note describes the feature as implemented in the 1.8 version.

Project usage reporting

The Project usage reporting is available on the EasyAdmin web interface. Click OpenLM Start → Resports → Project usage in order to see the report. Set the filtering options on the left-hand side of the screen, and click the ‘Apply’ button in order to run the usage query. It is also possible to view the report in a chart format, or extract the information to a CSV file (green arrow icon at the bottom) and manipulate it on a spreadsheet software.

However, before having any information to report – it is necessary to set up the projects. Please follow the section below in order to do so.

Projects Settings

The “Projects Settings” screen defines the policy of the Project usage monitoring capability. In order to open it, click the OpenLM ‘Start’ button → ‘Administration’ → ‘Projects’ icon.

Notes:

1. Projects’ information logging requires the installation of the OpenLM Agent (Either Active Agent or Utilizer Agent) on the end-users’ workstations.

2. When the OpenLM server is configured to employ user permissions, access to this window requires administrative privileges.

The ‘Projects’ window appears:

Note:

The project configuration window was moved in OpenLM version 1.8 to EasyAdmin (under the Administration menu. Following is an account of its different configuration objects:

Log Projects Information

Check the Log projects information checkbox to start recording license usage information according to projects’ allocation.

Minimal Usage Duration for Project

This setting defines the shortest duration for logging purposes. Shorter periods would be merged together to form significant usage periods. For example, if the minimal duration is set to 5 minutes, and a user has opened the application for only 3 minutes, this usage period will not be accumulated to the current session, but rather merged with the following session.

Agent’s Behavior Settings

These settings define what the end-users will see on their workstations if they work on more than one project for their organization. If the workers are only allocated to one project in EasyAdmin then OpenLM will log their license usage without the need to take any action when the software is started. If the users work on more than one project then a dialog box will appear on their screen prompting them to select the current project.

Hide projects option from menu

Deny users the ability to determine the name of the project on which they’re working.

Projects window fades away after

OpenLM enables users to ignore the project dialog box by having it fade away after a predefined number of seconds. The Projects window fades away after setting defines the number of seconds after which it becomes invisible.

Allow creation of projects in Agent

This option has been introduced in the OpenLM 1.8 version.

The OpenLM project management module facilitates project creation via the OpenLM Agent. Check this box to enable this option, thus adding the “Create New Project” menu item in the OpenLM Agent interface (see image below).

When an end-user selects this option, the “Create new Project” window opens. The user then could create new projects and associate themselves to them.

Modification of these projects will be possible in EasyAdmin only. The origin of creation of the project will be apparent in the EasyAdmin Projects list window.

Show unassigned projects

By default, users can only see projects they are assigned to in the Agent → Set Active Project menu option. Checking this box will produce a list that contains all enabled projects in the system and the user will be able to select any project from this list. This option has been introduced in the OpenLM 1.8 version.

Support Environment Variable

The LM_PROJECT env. variable support is a backward-compatibility option, that supports this variable for registering projects. The variable is defined separately for each workstation, so there is no option of overriding its value between users.

The environment variable option is disabled by default. It is recommended to use the OpenLM supplied solution, unless backward support of the environment variable option is required.

The “Add unknown project” option presents an administrative filter for project names that are unknown to the OpenLM server:

  • Checked: The unknown project will be set and added to the list of projects.

  • Unchecked (default): The unknown project will not be set.

Selecting the active project

When logging of project information is enabled (see above), work hours need to be assigned to a specific project. When there is only one project – that project will automatically be assigned all the working hours. When there are more than one project – it is up to the end users to report on what project they are currently working.

1. One option for the end user to set the Active project is to right-click the Agent icon, and select the “Set Active Project” option.

2. Another option for setting the Active project is by a pop-up window. The appearance of this pop-up is configurable by options in the ‘Projects’ window, which was mentioned above.

Display at license retrieval

The default option is to prompt the worker to select the project when retrieving a license. This is a very useful way to ensure accurate logging of the project information, therefore the recommended setting is to leave the checkbox turned on.

Display periodically every

Users may start to work on one project, and then switch to a different one, without changing the Active Project setting. If this checkbox is ticked, a dialog box will pop up in a predefined time interval, according to the number of minutes set by the user.

Project creation in EasyAdmin

In the previous section, we have seen the mathod for creating project via the Agent. Projects can also be created via the EasyAdmin “Add project” window.  

In the “Project details” tab, the Administrator can set up the following characteristics:

  • Project name

  • Start and End time for the project

  • Number of working hours allocated to this project

  • The project’s priority, and

  • The project’s completeness percentage.

Users and user groups may be assigned to the project upon its creation, via the ‘Users’ and ‘Groups’ tabs. After configuring these items, click the ‘Save’ button.

Editing existing projects

The new project would be apparent in the Projects list window. In order to access this window, Click the EasyAdmin Start button → Users and Permissions → Project List.

This window presents options to create new projects, as well as to delete or edit existing ones. It is split to two panes:

  • The left pane serves as a filter for projects to be shown on the list on the right pane.

    • The Priority drop-down list presents Low / Medium / High priority levels.

    • “Created in” marks whether the project was created by the Agent or via the EasyAdmin window: Admin / Agent

  • The right pane consists of a list of the existing projects, and an action bar at the top.  Click the top bar icons to add a new project, delete a selected project, Edit a selected project’s properties, Enable or Disable a selected project.

Attaching users and user groups to the project

After creating a project, it is time to bind users or user groups to the different projects, according to organizational preferences. In order to do so, select the target project, and select the Users or Groups tab in the ‘Add project’ window. Then select the User or Group that would be attached to the project, and click the ‘Add’ button.

Appendix A: Projects information logging in v1.7

This application note relates to the OpenLM 1.8 version. As stated in the scope of this document, most Projects information logging capabilities are already existent in the 1.7 version. The main change of interface is due to the shift of the configuration from the OpenLM Server configuration tool to the EasyAdmin web application. Below is a screenshot of the 1.7 Projects setting tab on the OpenLM Server configuration tool for comparison.

Please follow and like us:

OpenLM Maintenance Release Version 1.7.2.5

Version 1.7.2.5

Version 1.7.2.5 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.2.5:

  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.2.5 ?

OpenLM Server:

  1. French version labels in EasyAdmin and OpenLM server corrected.
  2. Fix LM-X reading: Fix LMX multi-session reporting issue (Bug #415).
  3. Fix DSLS reading for SQLServer DB
  4. Add first name, last name to active products export (Bug #404)
  5. Correct OpenLM LightTPD path variable (Bug #396)

OpenLM Agent:

  1. Active Agent 1.7.1.1: Install extensions for every Autocad component on a workstation.
  2. Agent 1.7.1.2: Add updated French resources.
Please follow and like us:

Automatically Release “Orphan” ArcGIS and Autodesk licenses

Users of network licensed ESRI ArcGIS and Autodesk (AutoCAD) applications report cases in which licensed application were closed, but the licenses remained “hanging”, and were not returned to the license pool.

This condition may be caused by broken communication between the FlexLM license server and the workstation on which the application is running, or any other “glitch” for that matter. The answer given by the vendors to this condition is that the system administrator should manually release the checked-out license via the license administrator tool or Flexera’s LMTOOLS UI.

But this is wrong.

This problem does not manifest in any apparent error message or visible notification, so this condition may persist indefinitely. Because of that:

  • There is no way for manually and routinely tracking down and fixing this condition. This condition is only captured when there is an obvious “leak” in the amount of available licenses.
  • On top of not being able to utilize the full extent of the acquired software licenses, this condition may also cause exaggerated billing for users.

An automatic solution for the identifying and fixing this condition is therefore required, and is supplied by OpenLM. On the OpenLM EasyAdmin web application, there is a check box which is configured to do just that. It configures the OpenLM system to track down ArcGIS and Autodesk applications’ licenses which are checked out but not used, and retrieve them.

This option is set active by default. The configuration check box is found as follows:

  • Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.
  • Select the “Active Agent” icon. The “Active Agent” window opens.
  • Select the “Extension dedicated” tab, and check the “Solve license manager errors” box.

That’s it. You wouldn’t have to worry about hanging “Orphaned” licenses for ArcGIS and Autodesk applications any more.

 

Please follow and like us:

OpenLM Maintenance Release Version 1.7.2.1

Version 1.7.2.1

Version 1.7.2.1 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.2.1:

  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.2.1 ?

OpenLM Server:

  1. Fix for logs uploader.
  2. Fix for DataExporter (timeout for http request).

OpenLM Agent (version 1.7.1.0)

  1. Fixed an issue that caused the software to close without showing a notification – in some cases.
  2. Fix localization issues for countries that use comma (,) as decimal point.
  3. Fix Portuguese configuration form (Bug #309).
  4. “License Usage Information” now shows available licenses.
  5. Improved “License Usage Information” & “Recently Closed Documents” windows loading time.

 

Please follow and like us:

Application Note 1020: Manually Removing Licenses Using the EasyAdmin web application

Scope

OpenLM’s main Administrative interface, the EasyAdmin web application, enables administrators to manually retrieve licenses via designated action buttons on the “Active Products” window. This option has proven to be very useful, however it seemed to have raised certain inquiries by customers. This document sums up the properties and limitations of the system’s license removal capabilities.

The “Active Products” window

The “Active Products” window displays data about licenses that are used at the current time.
Each line of the display represents a user who is momentarily using a specific license. It shows specific details about the software session such as start time and duration. Some of the information presented in this window originates in the OpenLM Agent module, so a proper installation of the OpenLM Agent (Active Agent or Utilizer Agent) on each client workstation is a prerequisite to obtaining this data.

With the “Active Products” window,  administrators can monitor individual workstations that run licensed applications. They can detect idle applications, and shut down such applications with a mouse click. In order to retrieve licenses and shut down applications, an OpenLM Active Agent module must be installed on each client workstation.

User Idle

If the user has not been actively using the license, the idle time period would be shown in the “User Idle” column. This information is sampled by OpenLM Agent modules (Active Agent or Utilizer Agent) on each client workstation, and sent to the OpenLM server. The sample period is set by the Agent policy’s “Agent report” period, as in the example below (set to 60 sec).


Removing licenses

Administrators have the option to manually remove a license from a specified workstation. This is done by highlighting the user row on the Active Products window and clicking the “Remove License” icon (See image below).
There are several constraints that are specific to this feature:

  • The end user must have been inactive for a minimum period of time in order for his license to be retrieved.
  • If the license is not really associated with any real product activity on the specified workstation (as happens when a license gets artificially “frozen” on a computer), then the license will be freed and will be returned to the pool of available licenses.
  • If the worker is actually using the product, then re-obtaining a license would be automatically attempted. If this happens the license for that product and workstation will re-appear on the active products screen, with a new handle number.
  • Retrieval of licenses may only be accomplished once a minimal period of time has elapsed since the license was checked out. This value is set by default to 5 minutes in compliance with FLEXlm license manager’s limitations.

Closing applications

In order to actively close an application on the workstation,  an administrator should highlight the relevant row, and click the Close Application icon (See image below).

This operation will retrieve the license back to the license pool, save the open project,  and the application itself will be shut down.
There are some constraints that are specific to this feature:

  • It requires a proper installation of the OpenLM Active Agent module.
  • It works only extension-based active agents. At the time of writing this revision (Rev 1.1), these include Matlab, ArcGIS and AutoCAD.


Common Constraints

There are several constraints that are common to both the License Removal and Application Closure features.These are as follows:

  • At the time of writing this revision (Rev 1.0), These features are only available when working with the FLEXlm license manager.
  • An OpenLM Agent module must be properly installed on each Client workstation. The Application closing feature requires the Active Agent. The License Removal feature may use either the Active Agent or the Utilizer Agent.
  • Borrowed licenses (AKA Linger licenses) may not be retrieved via the EasyAdmin application.

Revision 1.1: Orik, Apr 15 2012


Please follow and like us:

Application note 1017: Changing ports numbers in OpenLM

Introduction

The OpenLM Utilizer is a licensing management software. It provides productivity tools for system administrators, managers and end users. 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 software package includes modules and capabilities which provide additional functions. In order to interface these components and obtain full functionality of the OpenLM software, it is essential to open certain port numbers.

OpenLM license Server

The OpenLM Server is the core element of the OpenLM Utilizer system. It integrates the functionality of all other OpenLM peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

License manager: Default port 7016

The OpenLM Server interfaces the License manager over a dedicated port. this port’s default number is 7016.

Configuring the License manager Port:

In the “OpenLM Server” configuration window, select the “Port Settings” tab.
In the “License managers reporting port” text-box, type in the OpenLM server port number (e.g.: 7016).

The OpenLM Broker is an optional software component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server. The Broker is required in order to provide advanced licensing information and capabilities; such as controlling license servers remotely, managing FLEXLM option files etc.

The OpenLM module interfaces the OpenLM Server via a dedicated port. This pot number is 7016 by default, and should be configured the same as the license manager port (see above). For additional information on the OpenLM Broker component, please refer to this application note.

Configuring the OpenLM Broker Port:

There are two methods for configuring the OpenLM Broker port: via the OpenLM Broker configuration tool, and via the broker.xml configuration file.

OpenLM Broker configuration

  1. Open the “OpenLM Broker configuration”.

  2. Choose an OpenLM Server from the OpenLM servers list and click “Edit” .
    Edit the “Port” textbox. Repeat this for all OpenLM Servers.

broker.xml configuration file

  1. Open the broker.xml file,  located on: “C:\Program Files\OpenLM\OpenLM Broker”

  2. Search for the line <Port>7016</port>.

  3. Edit the port number.

OpenLM Agent:  Default port 7012

The OpenLM Agent facilitates available license querying, among other functions. It connects to the OpenLM Server through another dedicated port: the OpenLM Agent default port number is: 7012. The OpenLM Agent port number should be configured the same on the OpenLM Agent configuration tool, and on the OpenLM Server configuration tool.

OpenLM Agent configuration tool

  1. Right-click on the Openlm Agent blue icon on the Windows taskbar,

  2. Open the ”OpenLM Agent configuration” tool. The “Agent Configuration” window pops.

  3. Type in the port number in the “Port” textbox (e.g.:7012).

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Agent port in the “Agent reporting port” text-box (e.g.: 7012).

HTTP Server Port:  Default port 7014

This port enables EasyAdmin web application to send requests to the OpenLM Server.

This port number should be configured the same on the OpenLM Server configuration tool, and on the “config.js” file.

OpenLM Server configuration:

In the “OpenLM Server” configuration tool, select the “Port Settings” tab. Type in the HTTP Server port in the “User Interface http server port”  textbox (e.g.: 7014).

config.js file:

  1. Open the “config.js” file, typically located on:”C\Program Files\OpenLM\OpenLM Server\WeebApps\EasyAdmin2”
  2. Search for the number 7014.
  3. Edit the port number(Should be 7014).

OpenLM Alerts System:  Default port 7017

The OpenLM Alerts module produces alerts for system managers based on predefined conditions. These alerts may be directed to email messages, SMS text messages, the EasyAdmin web application or to a dedicated log file. Please refer to this application note for elaborated information on the OpenLM Alerts module.

Configuring the OpenLM Alerts port:

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Alerts port in the “Alerts server checking port” textbox (e.g.: 7017).
  1. In the OpenLM Alerts configuration form, of the OpenLM Alerts Editor, type in the port number in the “Alerts Port” textbox.

OpenLM HTTP port Default port 7019

OpenLM installs the LightTPD web server with the installation of OpenLM Server. LightTPD is configured as a Windows Service and starts up with the machine. The use of web servers such as Apache or IIS or others is also supported.

Configuring the OpenLM LightTPD port:

  1. Open the “lighttpd-inc.conf” file,  located on: “C:\Program Files\OpenLM\OpenLM Server\WebServer”.
  1. Search for the line “bind to port (default: 80) server.port = <port number>”.
  2. Edit the port number (e.g: 7019).

Serve OpenLM EasyAdmin using Microsoft IIS 6 & 7

The OpenLM Software package is delivered with LightTPD; a built-in web server. The LightTPD web service starts upon installation or machine start-up. Users can either use LightTPD or choose a standard web server such as Microsoft IIS.

For additional information on how to serve OpenLM EasyAdmin using IIS6, please refer to this application note. For information on how to serve OpenLM EasyAdmin using IIS7, please refer to this application note.For information on how to serve OpenLM EasyAdmin using Apache webserver, please refer to this application note.

Please follow and like us: