What is new in OpenLM version 1.8

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.

Please follow and like us:

Application Note 1029: LDAP (Active Directory) Synchronization

General

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP to combine license management, license statistics, and report extraction with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

LDAP Synchronization holds many advantages, for different levels of decision makers in the organization. On an administrative and managerial standpoint, it can be applied for enforcing license usage permissions, implementing usage chargeback (usage billing), analysis of usage trends etc. Administrators may gain in automating FlexLM Option file management, thus streamlining FlexLM reporting. From the end-user point of view, this information may be applied to easily locate other users holding a required license.

The Groups synchronization functionality is part of the Users and Groups extension, and requires additional licensing.

Additional information

Please refer to the video tutorial section on the OpenLM site, for a demonstration of Active Directory synchronization.

Users and groups presentation

The Users and User groups which exist in the OpenLM Database are apparent in the EasyAdmin web application, in the Users and Groups windows respectively. Initially, upon installation of the OpenLM server, the Users and Groups windows are only populated by the logged user (e.g. ‘Orik’ – that’s me), the default ‘generaluser’ user, and the “OpenLM Users” default group.

The Active directory tab – Interfacing the LDAP

This tab is the OpenLM Server’s interface to LDAP (Active directory) synchronization. The 1st thing to do is to connect to the LDAP Database. Type in the LDAP server details:

  • Domain name: the IP Address of the server which is your organization’s domain controller (e.g: 102.101.100.106)

  • Username (e.g: administrator)

  • Password, and

  • LDAP server type: (e.g. “Active Directory”)

Click the ‘Check’ button, and receive an authentication status notification, as depicted below:

 

Organizations may have multiple domain controllers (for example, if different departments or subsidiary companies have their own servers for user authentication). In order to add a second server, select the row where the asterisk is shown above, and type in the data for the second server. In order to apply another synchronization rule to the same LDAP server, click the “Duplicate” button under the list of domain controllers.

Synchronizing Users

It is important to note that synchronizing to the LDAP is a tricky business. You may end up having taken in more users than you intended, and deleting users from the database is difficult. It is highly recommended to experiment on a separate database, NOT on the production database.

In order to synchronize user information:

  • Check the “Synchronize users” check-box. Other fields on the “Active directory” tab are activated.

  • Click the ‘Select’ button. The active directory browser opens.

  • Select a synchronization start node.In this example, We’ve selected an Organizational Unit (OU): OU_Test. Click ‘OK’ and the node path appears in the “Synchronization Start Node” text box. The LDAP would be synchronized from this node down.

 

  • Set the “Sync time interval” value. The value in this example states that the user details would be updated every 12 hours.
  • It is highly recommended to Check the “Sync only active users of licenses” in order to avoid adding users that do not actively use the application. New active users would be added to the list of users as they check out a license, and their LDAP details would be synchronized when the “Sync time interval” elapses.
  • Set the “Sync username attribute”.

    • “sAMAccountName” is good for Pre Windows server 2000 Active directory versions.

    • “userPrincipalName” is good for Post Windows server 2000 Active directory versions.

    • “cn”  should be used for any LDAP configuration other than “Active Directory”, i.e. “Novelle Directory” or “Apache DS” .

      The value of the selected field (sAMAccountName or userPrincipalName or cn) within the Active Directory would be applied as the user name recognized by OpenLM.

Synchronization of Groups

Check the “Synchronize groups” checkbox to enable a variety of options for associating users with groups in the OpenLM database, according to the data structure on the LDAP.

AD Groups:

This option goes through the list of users that populate the nodes beneath the selected node. The “AD Groups” selection should be used carefully, because it may introduce a large amount of undesired groups. This is because users who are members of groups within the selected node may also be members of groups from beyond that node, resulting in additional introduction of these external groups.

Attribute:

OpenLM groups may be created according to specific attributes their members may have. In order to do that, select the “Attribute” radio button, and pick up a suitable attribute from the adjacent drop-down list of attributes. Examples for attributes are: “Division”, “Employee ID”, “Initials” or “Cost center”. Type in a Regex expression that would articulate the required attribute.

Fixed:

This option enables the administrator to associate a particular group name to all users of a specific node within the AD tree. The ‘Fixed’ name typed in the textbox is the group name of the users that would consequently be synchronized in this method.

OUs (organizational units):

