Tag Archives: DSLS

Application Note 2011: Quick Installation guide for the OpenLM license management system v1.8

Posted on by

The OpenLM Floating license monitoring and Usage optimization tool interfaces an ever growing variety of license managers, such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, LM-X and Easycopy.

Step 1: Installation

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.8 section:


And start by downloading the server:

When downloading is complete, double click the downloaded *.msi file and follow the standard installation instructions.

Step 2: Configuring License Servers

When the installation is complete, click:

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

The OpenLM Server configuration window opens.

1. Add in your license servers:

  • Click the ‘Add’ button,

  • Type in the License server’s host name or IP (e.g. lm10) and Port number (e.g. 27000)

  • Select the new License server’s type (e.g. FlexLM)

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

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

The image below demonstrates this configuration:

 

2. Select a license server and click the check button in order to ensure that OpenLM can retrieve information from that license server. This information is the input received from the License manager.

3. Repeat steps 1 & 2 for all license servers.

4. Click ‘Apply’, and “Restart now”.

Step 3: The OpenLM EasyAdmin Interface

The EasyAdmin web application is the main OpenLM Administrative and user interface.

You can find it on:

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

The OpenLM EasyAdmin opens. Click the 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.

For more information on the OpenLM EasyAdmin web interface, please refer to this document.

Congratulations!

You now have an up and running OpenLM system.

For further information regarding the installation and preliminary configuration of the OpenLM system components, please refer to the “Application Note 2010: OpenLM license management system Complete Installation guide v1.8” document.

Revision table

Revision

Author

Date

Remarks

0.1

Orik

Apr 23,  2013

Preliminary

What is new in OpenLM version 1.8

Posted on by

OpenLM 1.8 is out !

The release of this milestone version is a big deal for us here in OpenLM, and we are sure you will feel the same when you start working with it.

Note for OpenLM veterans:

At this stage we recommend not to upgrade OpenLM 1.7 production systems to 1.8, but rather to install it at a sandbox, side by side with the 1.7 production server. This is in order to ensure that full functionality has been maintained in your environment, and to familiarize yourself with the new version.

This document goes over the main features that have been added or enhanced in this version, and the list is quite long:

  • OpenLM Server engine
  • EasyAdmin: Personalization, New reports, Enhanced report windows,
    Moving configuration options to EasyAdmin
  • Support of License management tools
  • Active Directory
  • Named Users support
  • Packages
  • Projects
  • Permissions
  • License Usage
  • License Procurement table
  • License Usage Efficiency report window
  • Licenses not in use report window
  • Recent Feature Denials report window
  • License Servers
  • Session Idle time measurement
  • Database manipulation
  • ArcGIS Borrowed Licenses issue
  • OpenLM Broker
  • OpenLM Agent
  • ArcGIS Set Licensing level tool
  • Installation Process
  • Logs uploader

OpenLM Server engine

The OpenLM server integrates information from various sources in order to create accurate and coherent license usage information. All processing algorithms were reviewed and rewritten as needed in order to improve accuracy and processing speed.

EasyAdmin

The EasyAdmin web application has undergone facelift surgery, is more user friendly, and generally looks nicer. Some graphic presentation windows have been added, and others have been improved in both clarity and robustness.

Personalization:

EasyAdmin windows’ configuration and user settings are now maintained by the OpenLM database, not on the browser’s cache memory (as was in version 1.7). This provides the ability to personalize the EasyAdmin appearance, and get the same user’s view on different computers.

New reports

The new reports are hereby listed. Elaboration on each of these windows is provided below:

  • The License denial widget.
  • Procurement table: Shows licenses’ procurement path, providing detailed expiration information.
  • License usage efficiency report: Histogram per single feature, showing how much of the time have N licenses been used.

Enhanced report windows

Report windows have also been enhanced. It is now possible to:

  • Export chart images or PDF documents and
  • Set report window refresh period


Moving more configuration options to EasyAdmin

Several configuration options were moved from the OpenLM server configuration tool to the EasyAdmin web application, making them accessible from anywhere. One such option is the usage logging according to projects, as depicted below:

