OpenLM Maintenance Release: OpenLM Server version 2.0.0.39

General

OpenLM Server version 2.0.0.39 is a maintenance release to OpenLM version 2.0. It contains enhancements and bug fixes to problems found in previous versions. Users for whom these fixes are relevant should upgrade  to this latest version.

Note that this version does not update the OpenLM database, only the OpenLM Server software. If your current OpenLM Server version is 2.0.0.28 or later no database upgrade will be necesary.

What’s new in OpenLM Server 2.0.0.39 (December 12th, 2014)

Fixed Issues:

  • 2534: DSLS reporting error when DSLS Server is in French
  • 2595: Host Availability chart scroll bar
  • 2585: Minimum idle time for license retrieval is set to 3 minutes.
  • 2598: Borrowed “linger due” on “Currently Consumed License” window shows odd time.
  • Improved license suspend-resume functionality when the software consumes more than one feature.

Note:

  1. Before upgrading, please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.
  7. Run the installation file. An OpenLM Server Service restart may be required after installation.

Upgrading the OpenLM Server (External MS-SQL, Oracle, MySQL Database)

If your current version is 2.0.0.27 or earlier please contact OpenLM support at:

support@openlm.com

For later versions: just run the upgrade process as elaborated in the “Upgrading the OpenLM Server (Internal Firebird Database)” above.

Opportunity to review and get a gift

The ITAM Review review site is offering users of SAM tools to review the software they are using: http://itassetmanagement.us1.list-manage.com/track/click?u=fcb47a3a527637f1a80dfbb39&id=8bb3691f79&e=a74f84ec19

They offer $40 (£25) Amazon voucher to the first 40 completed reviews.

Please review OpenLM.

What is new in OpenLM 3.0

OpenLM is proud to present version 3.0 of the OpenLM license monitoring and management tool. We appreciate the assistance, cooperation, patience and initiative of our trusted customers, without whom much of these new features and enhancements would not have been realized. We look forward to continuing this collaboration with you toward further enhancements of the OpenLM software.

OpenLM Server

Query according to license typeS

OpenLM can now filter reported information according to the license type. Supported license types are:

  • Floating
  • User Based (Network named user license)
  • Host Based (Network named host license)
  • Node locked (license server based)
  • Single use (Local license, implemented by a software or hardware key)
  • User Based Casual (DSLS)

Query according to license asset info

OpenLM now provides the capability to query and report FlexLM licenses according to their asset_info. In the ‘Licenses’ window, the Asset info reference number is presented in the “Additional Key” column. In the “License procurement” window, this information is presented in the “Asset info” column.

3

Advanced Support for Network Named licenses

OpenLM fully supports monitoring of combined Floating, Network Named Licenses (NNU) and Host based licenses. Monitoring license usage for such combinations is exceptionally difficult, since standard FLEXlm reports do not include information regarding the consumed license type. OpenLM has developed a unique method to bypass this obstacle and provide usage information per license pool.

Fully automated DB update process

A fully automated OpenLM Database upgrade mechanism has been added. Until now this functionality was only available for the Firebird embedded database. This capability greatly simplifies and streamlines the upgrade process of the OpenLM Server on external databases (MS-SQL, Oracle and MySQL).

Keywords support added to Options file editing form

The OpenLM Options file editing form has been enhanced to supports additional keywords. When used within an options file entry, the feature name can be modified with an optional keyword-value pair to fully qualify it. This notation is used for distinguishing a particular group of licenses when there are multiple FEATURE lines for a single feature. The following syntax is used:

feature:keyword=value

For example:

f1:VERSION=2.0

specifies the version 2.0 pool of licenses for feature f1.

  • The following option keywords are used as feature name modifiers to denote a specific group of licenses: VERSION, HOSTID, EXPDATE, KEY, SIGN, ISSUER, NOTICE,  VENDOR_STRING (if configured by the publisher as a pooling component), dist_info, user_info and asset_info.
  • This enhancement also enables advanced operations such as allocating specific NNU licenses:

GROUP NNU_MATLAB_USERS User1 User2 User3 User4 User5

INCLUDE MATLAB:asset_info=123 GROUP NNU_MATLAB_USERS

EasyAdmin

Improved interface

The look and feel of the OpenLM EasyAdmin web interface has been improved. It is now clearer and faster.

New start menu

The start menu has been simplified and divided to different logical units

11

Set filter location:

You can now change the location of EasyAdmin windows’ filters. Right click on the ‘Utilities’ icon, and select the prefered location from the drop-down list.