This option is in use by organizations that have an organizational hierarchy represented in the LDAP; for example departments nested inside divisions. By selecting the OU synchronization method:

  • Users would be introduced into groups in the OpenLM database. These groups would be named after the LDAP OUs under which the users have been created.

  • If the “Add full hierarchy” checkbox is ticked, the entire OU hierarchy tree descending from the start node would be introduced as groups in the OpenLM database. OUs in which no users have been defined in the LDAP, would be presented in OpenLM as empty groups.

  • If the “Add full hierarchy” checkbox is not ticked, OpenLM would flatly create groups named after the LDAP OUs, and populate these groups by the users which have been defined under these OUs. No empty groups would be created.

Case study

In order to demonstrate the different group synchronization methods, I have created the following OU structure, and enabled all users. Note that Users U_A1 & U_AB2 are members of more than one group:

Case 1: Synchronize users only

Procedure: OU_AB was selected as the start node.

Outcome: All Users were synchronized. No Groups or OUs synchronized.

Case 2: Synchronize AD Groups (1)

Procedure: OU_AB was selected as the start node.

Outcome: All groups and users beneath OU_AB were synchronized. The Hierarchical tree was not preserved.

Case 3: Synchronize AD Groups (2)

Procedure: OU_B was selected as the start node.

Outcome:

  • Users B1 & AB2 have been synchronized.
  • Group B1 was synchronized.
  • Group A1 was synchronized, with only user AB2.

Case 4: Synchronize AD Groups (3)

Procedure: OU_A was selected as the start node.

Outcome: Mirror image of the previous case:

  • Users A1, A2, A3 & AB2 were synchronized.
  • Groups  A1, A2, A3 & B1 were synchronized. Group B1 only contains user AB2.

Case 5: Fixed

Procedure: Start node = OU_A. The “Fixed” name was named “The_A_Team”.

Outcome: All of OU_A’s users were gathered in “The_A_Team” group.

Case 6: Attribute

Reminder: Users A1 & B1 are the only users to have been defined owning “division” attributes with the value “my_division” (See LDAP diagram).

Procedure: OU_AB was selected as the start node. The “Attribute” synchronization method was chosen. The ‘division’ attribute with the value “my_division” was configured in the Active directory configuration form.

Outcome: All Users in OU_AB were synchronized. Users A1 & B1 were gathered in the “my_division” group.

Case 7: OU

Procedure: OU_AB was selected as the start node. “Add Full Hierarchy” was not checked.

Reminder: Users  AB1 & B1 were created under the OU_AB Operational Unit. All other users, i.e. A1, A2, A3, AB2 were created under OU_A.

Outcome: All users under OU_AB were synchronized. OpenLM has flatly created groups named OU_AB, and OU_A. Each of these two groups contain the users which have been created under the respective LDAP’s OUs:

  • Group “OU_AB” contains the users AB1 & B1 (see image below).
  • Group “OU_A” contains all other users, i.e. A1, A2, A3, AB2.

Case 8: OU (2)

Procedure: OU_AB was selected as the start node. “Add Full Hierarchy” was checked.

Outcome: This time the OU hierarchy was preserved, so OU_A and OU_B appear under OU_AB. The users are again grouped according to the position in which they were created:

  • Group “OU_AB” contains the users AB1 & B1.
  • Group “OU_A” contains all other users, i.e. A1, A2, A3, AB2 (see image below).
  • Group “OU_B” is empty.

Please follow and like us:

OpenLM Newsletter 2012 #01


Dear valued OpenLM users,

On this first edition of the OpenLM 2012 Newsletter I would like to greet you all, and wish you a happy and successful new year. 2011 has been very good for us here at OpenLM, all thanks to your support. Our team has grown bigger, and is now able to provide better support to our improved product.

We are proud to introduce the OpenLM Mobile touch interface. This interface may run on any mobile device operating system; e.g.: IOs, Android, Blackberry, Windows Mobile etc. With the help of some of our faithful customers, we have managed to perform a successful Beta trial for this interface. The OpenLM Mobile Touch interface is available to all customers under a valid maintenance agreement with no additional cost.

Based upon requests from our customers, and following Dassault Systemes migration from IBM-LUM to their proprietary DSLS license manager, OpenLM has quickly adapted to provide support to DSLS. We look forward to receiving further customer requests, in order to meet our users’ needs.