Support of License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 now supports the following concurrent license servers: FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy. In addition to that, support of some license management tools was enhanced. Here are some of these enhancements:

  • FlexLM: Asset Info information, which is unique per license pool is now monitored. Hence, it is now possible to follow user and group license check out per license pool.
  • FlexLM: Software packages are automatically recognized, and populated by the respective software products. Single features can be associated with different software packages.
  • IBM_LUM license manager monitoring has been added expiration date.
  • IBM_LUM Offline Licenses indications.
  • IBM_LUM HAL (High Availability Licensing) configuration support.
  • DSLS has been fully integrated into the OpenLM 1.8 system.
  • DSLS License borrowing is reported.
  • BetaLM has been introduced in the 1.8 version.
  • BetaLM Cluster configuration is supported.
  • RMS: License versions’ reporting was added.
  • Easycopy LM has been fully integrated into the OpenLM 1.8 system.
  • Matematica (MathLM) has been fully integrated into the OpenLM 1.8 system.

Active Directory

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP (Active Directory) to combine license management with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

In version 1.8, Active Directory synchronization has been profoundly improved, to support versatile and complex Active Directory environments. As a bonus, a preview of the impending synchronization scheme is now available. For more information please refer to these documents:

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

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

Version 1.8 now allows system managers to easily synchronize very complex structures of LDAP. In EasyAdmin the user can now control the execution of the synchronization, exclude groups and users from synchronizing and understand why each synchronized entity was generated.

EasyAdmin incorporates new administrative tools for LDAP synchronization. These provide a better view of the synchronization definitions and the relations between synchronized entities. Group and Users entities are interconnected by hyperlinks, to facilitate the browsing through LDAP synchronized data.

Named licenses support

FlexLM gets its licensing information from the license file, option file and other resources.

The License file contains the asset info information which is unique for every license pool.

The License file also contains asset info associated with groups. OpenLM Version 1.8 can be configured to read Flexnet publisher license files, and hence can report which user takes licenses from which pool.

License Suites and packages

OpenLM 1.8 is capable of integrating more information from FlexLM license files. One of the benefits of that is the capability of arranging licensed features within their respective license packages. The user does no longer need to configure packages’ members manually.

In addition to that, OpenLM 1.8 supports licensing schemes in which single features are associated with two different packages.

Projects

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some major 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).
  • Projects can also be introduced by end-users via the OpenLM Agent module. Please see the ‘Agent’ section below for more information on that.

For more information on monitoring licenses according to projects in OpenLM 1.8 please refer to this document:

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

Permissions

New users are automatically associated to the “Everyone” group. After being synchronized (or associated manually) to a different group – the new group becomes the default group.

License Usage

The central “License Usage” window’s graphic presentation was improved, and now employs a cleaner GUI, with a zoom-in option.

License Procurement table

Shows comprehensive license information, as appears in the license file: Licensed packages and their member features, issuing and expiration dates, Asset info etc.

License Efficiency report

A new window that provides a histogram of usage for a single feature, showing how much of the time have N licenses been used. The image below clearly demonstrates ineffective usage of the pool of licenses:

Licenses not in use report

Single out licenses that have not been used for a predefined period of time.

Recent Feature Denials report

A graphic presentation to show a comparative chart of the number of license denials over predefined periods of time: recent and long term.

License Servers

Reported license servers’ information has been enhanced to include:

  • License server timezone
  • Status of the OpenLM broker installed on the license server machine
  • Host availability indication


Session Idle time measurement

Graphical waveform presentation of the Active / Idle ratio for currently and historical sessions.

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database. It is now possible to

  • Archive or delete old data.
  • Extract irrelevant users and
  • Delete unnecessary groups.

ArcGIS Borrowed Licenses issue

We previously reported an issue pertaining to the upgrade of ArcGIS to the newer FlexLM version. This issue manifested in erroneous reporting of license borrowing. OpenLM 1.8 bypasses this issue and shows the actual borrowing user.

