Monthly Archives: October 2011

Application Note 1000: OpenLM system structure overview

Posted on by

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.

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

Posted on by

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

General:

FLEXLM ( FlexNet publisher ) 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 file’s setting.

Employing FlexLM option files, the license administrator can:

1. For concurrent (floating) licenses:

  • Allow the use of features

  • Deny the use of features

  • Reserve licenses

 

Concurrent licenses can be held either in license files or in fulfillment records within trusted storage.

2. For all license types:

  • Restrict the number of licenses available

  • Control the amount of information logged about license usage

  • Enable a report log file

  • Control the automatic rereading of licenses

 

FLEXlm Option files are implemented as text files, located on the license server. Although  this method fits the licensing requirements well, the process of creating and maintaining option files is error-prone and difficult to maintain.

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

 

Creating an Option File

1. The Option file should be placed under the same directory as the vendor daemon file, in order to enable FlexLM to read it automatically. Locating the Option file in a different folder is possible, but this requires FlexLM to be configured to search for it in that location.

2. The recommended name for the Option file is vendor.opt, where vendor is the vendor daemon name. Note that the name should not contain white spaces ( e.g.: Arcgis vendor: arcgis.opt,  Adsflex vendor: adsflex.opt ) “Vendor name.opt” is illegal.

FLEXlm option file editing

When configuring the option file using OpenLM, the configuration data is presented to the OpenLM Server, and forward by it to the OpenLM Broker, located on the license server machine. The OpenLM Broker updates the option file.

OPENLM SERVER CONFIGURATION

Check the “Enable OpenLM option file management” box

 

It is necessary to install the OpenLM Broker on the license server machine in order to edit the option file using the OpenLM EasyAdmin web application.

OPENLM BROKER INSTALLATION

  • Information about the OpenLM Broker and its installation process is available in Application Note #1004.

  • The latest OpenLM Broker version  is available for download for version 1.8. If you need a previous version please contact Support@openlm.com.

OPENLM BROKER CONFIGURATION

The next step after creating an option file on the license server machine, is to configure the OpenLM Broker to work with it.

 

1. Open the “OpenLM Broker configuration tool” installed on the license server machine

(“Start” → “Programs” → “OpenLM” → “Broker” → “Broker Configuration Tool”). The Broker Configuration Tool window appears.

 

2. On the Broker Configuration Tool window, Click the (+) button near the License server name in the configuration window.

 

 

3. Click the (+) button near “Vendors” (1).

 

4. Click the “Edit” button.

 

5. Check the “Watch Option File” box (2)

 

6. Type in the path to the Option file previously created. (3)

 

7. Restart the OpenLM Broker.

Editing Option Files

OPTION FILE TARGETS: USERS, USER GROUPS, HOSTS, HOST GROUPS AND IPS

Option Files apply license permission limitations to certain target categories; namely Users, User groups, Hosts, Host groups and IPs. Setting up and introducing these targets is beyond the scope of this article, but a short explanation on each of these target categories is attached at the end:

In order to edit option files, select a specific option file, and then apply changes to it.

OPTION FILE SELECTION

1. Open the OpenLM EasyAdmin web application.

2. Click Start → Opt. File Admin. The “Option File” dialog window appears.

3. Select the specific Option file to be edited (e.g.: Autocad Option File) and click “Set”.

 

GLOBAL SETTINGS OF THE VENDOR DAEMON

On the EasyAdmin web application click Start →  Option Files → Policy.

The “Policy of Option File” window appears.

This window comprises of several text boxes:

GROUPCASEINSENSITIVE (OFF / ON)

ON: User names and host names specified with the Options File GROUP and HOST_GROUP keywords respectively, are treated as case insensitive.

OFF (Default): User names and host names are treated as case sensitive.

NOLOG { IN | OUT | DENIED | QUEUED }

Suppresses logging of the selected type of event in the debug log file.  License administrators may use this option to reduce the size of the debug log file, however it can reduce the usefulness of the debug log when debugging license server problems.

  • IN / OUT: Turns off logging of license check-ins and check-outs respectively.

  • DENIED: Turns off logging of license check-out denials.

  • QUEUED: Turns off logging of queued license requests.

REPORTLOG

Specifies the report log file for this vendor daemon. It is recommended to precede the report_log_path with a ‘+’ character to append logging entries; otherwise the file is overwritten each time the daemon is started.