We have recently launched a new and enhanced company website. This site is clearer, more informative, useful and generally – nicer than our old one. Among other things, It features a new introductory animated video on OpenLM. We hope that you will like it.

Best Regards,

Oren Gabay, CEO


OpenLM updates

OpenLM goes mobile !

 

The OpenLM EasyAdmin Mobile application enables system administrators to keep track of the license management systems, while being out of office. This document describes the essentials of the OpenLM EasyAdmin for mobile application; installing the application, and running it on a Mobile set.Read more…

 

OpenLM Live Webinars

OpenLM is now hosting a couple of Online Webex Webinars each week. This Webinars give an overview of the OpenLM system; its components and capabilities, and is intended for newbies as well as for experienced users. Please check out the date for the next webex Webinar on OpenLM’s site.


OpenLM resources

OpenLM introductory video

 

 

 

 

 

OpenLM Video tutorials: OpenLM server configuration – License server tab

 

 

 

 

 

 

OpenLM Video tutorials: Active Directory Synchronization

 

 

 

 

 

 


Monthly Articles

Get more out of your floating licenses

Being this our first edition of the OpenLM Newsletter for 2012, We found it adequate to give a brief summary of what the OpenLM utilizer actually is. This is good reading material for Newbees, and nice to remember for more experienced users. Read more…

OpenLM system structure

Another important article for first timers, this one elaborates all about the OpenLM system structure; Where should every module be installed, and what are the interconnections between them. Read more…

Products and Packaged licenses in OpenLMs EasyAdmin web application

This Article deals with two adjacent subjects: Renaming features as products, and gathering these features into licensed packages in the OpenLM EasyAdmin web application. Read more…

Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

FLEXlm (Flexera FLEXnet) option files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, according to the option files setting.

The OpenLM solution incorporates synchronization of License administration tools with the organizations LDAP (Active Directory), keeping the FLEXlm option file up-to-date as users leave or join the organization, or move between groups. Read more…


 

Points of interest

IBM Rational – FlexNet Token based licensing:

The IBM Rational License Server uses FLEXnet for licensing IBM Rational products. This article presents the main characteristics of FlexNet Token based licensing, and the benefits of this method. Read more…

Autodesk cascade licensing and the PLIST

Cascade Licensing allows a product to obtain a license from a network license manager pool when that license manager is servicing more than one product. Cascading was implemented primarily to address mixed-product environments where both suite and base products co-exist.

Read more…

FlexNet Producer Suite Is Distinguished by the Frost & Sullivan 2011 Market Share Leadership Award for Software-Enforced License Management

The Frost & Sullivan Award for Market Share Leadership is presented to the company that has demonstrated excellence in capturing the highest market share within a segment of its industry. Read more…

Please follow and like us:

Application Note 1000: OpenLM system structure overview

Application Note 1000: OpenLM system structure overview

Table of contents

OpenLM
OpenLM’s customer testimonials
The OpenLM solution
Components of the OpenLM system
Block Diagram
OpenLM Software Modules
OpenLM Server
OpenLM EasyAdmin
OpenLM Broker
OpenLM Alert
OpenLM Utilizer Agent
OpenLM Active Agent
OpenLM External Data Base (DB) Support
OpenLM Groups & Projects
OpenLM Role Based Security
OpenLM Option File Management
OpenLM Logs Uploader

OpenLM

OpenLM is a licensing management software company with an international install base. Companies that use OpenLM’s software range from global corporations and nation-wide companies to small offices. Our company’s commitment to innovation guarantees that our clients constantly receive updates with the most advanced technology.

OpenLM’s customer testimonials

Please review a partial list of OpenLM’s satisfied customers,

http://www.openlm.com/index.php/about-us-topmenu-3/customers

and their testimonials:

http://www.openlm.com/index.php/support/testimonials-topmenu-29

The OpenLM solution

OpenLM’s Software provides a comprehensive management solution for license management software such as FLEXlm, FLEXnet, Sentinel RMS, Sentinel HASP, RLM, IBM LUM and LM-X. The software provides productivity tools for system administrators, managers and end users. OpenLM’s software supports the major trends in the field of license management, e.g.: license consolidation, Usage charge back (usage billing), usage trend analysis etc. The software provides a comprehensive solution that combines the best of breed software, superior support, implementation and consulting services, in order to ensure your success.