OpenLM Broker

The OpenLM Broker has undergone important changes. These include:

  • Enhanced robustness
  • Enhanced compatibility with a wide array of license managers
  • Ability to read FlexLM license files and Audit logs, in addition to Option files.
  • Implementation of buffers for Broker messages, providing the ability to overcome limited network connectivity failure and continues usage reported even if the OpenLM Server machine crashes for long period of times.

OpenLM Agent

The OpenLM Agent has changed skin and looks much nicer now.

It also integrated the improvements for the following features:

  • Restoring of closed sessions
  • Searching and sorting of the license usage list
  • Selectively hiding or showing specific features
  • ArcGIS licensing level determination (see below).
  • As mentioned above, projects can be introduced by end-users via the OpenLM Agent. Just click the “Create New Project” menu item in the OpenLM Agent interface:

The “Create new Project” window opens. Users can then create new projects and associate their working hours to these projects.

For more information please refer to this document:

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

ArcGIS Set Licensing level tool

ESRI implementation is unique in the sense that you can activate the ArcMap software in three different licensing levels:

  • Basic (Previously called viewer or ArcView)
  • Standard (Previously called ‘ArcEditor’)
  • Advanced (Previously called ‘ArcInfo’)

ArcGIS end users can set the licensing level before activating the software. If such a license is available, the software will start. OpenLM has provided this capability since version 1.6 of the software. In version 1.8 we have highly enhanced it:

  • It is now possible to set the licensing level according to available licenses, and
  • The user can choose whether to save the ArcGIS licensing level to the Registry, to do it on a user level, or on a system level (for all users – requires administrative permissions).

Installation Process

The OpenLM installation process has been standardized, and is more coherent on OpenLM version 1.8.

Logs uploader

The Logs uploader has been rewritten, and its robustness has been improved.

OpenLM beta version 1.8 is publicised

Posted on by

General

In the past couple of years, OpenLM v1.7 has been the selected tool for application usage metering and license usage optimization for an expanding circle of customers. OpenLM has steadily widened the variety of supported network license managers, and enhanced its monitoring capabilities per each license management tool.

OpenLM beta Version 1.8 incorporates many bug fixes, performance improvements and new features that were required by our cooperative and trusted customers. These changes have increased OpenLM’s robustness and made it less prone to errors.

This version also integrates some fundamental architectural changes that have expanded OpenLM’s ability to further develop license usage control and monitoring. Here are some of the main highlights of this new version.

Important note:

As of today the released version is still a beta, and as such it is not yet error free.
DO NOT upgrade production installations of OpenLM 1.7 to 1.8 beta.
The use of version 1.8 beta is recommended for:

  • New evaluating customers, who wish to explore the 1.8 beta version functionality, or
  • Active OpenLM 1.7 users, installing version 1.8 beta separately and parallel to the 1.7 production installation.

Please read this document prior to installing OpenLM 1.8 beta parallel to production 1.7 installations.

Support of License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 now supports the following concurrent license servers: FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta LM, Mathematica LM (MathLM), and Easycopy. In addition to that, support of some license management tools was enhanced. Here are some of these enhancements:

  • FlexLM: Asset Info information, which is unique per license pool is now monitored. Hence, it is now possible to follow user and group license check out per license pool.
  • Also on FlexLM: Software packages are automatically recognized, and populated by the respective software products. Single features can be associated with different software packages.
  • IBM_LUM license manager monitoring has been added expiration date, Offline Licenses indications, and support for HAL (High Availability Licensing) configuration support.
  • DSLS has been fully integrated into the OpenLM 1.8 system. License borrowing is reported.
  • RMS: License versions’ reporting was added

EasyAdmin

The EasyAdmin web application has undergone facelift surgery and generally looks nicer. Some graphic presentation windows have been added, and others have been improved in both clarity and robustness.

Personalization:

License usage status windows’ configuration can now be saved between workstations and browsers.

New reports

Some of the new reports are:

  • The License denial widget.
  • Procurement table: Shows licenses’ procurement path, providing expiration information.
  • License usage efficiency report: Histogram per single feature, showing how much of the time have N licenses been used.
  • Max usage heat map report.

Enhanced report windows

Report windows have also been enhanced. It is now possible to:

  • Export chart images or PDF documents and
  • Set report window refresh period
  • The “License Usage” graphic presentation was improved.

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database. It is now possible to

  • Archive or delete old data.
  • Extract irrelevant users and
  • Delete unnecessary groups.

License Servers

Reported license servers’ information has been enhanced to include:

  • License server timezone indication
  • Host availability indication
  • License not in use indication.

Active Directory

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP (Active Directory) to combine license management with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

In version 1.8, LDAP synchronization has been profoundly improved, to support versatile and complex Active Directory environments. As a bonus, a preview of the impending synchronization scheme is now available.

Projects

The Project license usage recording capability is available for OpenLM from version 1.6 onward.  In the 1.8 version, some major 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

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

OpenLM Broker

The OpenLM Broker has overgone important changes, enhancing its robustness and compatibility with a wide array of license managers. One of these changes is the implementation of buffers for Broker messages, providing the ability to overcome network connectivity failure.

Finally

we would like to thank our loyal customers for collaborating as beta sites for this new version. Your ever welcomed feedback has enabled us to publicize this product, and is constantly driving us toward improving our releases.

Application Note 1035: Configuring OpenLM v1.7 to interface the EasyCopy License Manager

Posted on by

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM (Flexnet), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This application note elaborates the steps required to configure OpenLM to interface the EasyCopy License Manager, and obtain reliable license reports and usage statistics. This capability is available for Easycopy versions 8.7.12 onward.

OpenLM Server configuration

In order to configure OpenLM to monitor an EasyCopy License Manager, The OpenLM Server must be configured as follows:

  • Click the ‘Add’ button.
  • Set the LM Type to ‘Other’
  • Set the License server’s Time zone (e.g.: Central Time)
  • Type in the Hostname (e.g. easycopy_lm) or IP of the EasyCopy License server.
  • The port number is insignificant here. Type in any number (e.g.: 123). Note that the same number will need to be used in the OpenLM Broker configuration as well (see below).
  • Click the ‘Apply’ and “Restart now” buttons.

OpenLM Broker Configuration

After setting the OpenLM server, the Broker needs to be configured as follows:

  • Please refer to the Application Note 1004: OpenLM Broker quick start guide document for general Broker configuration. In the example below – the OpenLM server hostname was set as openlm_server, the OpenLM Broker port was maintained at its default 7016.
  • The license server characteristics are set exactly as they were on the OpenLM Server configuration tool: The type is set to ‘Other’, the name to easycopy_lm, and the port to 123.
  • Type in the EasyCopy command line in the Broker’s “data_inquiry” command text box. The command is “eclic openlm” and it needs to be run from the location of the eclic.exe path.
  • Click the ‘Apply’ and “Restart Broker” buttons.

Siemens PLM license analysis and license monitoring

Posted on by

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.

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

Posted on by

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>

Here’s a good example for DSLS implementation of offline licensing.

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.

OpenLM: Concurrent license monitoring and optimization tool

Posted on by

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, Sentinel HASP, Reprise RLM, DSLS, IBM-LUM and LM-X. MathLM and BetaLM support has also been implemented, and would be released soon.

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, e.g.: FlexLM / Flexnet publisher, IBM LUM, Sentinel RMS, Sentinel HASP, RLM, DSLS and other leading license managers.
  • Concurrent monitoring of multiple license servers on multiple time zones.
  • Management of Floating, Node-locked and Borrowed licenses.

Monitoring capabilities:

  • Easily review license inventory in real time.
  • Extract license activity reports (e.g. Flexnet report), with configurable resolution.
  • Receive Billing reports for any time period, per user or software (FLEXbill capabilities).

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@openlm.com, and we’ll be glad to help.

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

Posted on by

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 (0×80131904): 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”).

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

Posted on by

 

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”.

 

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

Posted on by

 

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.