4

 

Administration form

Sort and Filter functionality has been added in the Administration form in order to enable quicker function search;

  • Sort: Arrange icon names according to ascending or descending order.
  • Filter: Type in a string to search for specific functions

6

 

EasyAdmin Dashboard

Based on feedback we have received from our trusted users, we have added a dashboard with a set of useful indicators. The desktop is accessible from the EasyAdmin ‘Start’ menu:

7

The featured indicators in the dashboard are:

  • Top 10 Denied Features: Licensed features that have been frequently denied.
  • Top 10 Users: Users with the most recorded usage time.
  • Top 10 Current idle sessions: The longest currently open sessions that have been indicated as idle.
  • Top 10 Current Longest Sessions: The longest currently active sessions
  • Top 10 Used Features: Most popular licenses to check out.
  • Top 10 Denied Users: Users who have been denied usage most frequently.
  • License server status: Overview of the monitored license servers. This information can also be obtained by the EasyAdmin start → Widgets → License Servers window.

12

 

Each indicator can be individually refreshed or minimized, and is individually customizable; Its time range and number of items can be set separately:

8

Report Sharing

We have added the ability to share a view (report) with a single click;

  • Click the “Share” button on any report and get a link.
  • Send this link to any other EasyAdmin user to share the same presented information.

13

 

The new functionality supports almost any filter in the system and allows different implementations such as periodic email report or a webpage with constant reports.

Improved interface for the license usage report window

1. Color selection and legend

  • Clear chart display: The legend and the color selector were united and are now located on top of the chart area, leaving a lot more space to the chart itself.
  • Immediate color change: Color selection was moved from the selection filter to the top of the chart area. This facilitates chart color changes without resubmitting the data query to the server.

14

2. Chart line highlighting

Temporary or Permanent, highlighting is done in two ways:

  • Temporary: Hover the mouse over a monitored feature for instantaneous highlighting.
  • Permanent: Clicking the ‘Highlight’ checkbox for permanent highlight of the display.

15

 

3. Include current usage

By default, the License Usage window reports historical usage. Only sessions that had already ended will be transferred to this display. In version 3.0 we have added the possibility to include current license usage in the License Usage display. This option is accessible as part of the Filter selection.

9

 

4. Incorporated heatmap in the license usage report

The Heatmap report is now integrated in the License Usage report as an additional tab. This enables users to easily switch between the two displays without the need to configure a filter for the second view.

16

The Heatmap chart was also enhanced to include

  • Hours and Days resolutions – for finer examination of usage in the heatmap.
  • Multiple months’ view on the same screen: to obtain a comparative insight on license usage.

17

Full OpenLM Server Logging

On previous OpenLM versions, setting the OpenLM Server’s logging level to ALL for debugging purposes required logging into the OpenLM Server machine and restarting the OpenLM Server service. This action has now been integrated into the EasyAdmin ‘Administration’ form. Moreover, logging can now be set for a limited period in order to avoid excessive use of the machine’s resources. When the predefined period has elapsed, logging will resume the ‘ERROR’ level.

18

Time zone selection on the EasyAdmin interface

Changing the timezone on the EasyAdmin interface will now change the whole EasyAdmin time display to the selected time zone. In previous versions this was set automatically according to the user timezone as set on his machine.

Changing the time zone is beneficial for system administrators whose licensing systems span over multiple time zones. License managers can now set the EasyAdmin time zone to match that of the license consumption site and view usage reports accordingly.

10 latest ‘Start’ menu selections

The 10 latest EasyAdmin ‘Start’ selected options are now saved per user. This capability facilitates quicker access to popular EasyAdmin selections. Access this via the ‘Start’ → Recent option.

19

Close all but this

In order to avoid clutter, EasyAdmin 3.0 now incorporates the capability to close all report windows, apart from the window of interest. In order to do so, right click the required window’s icon on the bottom taskbar, and select “Close All But This”

10

Reset Layout for specific windows

Users may change EasyAdmin report windows’ layouts during work. This layout would include parameters such as: shown and hidden fields, fields’ order, windows’ sizes and locations, etc.

In order to resume the default layout for individual windows, an additional field has been added in the windows’ properties selection: This is the “Reset Layout” selection.

20

Editing multi selection fields

EasyAdmin enables users to assign multiple values filter parameters. In version 3.0 the capability to edit the content of these parameters was added. It is now possible to add or remove single values, as well as to clear the entire content.

  • In order to clear the entire parameter’s contents, click  the marker icon:

21a

  • In order to remove a single parameter value, click the ‘X’ icon:

21b

Agent

Automatic configuration update – no need to restart Agent

In previous versions of OpenLM, the OpenLM Agent would be configured by the OpenLM Server upon startup. This mechanism required the Agent to be restarted whenever its configuration was updated, e.g. when adding processes to track using the unmanaged license monitoring functionality. In version 3.0, the OpenLM Agent quickly updates itself following changes in the OpenLM Server configuration.

OpenLM APIs

In OpenLM 3.0 a change has been introduced in OpenLM APIs, following a fundamental change in OpenLM’s relation to message dates. Developers should consult OpenLM support regarding the required changes.

That’s all folks

This sums up the list of additional features that were integrated in version 3.0. Please feel free to address any feedback or question to support@openlm.com , and we will be glad to assist.

OpenLM Version 3.0 Pre Release download

 

OpenLM Maintenance Release Version 2.0.0.38

OpenLM Server version 2.0.0.38

OpenLM Server version 2.0.0.38 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.28 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.38 (October Dec. 9th, 2014)

Fixed Issues:

  • 2601: LogCompletion – Handle number of licenses when creating new sessions from debug log
  • 2570: Correct LMX usage accumulated
  • 2341: Missing License Availability notification OpenLM Agent
  • 2442: Host Availability: chart is not shown
  • 2588: Add SetDefaultProject request to AgentsListener
  • 2441: Roles Based Security: users assigned to a role by group do not lose roles permissions if removed from the group
  • 2328: DSLS not parsed properly.
  • 2538: EasyAdmin – Reports – Denials – Chart: Screen turns blue  when running query

Note:

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.38:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.27 or lower in order to upgrade to version 2.0.0.38, please contact OpenLM support at support@openlm.com

 

 

OpenLM All License Parser Release Version 1.7

What is new in the OpenLM All License Parser Version 1.7?

The system now only offers HTTPS connection in order to better protect data privacy.

Added support to the DSLS license file and license server log (Dassault Systèmes).

Grouping error messages to create a clearer and shorter report.

The service is available at: www.alllicenseparser.com

 

What are Flexnet Network Named Licenses ?

General

“Network Named Licensing” is a  FlexLM licensing format that dedicates a certain amount of licenses to predefined people in the organization. This type of licensing is typically cheaper than simply applying ‘INCLUDE’ restrictions on floating licenses in the FlexLM Options file.

How it this done ?

In this method, a number of licenses for a specific Feature are marked in the license file’s INCREMENT or FEATURE line as “USER_BASED”. This is done per license pool (marked as ‘asset_info’ indices). See a customer’s Matlab example below:

 

INCREMENT MATLAB MLM 31 01-jan-0000 XX XXXXXXXXXX\

VENDOR_STRING=vi=0:at=276:ae=1:lu=300:lo=NNU:ei=XXXXXX:lr=1: \

HOSTID=ID=123 USER_BASED=5 DUP_GROUP=UH sort=90 asset_info=123 \

ISSUED=XXXX BORROW=720 NOTICE=product=MATLAB SN=123 \

SIGN=”XXXX XXXX … XXXX”

 

In the Options file, a group containing exactly 5 users is defined:

GROUP NNU_MATLAB_USERS User1 User2 User3 User4 User5

 

Further down the Options file, an INCLUDE line is added, to reserve the licenses for users User1,…,User5:

INCLUDE MATLAB:asset_info=123 GROUP NNU_MATLAB_USERS

Restrictions

Using the Network Named Licenses (“USER_BASED”) imposes restrictions on editing the Options files; Customers are restricted by agreement not to make changes to the Options file within a period of agreed length. The rationale behind this restriction is that applying frequent changes to the Options file will effectively turn the Network Named License into a Floating license, which is more expensive.

 

Trouble Shoot Form: FlexLM item 003 (Denials do not appear in the Flexnet debug log)

Denials do not appear in the Flexnet debug log

  1. 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:

Application Note (3007): OpenLM v2.0: Options File Using OpenLM EasyAdmin

  1. Another case of similar symptoms (no denial reports in the debug log) was reported by one of our customers. They were monitoring Matlab, and FlexLM seized denial reports following the .NET update KB2978128. After uninstalling this update Matlab resumed denials reports.

 

What is Reprise RLM

Reprise is a software company which bases its activity on software license management. It is a descendant of Globetrotter, the same company that also begat Flexera – producers of Flexnet publisher.

Reprise’s flag product is the RLM license manager. The RLM license manager controls the allocation of licenses by allowing a product to check out and check in a named license. The license manager keeps track of which users and computers can use these licenses, and, if the license is a floating license, the license manager keeps track of how many copies of the license are in use.

RLM resembles FlexLM in certain aspects, such as the structure of license server commands, and content of license files, options files and log files. According to Reprise publications, RLM was made more efficient than its sibling FlexLM, by “avoiding unnecessary options in the client library and the license servers and moving these options to the license file, where they are visible and understandable by everyone”.

 

What is DSLS

DSLS (Dassault Systemes License Server) is – as the name implies – Dassault Systemes’ proprietary license management tool.

This tool is in charge of enrolling Dassault licenses on the server; Dassault applications that are installed on end-user workstations communicate with the license server over the network. The license server either grants or denies a license from the client, based on license availability and license agreement compliance.

Dassault Systemes was established in the late 1970s as an aviation engineering company. It developed the CATIA CAD software tool in collaboration with IBM, and centered itself in the 3D mechanical design market.

In recent years Dassault has expanded to include other prominent CAD and engineering software, such as PLM, Solidworks, 3DVIA and Simulia. Consequently, DSLS has become increasingly substantial in managing CAD and engineering software, often shunning out other license management tools such as IBM-LUM.

 

Installing the ESRI ArcGIS Administrator as a second License Manager

General

A single machine may very well host several FlexLM License management vendor daemons. The following process elaborates how to install the ArcGIS license manager on a machine that already hosts the Autodesk LM. In the process we will show how to authorise the ArcGIS license, set the FlexLM license manager to interface the ArcGIS license manager and configure ArcGIS license management ports.

Ports

During this process, we set the vendor daemon port and license manager port in order to obtain better control over these services, and set inbound rules in the Windows’ firewall administrator.

Process

1. ArcGIS License Manager setup: Download the Latest ArcGIS License Manager setup executable file to your intended license server. In this case: ArcGIS_License_Manager_Windows_1022_XXXXX.exe. Run the file, and follow the installation procedure.

1and22. Authorization: Open the ArcGIS License Server Administrator tool, in the ‘Authorization’ node. Select the version number in the ‘version’ drop down menu, and click the “Authorize now” button.

3

The software authorization wizard opens. In this case we already had an authorization code for a single desktop license with no extensions. We chose to authorize ArcGIS using the internet, and specified this information on the following screens:

4and5

6and73. LMTOOLs configuration:

As stated above, we started out with a license server that already hosted the Autodesk LM. See the LMTOOLs windows below:

9

Select the “Config Services” tab, and type ‘ARCGIS’ in the Service name text drop box. Click the ‘Browse’ button: the path text boxes are cleared. The ArcGIS License manager was installed at its default path: C:\Program Files (x86)\ArcGIS\License10.2, so that’s where we directed the three required paths:

  • lmgrd.exe: C:\Program Files (x86)\ArcGIS\License10.2\lmgrd.exe
  • License file: C:\Program Files (x86)\ArcGIS\License10.2\service.txt
  • debug log file: C:\Program Files (x86)\ArcGIS\License10.2\lmgrd9.log

We also selected the server to run as a service, and start on power up.

12b

4. License file: In the license file we dictated specific ports for the license server and vendor daemon. These were 27001 and 12345 respectively:

SERVER this_host ANY 27001

VENDOR ARCGIS PORT=12345

INCREMENT ACT ARCGIS 1 permanent 1 XXXXXXXXXXXXXXXXXX \

       vendor_info=XXXXXXXXXXXXXXXXXXX

The ARCGIS service is now configured, and apparent on the LMTOOLs utility:

13and14

5. Firewall: The two license management ports (27001 and 12345) need to have a firewall inbound rule assigned to them, to permit communication over the network. See the image below.

15

This concludes the actions that need to be implemented on the FlexLM license server.

6. Set server and port: Open the ArcGIS License Server Administrator tool on the client machine, in the ‘Desktop’ node. Click the ‘Chage’ button, and type in the server name and port number of the newly configured license server, like this: port_number@server_name.

16

If several license servers are configured, a semi-colon ‘;’ will be needed to separate between them, i.e:  port_number_1@server_name_1; port_number_2@server_name_2

That’s it – we’re done with the license manager configuration, and can check out ArcGIS licenses on that server

7. OpenLM: Now we can utilize OpenLM to monitor the checked-out ArcGIS licenses over the EasyAdmin web application. For more information on this – refer to this document.