TIMEOUTALL

Specify the idle timeout for all features, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

DEBUGLOG

Writes debug log information for this vendor daemon to the specified file.

Note that this affects output from only the vendor daemon associated with this options file. The debug log output of lmadmin or lmgrd and any other vendor daemons in the same license file is not captured in this file.

Click the ‘Save’ button in order to save the edited configuration.

FEATURE SETTINGS

On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘Features’.

The “Features of Option File” window opens, according to the option file selected before. This window enables the configuration of each feature separately, applying changes either globally or to specific Users, User groups, Hosts, Host groups and IPs.

1. Select a feature. The ‘Permission’ column is filled

2. Select a user (shown in the screenshot below):

2a. Select the Users tab

2b. Click the ‘Add’ icon. The “Users search” window appears.

2c. Mark users from the “Users search” window, and click the ‘Select’ icon. The selected users are added

3. Select a specific permission, and set its value as explained here:

BORROW_LOWWATER:

Sets the minimal number of BORROW licenses that cannot be borrowed, i.e: the minimal number of licenses that need to remain as Network licenses. For example, if FEATURE has a count of 10, borrowing is enabled in the application, and BORROW_LOWWATER = 7 then only 3 licenses may be borrowed. This option is used for licenses held in license files.

LINGER:

A lingering license stays checked out for a specified period of time beyond its checkin or FlexEnabled application exit, whichever comes first. This configuration enables users to extend the linger time for a feature beyond its check in.

Note:

  • The software publisher sets a minimum linger value. If a value smaller than the minimum is configured, the minimum value is used.

  • The linger time may be configured by the software publisher in the FlexEnabled application. When this is the case, the longer linger time is applied.

MAX_BORROW_HOURS:

Change the maximum borrow period for a specific feature. The new configured period value must be less than that in the license file. This option is used for licenses held in license files.

MAX_OVERDRAFT:

The overdraft policy allows a software publisher to specify a number of additional licenses which users are allowed to use, in addition to the licenses they have purchased. This allows your users to not be denied service when in a “temporary overdraft” state. The MAX_OVERDRAFT parameter Limits the overdraft usage to less than the amount specified in the license file.

TIMEOUT:

Specify the idle timeout for a feature, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

SETTING PERMISSIONS ON SPECIFIC FEATURES

Some Option permissions may be applied according to the following categories: Users, Groups, Hosts, Host Groups and IPs as shown below.

These configurations include

  • Reserved: Reserve licenses for a User / User group / Host / Host group of users/hosts.

  • Included: Allow a user to use a feature.

  • Excluded: Deny a user access to a feature.

  • Borrow Included: Allow a user to borrow licenses.

  • Borrow Excluded: Deny a user the ability to borrow licenses.

  • Max: Limit usage for a particular feature/group—prioritizes usage among users.

ALLOW OR DENY THE ENTIRE VENDOR’S FEATURE SET

It is possible to Allow or Deny a category of users (user\group\host\host group\IP) the entire set of features that a specific vendor daemon serves. In order to do that:

  1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → “All Features”.  The “All Features …” window appears.

1. Add a Category of users (User \ Group \ Host \ Host Groups \ IP)

2. Check the “Include All” or “Exclude All” radio button;

  • Include All: Allow a user to use all features served by this vendor daemon.

  • Exclude All: Deny a user access to all features served by this vendor daemon.

3.Click ‘Save’.

SAVING THE OPTION FILE ON THE LICENSE SERVER

Saving the changes made to the Option file back to the License Server is done as follows:

1. On the EasyAdmin web application window click “Start” → “Opt. File Admin.”

2. Select the specific Option File, and click “Set”.

3. Select “Save back to server”.

The Option file update mechanism

  • The OpenLM Server writes this request to a table on OpenLM db and waits.

  • Every 10-15 seconds the OpenLM Server checks that table for any new messages for sending to the OpenLM Broker.

  • If such messages are available, the OpenLM Server sends the option file back to the broker.

  • The OpenLM Broker receives the new option file. It creates a copy of the old option file and replaces it with the new one.

  • After that, the broker issues a re-read command to the license manager. If the re-read was successful, the process is complete.

This procedure refers to user permissions. The same permissions are applicable to Groups( a groups of users ), Hosts, Host Groups (defines a group of hosts) and IPs.

 

Appendix A: Users and Groups

There are two methods of introducing new users and user groups to the OpenLM system. One is through the EasyAdmin web application, and the other is by synchronizing with a company’s Active directory. Both these methods are elaborated below.

SYNCHRONIZING USERS AND USER GROUPS WITH AN ACTIVE DIRECTORY (AD)

The best way to add users and groups is to synchronize them with the AD. OpenLM supports such synchronization:

1. Open “OpenLM Server Configuration” (Start →  Programs → OpenLM →  OpenLM server configuration )

2. Select the “Active Directory” tab.

3. Enter The following information in order to connect to the AD and synchronize users:

3a. Domain name: The Active Directory domain name is the full Domain Name System (DNS) name of the domain.

3b. Active directory user name and password, in the respective fields.

4. From the LDAP Server drop-down menu select “ActiveDirectory”.

5. Check the “Synchronize users” checkbox.

Another method for adding users and groups makes use of the EasyAdmin “Users & Permissions” menu:

INTRODUCING A NEW USER

On The EasyAdmin window, Click Start → Users&permissions → Users. The User details window appears.

Insert the required data, Check the ‘Enabled’ box,  and click the ‘Save’ button.

INTRODUCING A NEW USER GROUP

  • In The EasyAdmin web application, Click “Start” → “Users & Permissions” → “Groups”. The Groups window appears.

  • Click the green “Add Group” icon in order to create a new group. Enter the new group name (e.g.: my_new_group), and click “OK”.

 

  • On the “Groups” window, select the newly created group (e.g.: my_new_group), and click the “Members” icon to add new members to the group. The “Users in my_new_group” window appears.

  • Click the green ‘Add’ button. The “Users search” window appears. Mark and select users from the “Users search” window to add to my_new_group.

Appendix B: Adding an IP

What is an IP?

An Internet Protocol (IP) address is a numerical label assigned to each device (e.g., computer, printer) participating in a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: Host or Network interface identification and location addressing.

Controlling the license usage of a specific computer is made possible by the “IPs” tab on the “Features of Option File” window. It is also possible to control the license usage of an IP range of computers. For example, typing in the IP:  123.123.123.* causes the feature configurations done in the “Features of Option File” window to be implemented on all user IPs in the range of 123.123.123.0 through 123.123.123.255.


Adding a specific IP:

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip address you want to add.

Add a range of IPs

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip range you want to add (as explained above).

 

Appendix C: Adding a Host Group

About Host Groups

Custom groups of virtual machine hosts may also be created, for grouping of hosts and their virtual machines in meaningful ways. For example, you may create a host group for every branch office in your organization. You can also use host groups to set aside resources on hosts in the host group for the use of the host operating system.

1. On the EasyAdmin web application window click “Start” →  “Option Files” → “Host Groups”. The “Host Groups” window appears.

2. Click the green ‘+’ sign, and add a group (e.g.: my_host_group1).

3. Select the newly added group, and click the “Members” icon. The “Memebers of my_host_group1” window opens (see image).

4. Select the computers that are required for grouping, and click the green “Select” button. The new Host group is ready for use.

Revision

Revision 1.3 (Revised)

Authors: Mira, Orik, Chen

May 20, 2013.

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

Posted on by

General

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

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

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

OpenLM system requirements

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

Adding a Sentinel HASP Server

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

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

HASP Server Settings

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

OpenLM EasyAdmin display screenshots

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

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

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

Posted on by

General:

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

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

  2. Installing the OpenLM components

  3. Configuring the OpenLM components

  4. Setting up the OpenLM database

  5. Running OpenLM 1.7, checking its proper functionality

Components of the OpenLM system

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

  • OpenLM Broker

  • OpenLM Agent

  • OpenLM Alerts

  • Log file Uploader

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

  • OpenLM Active Agent

  • External DB support

  • Groups and projects management

  • Role base security

  • Option file management

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

OpenLM Server

The OpenLM Server is the core element of the OpenLM system. It integrates the functionality of all other peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker.

OpenLM EasyAdmin

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

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

  • Management of license servers

  • License usage data extraction for Investigative and statistics purposes.

OpenLM Broker

The OpenLM Broker is an optional server component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server, and is required in order to provide advanced licensing information and sophisticated abilities.

OpenLM Alert

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

OpenLM Utilizer Agent

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

OpenLM Active Agent

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

OpenLM External Data Base (DB) Support

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

OpenLM Groups & Projects

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

OpenLM Role Based Security

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

OpenLM Option File Management

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

OpenLM Logs Uploader

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

System Requirements

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

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

You may also find this OpenLM FAQ guide useful.

Installing the system components

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

OpenLM Server

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

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

Continue the installation process:

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

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

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

4. Add a new license server:

  • Click the ‘Add’ button.

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

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

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

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

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

  • Check the ‘Enabled’ check box.

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

The image below demonstrates a configuration of four license servers.

Repeat steps 4 & 5 for all license servers.

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

You could find it on

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

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

The EasyAdmin Interface

The EasyAdmin web application is the main OpenLM users interface.

You could find it on:

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

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

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

OpenLM Broker

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

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

OpenLM Utilizer Agent (Windows)

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

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

OpenLM Active Agent (Windows)

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

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

OpenLM Java Agent (Unix/Linu)

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

OpenLM Alerts system

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

Setting up the OpenLM database

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

Revision table

Revision

Author

Date

Remarks

0.1 – Preliminary

Orik

Oct 17,  2011

Preliminary

1.0

Orik

Oct 30, 2011

Revised.

1.1

Orik

Jun28, 2012

Revised.

Application Note 1011: Quick Installation guide for the OpenLM license management system.

Posted on by

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

By the end of the installation process, The OpenLM Server configuration window appears.

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 a configuration of four license servers.

2. Select a license server and click the check button in order to ensure that OpenLM can retrieve information from that license server.

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

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

You can find it on

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

Step 3: The EasyAdmin Interface

The EasyAdmin web application is the main OpenLM users interface.
You can find it on:
Windows’ Start button → All Programs → OpenLM → OpenLM EasyAdmin2.

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

 

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

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 1010: OpenLM license management system Complete Installation guide” document.

Revision table

Revision 1.1

Author: Orik

Date: June 2012

Remarks: Updated

SECOPTENA to exhibit OpenLM at the PlanetPTC Live 2011 in Stuttgart, Germany

Posted on by
SECOPTENA, exclusive OpenLM Distributor for Germany & Austria will exhibit OpenLM at PlanetPTC LIVE 2011 which will take place in Stuttgart, Germany, November 15 and November 16.The OpenLM team is eager to meet you there.
Just stop by or fix an appointment now!
Email SECOPTENA: info(at)secoptena.com or call SECOPTENA: +49 8151 77499-55

For more information:

OpenLM Version 1.7.1.4 – Maintenance release

Posted on by

Version 1.7.1.4 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.7.1.4?

OpenLM Server:

  1. Easyadmin – option file features deleting bug.
  2. Easyadmin – sorting groups & projects reports now works..
  3. Easyadmin – “License Activity” & “Active Products” export in the correct number format.

Note: After upgrade, you may experience problems with “Licenses” window in easyadmin. If this is the case, open “User Settings” window, click “Clear Settings” and click “OK” for the problem to be resolved.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001″ which is related to a problem with Windows):

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

OpenLM Version 1.7.1.3 – Maintenance release

Posted on by

Version 1.7.1.3 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.7.1.3?

OpenLM Server:

  1. Allow time deference (60 seconds) with OpenLM Brokers on remote  servers when reading license output.
  2. Easyadmin permissions – Disabled users are now denied from logging into EasyAdmin.
  3. Easyadmin permissions – Failure to log in to EasyAdmin resulted in a scrambled text.
  4. Easyadmin permissions – Fix some bugs causing “Server Error”.
  5. Easyadmin – Disable existing usernames editing.
  6. Easyadmin – When adding group under root, refresh also root.
  7. Easyadmin – Fix error when sorting projects/groups report.
  8. Easyadmin – Checkbox selection disappears when sorting columns.

Note: After upgrade, you may experience problems with “Licenses” window in easyadmin. If this is the case, open “User Settings” window, click “Clear Settings” and click “OK” for the problem to be resolved.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001″ which is related to a problem with Windows):

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

Application Note 1006: OpenLM Roles and Permission Groups based security

Posted on by

Scope

This document describes the OpenLM “Roles and Permission Groups” feature, and serves as a quick reference guide to system administrators who seek intricate grouping and permission granting over their OpenLM managed licencing control system.

Table of contents:

1. General
* Permissions and roles
* Role inheritance
* Feedback
2. Creating a new role
3. Adding resources to a role
4. Creating a new user
5. Adding a user to a group
6. Assigning roles to a user or group of users
7. Changing a Resource’s permission attribute
8. Server Resource visibility
9. Permission arbitration

1. General

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

Permissions and roles

Permitting a Resource is the act of granting a certain accessibility level to that resource. Each permission is attached to a specific Resource, granting it a permission attribute. Permission attributes may hold either one of the following values:

  • Allow: The resource is accessible for a user or a user group.

  • Disable: The resource is visible but not accessible for a user or a user group.

  • Deny: The resource is neither visible nor accessible to a user or a user group.

A set of such Resource permissions is referred to as a role. Roles are attributed to certain groups of function holders in a company, each group having different accessibility options to OpenLM’s resources.

Roles’ implementation may be set on, enabling the differentiation of users and groups according to permission levels, or turned off altogether, thus granting all users and user groups full accessibility to all the system’s resources.

Handling of roles and permissions is easily done by system administrators on the EasyAdmin administrative interface of the OpenLM system. The intuitive EasyAdmin control panel incorporates all the options requires to configure the roles and permission groups according to administration requirements.

Role inheritance

Permission groups posses an inheritance property. This property facilitates the application of similar permission schemes to different groups. Thus different groups may be easily created  with only slight differences between their permission schemes.

Feedback

The characteristics of the roles and permissions feature have evolved over time, through constant feedback from OpenLM’s dependable customers, and are continuing to evolve according to common requests. For this reason OpenLM encourages its customers to send back their feedback and specific required features.

2. Creating a new role

In order to create a new role go through the following steps:

  1. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” → “Roles” tab. The “Role Details” dialog window appears.

  2. Type in the role name and description (e.g. “HelpDesk” and “Help Desk Team Role” as they appear respectively in the image above). Click the “Save” icon. Note that the new role name would be saved in lower-case format (i.e. “helpdesk”).

3. Adding resources to a role

Adding resources to the newly created role may be done in either one of two methods. The 1st is by manually selecting Resources and attaching them to the new role:

  • In the “Roles” window, Select the required role, e.g.: “helpdesk”. Click the “Edit” icon. The “Role Details for helpdesk” window appears (Similar to the “Role Details” dialog window depicted above).

  • Select the Resources tab, and click the green “Add” button. The “Resources Search” dialog box appears. Note that each line in this table contains a Resource name and description, easing the linkage between a registry in the table and its actual function in the OpenLM system.

  • Select a resource (e.g. the active_products_column_duration as marked above), and click the green “Select” button. The “Role Details” window’s “Resources” tab now appears with the newly attached “active_products_column_duration” resource.

Another option for adding Resource Permissions to the new role is by employing the inheritance property:

  • In the “Role Details for helpdesk” dialog window, select the “Parent Roles” tab and click the green “Add” icon. The roles search dialog window appears.
                
  • Select the role that would serve as the parent of the newly created “helpdesk” role, e.g. “admin_role” in the image below, and click the green select button. Note that the “admin_role” is the default basic role, and is always apparent for serving as a parent role. The new “helpdesk” role now possesses all the permission attributes of the parent “admin_role”.

4. Creating a new user

In order to a user to the users list, go through the following steps:

  1. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” → “Users” tab. The Users window appears.

  2. Click the “Add User” button. The “User details” form appears. Fill in the appropriate information items, check the “Enabled” box and click “Save“ as depicted below.

The new user’s information is presented attached to the Username on the “Users” window:

                      

5. Adding a user to a group

In order to add a user to a group, follow this procedure:

  1. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” → “Groups” tab. The “Groups” window appears.
  2. Select a group from the “Groups” window (e.g. “GroupName”), and click the “Members” icon in order to view the members of the selected group. The “Users in GroupName” window appears.
  3. Click the green “Add” icon, in order to add further users to GroupName ’s list of users.

6. Assigning roles to a user or group of users

After establishing a new role of permissions and introducing a new user or group of users, it is now possible to attach this role to the users, in order to assign the role’s permission set to these users. In order to do so, Please:

  1. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” → “Roles” tab. The “Role Details” dialog window appears.
  2. Select the new role (e.g. “helpdesk”), and click the “Edit” button. The “Role details for helpdesk” dialog window appears.
  3. Click the “Users” or “Groups” icon on the bottom of the window. The appropriate window (i.e. the “Users in helpdesk” or “Groups for Role”) appears.
  4. Click the green “Add” icon. The appropriate window (“User search” or “Groups”) appears. select the required instance of user or group, and click the green “Select” icon. The added user or Group instance has been added to the role, and may be seen there in the “Users in helpdesk” or “Groups for Role” window.

7. Changing a Resource’s permission attribute

In order to change a Resource’s permission attribute, e.g. to disable accessibility to this Resource by a certain role, follow this procedure:

  1. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” tab. Observe the “Workstations” tab. In this example – this would be the affected Resource.

  2. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” → “Roles” tab. The “Role Details” dialog window appears.

  3. Select a specific role, e.g. “admin_role”. Click the Edit button. The “Role details for admin_role” dialog window appears.

  4. Select a resource, e.g. “control_panel_menu_workstations” as depicted. Hover over the permission attribute of that Resource. a drop-down list appears. Click the drop down list, and select the required permission attribute value, e.g.: Disable.

  5. Click the save icon, close and reopen the OpenLM EasyAdmin UI.
  6. Click the ‘Start’ button on the EasyAdmin control panel. Select the “Users & Permissions” tab. Observe the LACK of the “Workstations” tab. It has been removed from the admin_role view.

8. Server Resource visibility:

If the permission of a Resource entry which name starts with the word “server_*” is disabled or denied, the respective user groups would become unable to view items on that server. Moreover, that server would become omitted from the OpenLM Agent’s “License usage information” window.

The following is an administrator Frequently Asked Question: “Why is all license usage information on the Agent blocked whenever an admin account is created in the OpenLM Server Configuration window?“ The answer is that when permissions are enabled, users need to be assigned a set of permissions that would allow them to view license servers’ details. In order to achieve this, please follow this action list:

Preliminary step: Create the required admin account on the OpenLM Server Configuration window: This can be done by unchecking, and then rechecking the “Enable permissions” highlited checkbox. A small dialog box subsequently appears, requiring a name & password for the new user (e.g.: User name: admin, Password: admin).

1. Create a role: Login to EasyAdmin with the “admin” account. follow the steps described in the “Creating a new role” section above.

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

3. Assign the new role to the “admin” user: In order to do so, Follow the description in the section “Assigning roles to a user or group of users” above.

9. Permission arbitration

Using the permissions tool, it is possible to grant resource permissions to single users independently. Also, as stated above, permissions may be inherited from parent roles. If one method grants permission and the other denies is, a mismatch condition may be present. in this case – an arbitration procedure is executed; The closest entity to a single user, i.e. a permission attribute granted to an individual user, or to the “youngest child” of an inherited attribute is the most “powerful”. If two contradicting attributes of the same strength are applied: an unknown condition may occur.

For example, picture the following constellation:

  • Admin role is parent to two roles: Role1 and Role2.
  • Admin denies permission to a resource.
  • Role1 does not explicitly refer to that resource, hence – it denies it implicitly.
  • Role2 explicitly allows the resource permission.

User attributes:

  • If User is attached to any one single role, its permission attributes will be the same as that of the role.
  • If User is attached to roles Admin and Role1 the permission will be denied.
  • If User is attached to Role1 & Role2, the permission would be allowed, since Role2 is the “youngest child” to infer to that resource.
  • If User is attached to roles Admin and Role2, an unknown condition occurs.
Revision Table
Revision Date Author Note
0.1 – Preliminary Sep 26, 2011 Orik Preliminary
1.0 Oct 16, 2011 Orik Revised

Application note 1008: OpenLM database migration: Firebird to MS SQL

Posted on by

Scope

This document is intended for system administrators who wish to perform an OpenLM database migration from Firebird to MS SQL. It elaborates the process and tools required for such a migration. This document is closely related to the
“Guide to OpenLM Data Migration Tool”,
“Upgrade guide of OpenLM Version 1.6 to Version 1.7”,
“OpenLM Database Configuration Form”  and
“Backing Up Your OpenLM DB”
documents, which are recommended for further reading.

Backup the current OpenLM database

It is good practice to begin with backing up the OpenLM database prior to migrating its content. In order to do so:
1. Navigate to the windows services (you can do that by searching for services.msc in the start menu’s search line).
2. Select the “OpenLM Server” service, and Click the Stop icon.

3. Backup the OpenLM database (typically located on:
C:\Program Files\OpenLM\OpenLM Server\db). Please refer to the “Backing Up Your OpenLM DB” document for a more detailed explanation.

Creating a new SQL Server Database: Building the tables

The first stage in migrating the OpenLM database is to create new empty database with OpenLM tables in SQL Server. In order to do so, OpenLM supplies dedicated DDL scripts (*.SQL files) to be applied in the SQL Server application.

1. The DDL scripts for the SQL Server is available for for download on the OpenLM site.

After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.7 section:

2. Now choose the DDL scripts section:
The Downloaded file contains two files for MS-SQL, and 2 for Oracle servers. In this document we would make use of the MS-SQL files.

3. Open the Microsoft SQL Server Management Studio
(Start → All Programs →  Microsoft SQL Server → SQL Server Management Studio).

4. Create a new DB: Right click the  “Databases” icon. select  “New Database” from the pop-up menu, as shown below.

5. Enter a new name for the database (e.g.: db_name) and click OK.

6. Drag the “OpenLM_SQLServer.SQL” file from the downloaded directory (e.g.: ddl_170) over to the Microsoft SQL Management Studio window. The Contents of “OpenLM_SQLServer.SQL” is displayed. (The file can also be opened by clicking “File → Open → File…” and selecting “OpenLM_SQLServer.SQL” from the unzipped folder).

7. Enter the new database name after the word “use” as shown below (e.g.: db_name) and click “Execute”

8. Wait until you see the message  “Query executed successfully” as shown below:

Data Migration

Now we get to the actual migration of data from Firebird to SQL Server.

1. Make sure that the original (Firebird) database is backed up, according to the Backup the current OpenLM database section, above.

2. Open the “OpenLM Data Migration” tool.

3. On the Source frame:

a. Select “Firebird”. The “Database Credentials” window appears.

b. Enter the Firebird database path in the appropriate text box.

c.Select your database(*.FDB) and enter the user name and password. By default, the user name is set to ‘sysdba’ and the password is ‘masterkey’

4. Target frame actions:

There are two alternatives for configuring the target frame. One is set for users who use the “Windows Authentication mode”. The 2nd alternative is for users who use the “SQL Server Authentication mode”.

For “Windows Authentication mode”:

a. Select the “MS SQL Server” radio button. The “Database Credentials” window appears.

b. Check the “Integrated security” box and click the “Test connection“ button. A  “Connection successful” message box appears upon completion of the test.

c. Select the database name (i.e. db_name from the “..building the tables” section above) from the “Databases” drop down menu, and click OK.

 

For “SQL Server Authentication mode”:

a. Select the “MS SQL Server” radio button. The “Database Credentials” window appears

b. Check the “Integrated security” box.

c. Enter the User ID and password as configured in the SQL server.

d. Click the “Test connection” button. A  “Connection successful” message box appears upon completion of the test.

e. Select the database name (i.e. db_name from the “..building the tables” section above) from the “Databases” drop down menu, and click OK.

5. After configuring the Source and Target databases, the migration process may begin. Click the “Transfer” button. At the end of the migration process, a notifier window appears.

Please refer to the “Guide to OpenLM Data Migration Tool” document for further information.

Configuring Openlm to work with the SQL Server

Now the OpenLM server must be made to reference the new SQL Server.
1. Open the “OpenLM Database Configuration” tool:
(Start → All Programs → OpenLM → Server → OpenLM Database configuration)

.

2. Click the DB provider drop-down menu. Choose one of the options: “SQL Server Authentication” or “Windows Authentication mode”. The “OpenLM Database Configuration” window changes accordingly:

3. Fill in the information in the blank text boxes.
4. Click “Check” to check the OpenLM server’s connection to SQL Server.
5. Click “Apply” to finish the configuration.

Please refer to “OpenLM Database Configuration Form” for further information.

Revision table

Revision Date Author Notes
Rev 0.1 – Preliminary Oct 11, 2011 Orik / Mira Preliminary
Rev 1.0 Oct 11, 2011 Orik / Mira Revised
Rev 1.1 July 03, 2012 Orik Slight changes