OpenLM is proudly ISO9001:2008 certified by the ANAB (the U.S. accreditation body for management systems), and an ESRI business partner.

OpenLM’s solution is tailored according to specific customer needs, optimizing the licensing system and increasing software productivity.

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 these core components, the OpenLM Broker and the OpenLM Utilizer Agent modules are incorporated in the basic software package, but their installation is not mandatory; The Open LM system can function without the use of these two components.

The OpenLM software package also includes several optional modules / capabilities, which are commonly referred to as “OpenLM extensions”. These extensions provide additional functions such as:

  • OpenLM Active Agent (Active release of licenses)
  • External DB support
  • Groups and projects management
  • Role based security
  • Option file management
  • OpenLM Alerts
  • OpenLM Logs Uploader

The OpenLM Extensions are separately licensed:

  • Some of them are included within the OpenLM Server but require additional licensing
  • Others require the installation of an additional software module.

Block Diagram

Figure1 (below) shows a generalized block diagram of OpenLM’s license management solution:

OpenLM Software Modules

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

The OpenLM Server is implemented as a Windows service and could be installed on any network machine. It enables monitoring and managing of multiple license servers, over LAN or WAN networks. Common OpenLM Server configurations may vary from one or more license managers nationwide to multiple license servers located worldwide, over different time zones.

OpenLM EasyAdmin

OpenLM EasyAdmin is the administrative interface of the OpenLM system. EasyAdmin’s control panel features a desktop interface that enables users to configure the OpenLM Server; OpenLM’s core component. Some of EasyAdmin’s main properties are listed below:

  • EasyAdmin Easily extracts statistical license usage information from all attached license servers.
  • EasyAdmin’s role-based security enables system administrators to grant varying degrees of access to different groups of users.
  • EasyAdmin can run on any standard web browser (e.g.: Mozilla FireFox, Microsoft Internet Explorer, Google Chrome) and be accessed from any machine in the organization.
  • EasyAdmin features a touch interface that is compatible with mobile operating systems like Android, IOS, Blackberry and Windows Mobile. The OpenLM EasyAdmin Mobile application is particularly useful for after-hours crisis management situations.
  • EasyAdmin’s streamlined user interface design promotes simple and effective use of its unique capabilities.

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.

The Broker’s main task is to extract License Manager Servers’ debug log information and to push it to the OpenLM server. This action facilitates reading of license servers’ log files. Other capabilities provided by the broker are:

  • Controlling license servers remotely (e.g. start / stop the servers)
  • Managing FLEXLM option files.
  • Generating denial reports and
  • Support of complex configurations, e.g. license servers that work over WAN networks.

The Broker is an independent java based software module that can run on any license server operating system: UNIX, Linux or Windows.

OpenLM Alert

The OpenLM Alert is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met. Alert service users can set complex alert conditions on multiple license servers. For example, if the combined usage of a certain feature on servers A and B is above a certain threshold, an email message will be sent, alerting those concerned to the situation. The Alert service also supports adjustable timing for alert checking and message sending. Alert destinations are also configurable; Alerts could be sent to the EasyAdmin interface, over emails, as SMS text messages, or directed to a system event log.

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system. It provides OpenLM users with 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 application either manually, or by defining a timeout policy. In this manner, system administrators can save, close, or suspend 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.

OpenLM External Data Base (DB) Support

This extension facilitates saving license usage information on an external Data Base 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 collecting license usage information from Groups of users or projects. This capability is predominantly used by companies that charge back usage time to cost centers. The Groups & Projects extension synchronizes users’ data with its LDAP Data Base (Active Directory), keeping the data collection process fully automatic.

OpenLM Role Based Security

The OpenLM Server supports a role-based security feature that enables the implementation of customized access to OpenLM tools by setting access roles. This feature facilitates the implementation of OpenLM tools for diverse groups; e.g.: help desk, system administrators, managers and developers. The role based security system secures nearly all parts of the system entities, such as listed servers, fields and action buttons.

OpenLM Option File Management

The OpenLM Option File Management extension employs LDAP (Active Directory), to enable system administrators to manage Option Files easily from the EasyAdmin web based interface. This gives the system administrators easy control over the access of user groups and individuals to licenses.

OpenLM Logs Uploader

The OpenLM Logs Uploader extension enables loading of historical FLEXlm debug log files. This extension is essential for investigating historical license usage. Logs Uploader is also necessary for checking license usage in files received from customer sites, typically in order to charge per use.

Please follow and like us:

OpenLM Version 1.6.0.1 – Maintenance release

Version 1.6.0.1 is a small maintenance release fixing small problem found by our customers that upgraded to version 1.6. We recommend all users of version 1.6.0 to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.0.1?

  1. Fixed a  problem with HASP date.
  2. Active Directory syncronization doesn’t synchronize disabled users now.
  3. Narrowing license output chart when the date overlaps from one month to another.
  4. Report Tab clear filter does not clear all fields.
  5. Fixed OpenLM Broker configuration tool startup script for Windows Server 2003 and Windows XP.
  6. OpenLM Broker – when adding a new port, the default configuration will be “Periodic”.
  7. Fix OpenLM Broker installation problem when Java does not exist.
  8. Easyadmin Control Panel – Feature usage status window – make numeric columns sortable.
  9. OpenLM Agent install error on pre-vista OS’s (XP and Server 2003) solved.
Please follow and like us:

Collecting project information for usage using OpenLM Software

Preface

OpenLM Software allows organizations to collect usage data for billing and management purposes. OpenLM supports different policies, by groups or by project. Collecting information by groups is most common, the organization is using OpenLM in order to collect information according to any sub-division: subsidiaries, divisions, departments, etc.. The information is then used in order to implement the billing policy selected by the organization: charge by the hour, distribute maintenance costs between cost centers, or other.

Billing usage time by the active project is mainly used by project oriented companies. It helps such companies to calculate a more accurate cost of the project by collecting the usage time for each project.

Supported Software Systems

The process of collecting project information for software usage is supported for software systems that are using license managers such as FLEXlm (FLEXnet), SafeNet RMS, SafeNet HASP, IBM LUM, LMX and more.

These types of license managers are used by high-end software systems such us: ESRI ArcGIS, AutoDesk Autocad, Pro Engineer, PTC, Catia, Matlab and more.

Setting project support settings

OpenLM interfaces that allow the system administrator to perform the following actions:

  • Create new projects.
  • Set project state (Active, Not Active).
  • Assign users to projects (or remove).

Version 1.5 of OpenLM provides these interface by using OpenLM Users Management Module. From version 1.6 and on, we integrated these interfaces into OpenLM EasyAdmin.

The project collecting capability needs to be activated from OpenLM Server Configuration form. This can be done by navigating to the Projects tab. The following options are available:

Activating projects capability (“Log Project Information”).
Minimal Usage Duration – User can set a short period of usage that won’t be considered as actual usage.
Agent’s Behavior – Allows the system administrator to select one of two policies, by using OpenLM Agent functionality or by Environment Variables. The use of OpenLM Agent functionality is more user friendly and provides a more accurate results.

Environment Variables – The use of an environment variable is simple, set the name of the environment variable and OpenLM will automatically collect the information based on the environment variable settings. Using these option may also require the use of “Add unknown projects”, OpenLM server will automatically create unknown project names reported by users.

OpenLM Agent functionality – OpenLM actively collects project information for usage sessions. OpenLM Agent provides the following functionality:

  • Active Project prompt popps up automatically from OpenLM Agent when the user is activating the licensed software.
  • Active project prompt to pop-up every few minutes, in case the user switched to another project.
  • Active project prompt can be set to disappear automatically when the user ignores it.
  • The user can also activate the active project prompt from OpenLM Agent icon at any time.

Generating Reports

OpenLM EasyAdmin->Reports Tab provides reports based on active project. The user can generate usage reports at any time and limit the query by almost any argument.

Individual sessions can be reported by using OpenLM EasyAdmin->License activity tab.

Synchronization with external systems and sharing information

OpenLM allows organization to synchronize project assignment information automatically with external systems like the organization project management system.

OpenLM supports the update of the project list and and assignment of users to project through OpenLM API.

External systems can also access the project information and totals by using OpenLM API.

Summary

OpenLM System provides a complete infrastructure that allows organizations to implement a billing policy for licensed software usage. The system supports billing policy based on groups or users, projects or both together.

OpenLM Supports automatic synchronization of project information with external system like project management systems.

Please follow and like us: