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

Trouble Shoot Form: Item 02.001

Title Connection to SQL Server DB failed.
Category Data Base
Date Sep 26, 2011
Handled by Rachel.
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet Publisher, IBM LUM, HASP, RLM, Sentinel RMS, DSLS, LM-X
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer reported failure to connect to a new SQL Server through EasyAdmin. Succeeded in connecting it via the Configuration form “Check” button. Customer succeeded in connecting to old FB Server through EasyAdmin.
Observed during investigation Log contained fatal error:
Login failed for user ‘DPI\ORANTESTSPATIAL$’
Trouble shoot process Credentials issue
Solution Found (Options: Found/Pending/Known Issue)

Symptoms

Customer reported a failure in connecting to an SQL Server.
The “Check” button worked OK in the “OpenLM Database Configuration” dialog box, but EasyAdmin couldn’t connect to the SQL Server. See customer’s image below.

Observed during investigation

1. The customer defined the OpenLM Server (in the “OpenLM Database Configuration” dialog box) to work with SQL server using “Windows Authentication”. This means that logging to the SQLServer was done using windows credentials.

2. The customer clicked “Check” on the “OpenLM Database Configuration” dialog box, and it worked OK because the process worked fine with these windows credentials.

3. Then he started the “OpenLM Server”. It didn’t work because it had other credentials.
The customer sent a log containing these lines:

FATAL 2011-09-26 12:11:14,276 [thread 11]  SessionProducer CreateFactory – Can’t map nhibernate domains
System.Data.SqlClient.SqlException (0x80131904): Login failed for user ‘DPI\ORANTESTSPATIAL$’.

This means that a user named DPI (on server ORANTESTSPATIAL) could not login to the SQL Server, hence the system halts (FATAL error means that the application could not recover).

Trouble shoot process

  1. The “Database credentials” dialog box may be configured wrong, e.g.: check the “Embedded” check box in the window for Databases that are located on local drives.
  1. OpenLM Service credentials: In the “Windows Services” window, Select the “OpenLM Server” item. The “OpenLM Server Properties” dialog window opens. Select the “Log On” tab.

Here you can see under what credentials the service runs. By default we install it with “Local System Account” but some users change it.

We suggest acting according to one of these options:

1. Change the OpenLM Service credentials to that of a user who has both administrative permissions and a permission to login to the SQL server.

2. Another option is not to use the “Windows Authentication” (but “SQL Server Authentication”).

Please follow and like us:

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

 

Title License usage reporting information on the Agent is blocked
Category Permissions and Roles.
Date Jul 6, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Following the creation of an admin account in the OpenLM Server Configuration, all license usage information on the Agent is blocked
Observed during investigation
Trouble shoot process 1. Create a role.
2. Assign all the necessary resources, that will allow viewing details, to the new role.
3. Add users as members of this role.
Solution Found (Found/Pending/Known Issue)

Symptoms

The customer complained: “Every time I go to add an admin account in the OpenLM Server Configuration it blocks all license usage information on the Agent?  I’d like to password protect the EasyAdmin web application but still allow users to see the license usage through the agent. Is there a way to do this?”

Observed during investigation

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

Troubleshooting

When you enable permissions, users need to be assigned with a set of permissions that will allow them to view license servers’ details

1. Create a role: Login to EasyAdmin with the “admin” account. follow the steps described in the “Creating a new role” section of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

2. Assign resources to the new role: After you save the new role, the “Resources” tab will become enabled. Navigate to that tab. Note that it is assigned with one default resource. Now you need to add all resources that have this name pattern “server_servername” e.g. server_srv1 (where srv1 is the name of the server that you will grant access to). In order to do so, Follow the description in section “Adding resources to a role” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

3. Assign the new role to the “admin” user: In order to do so, Follow the description in section “Assigning roles to a user or group of users” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

 

Please follow and like us:

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

 

Title Following data migration from SQL to FB, EasyAdmin doesn’t show any logging
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer complained that EasyAdmin does not show any stats.
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

A customer complains that: “I have successfully connected the new database, BUT nothings seems to be logging. I have no stats showing on the EasyAdmin screen.”

Trouble shoot process

1. Make sure the license servers list is defined at the “OpenLM Server Configuration Form”
2. All settings of OpenLM are saved in the database. When you migrate to a different database (e.g.: from SQL to FB), you need to re-enter the license servers list.

  1. Switch to Firebird.
  2. Open “OpenLM Configuration Form”, navigate to “Advanced” panel, click “Export…” button and save the settings to a file.
  3. Close “OpenLM Configuration Form”.
  4. Switch to SQLServer.
  5. Open “OpenLM Configuration Form” again and you will see that servers list is empty.
  6. Navigate to “Advanced” panel, click “Import…” and import the file you saved earlier.
  7. Click “Apply” and restart OpenLM server.
  8. Check EasyAdmin.
Please follow and like us:

Trouble Shoot Form: Database Item 002 (Data migration from SQL to FB)

Trouble Shoot Form: Item 02.002

Title Data migration troubles, from SQL to FB.
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Symptoms Customer reported failure to import the SQL database to FB At first.
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

Customer reported failure to import the SQL database to FB.

Trouble shoot process

 

  1. Make sure the “Data Migration” tool version is compliant to the OpenLM version.
  2. A special version of the data migration tool is required for 64 bit computers.
  3. Migration of a database over to a new database that is not empty may result in failure to migrate certain tables. This is indicated by the following message: 

If this is the case, create a clean database again, and run the OpenLM_SQLServer.SQL” script to build the tables and try to migrate again.

Please follow and like us:

Get more out of your floating licenses

OpenLM is a complete floating license management solution designed to optimize the use of licensed software: more production for lower cost.
OpenLM is made to harvest idle licenses, and improve license utilization of any organization: big or small.

Who was the OpenLM Utilizer Designed For?

Unlike other license management systems that only offer administration and license monitoring statistics, the OpenLM Utilizer optimizes license usage in a unique manner that provides all personnel with useful license-related functions.

Organization managers:

  • Know what you have: Inventory.
  • Plan license maintenance and procurement of expensive licenses.
  • Charge projects or business units for software usage time.
  • Cut costs by dropping maintenance for licenses that are no longer in use.

Administrator view:

  • Real time license usage management
  • Alerts – Real time troubleshooting
  • Extract usage statistics information and patterns as reports or charts.
  • Roles and Permissions: Grant licenses according to specific Users’ permissions. Enforce concurrent License restriction.

End User View:

  • End users are not kept in the dark. They are informed about the status of denied licenses.
  • Receive a License availability notification when a license becomes vacant.
  • Who is using the license I need?
  • What is this person’s contact details?

Supported features

License managers:

  • OpenLM interfaces a wide variety of license managers, e.g.: FLEXlm / Flexnet, IBM LUM, Sentinel RMS, Sentinel HASP, RLM, DSLS and other leading license managers.
  • OpenLM supports Concurrent monitoring of multiple license servers on multiple time zones.
  • OpenLM supports management of Floating, Node-locked and Borrowed licenses.

Monitoring capabilities:

  • Easily review license inventory in real time.
  • Extract license activity reports, with configurable resolution.
  • Receive FLEXlm reports, statistics and charting (FLEXnet reports).
  • Receive Billing reports for any time period, per user or software (FLEXbill capabilities).

Infrastructure:

  • OpenLM may work over WAN and LAN networks.
  • OpenLM employs a web-based user interface that works with any supported browser.
  • A Mobile interface application enhances monitoring abilities for system administrators.
  • OpenLM may interface license managers that run on UNIX, Linux, or Windows’ Operating systems
  • OpenLM supports both external and embedded databases.

Proactive capabilities:

  • Release orphan licenses with a single mouse click.
  • Query users and licenses from any workstation.

Other features

  • A customizable alert system
  • An open, detailed API

OpenLM Architecture

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, OpenLM Alerts module and the OpenLM Utilizer Agent modules are also incorporated in the basic software package.

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. The OpenLM Server is implemented as a Windows service and could be installed on any network machine.

OpenLM EasyAdmin

An HTTP based application that can run on any machine in your network. EasyAdmin is the reporting and management interface of OpenLM. It facilitates extraction of lisence usage statistics, and usage repots, as well as the control and optimization of license usage.

OpenLM Agent

An optional component that can be installed on any machine on the network. The Agent enables end users to query license availability and find who is using the license they need at any point in time.

OpenLM Alerts

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

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 Screenshots

Watch the OpenLM EasyAdmin screenshots on the OpenLM site.

Want to evaluate the software ?

You can get the most updated version of OpenLM Utilizer from our OpenLM downloads area. After filling in your name and email – you’d be directed to the Downloads section. The Installation process is easy and straightforward, but if you still need any assistance – Please send an email to support@openlm.com, and we’ll be glad to help.

Please follow and like us:

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

General

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

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

Scope

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. This Application Note describes the feature as implemented in the 1.7 version.

Project usage reporting

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

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

Projects Settings

The OpenLM Server configuration tool’s ‘Projects’ tab defines the policy of the Project usage monitoring capability. Please note that Projects’ information logging requires the installation of the OpenLM Agent (Either Active Agent or Utilizer Agent) on the end-users’ workstations.

Log Projects Information

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

Minimal Usage Duration for Project

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

Active Project window

These settings define what end-users see on their workstations if they work on more than one project for their organization. If users are only allocated to one project, OpenLM will log their license usage without the need to take any action when the software is started. If the users work on more than one project, then a dialog box will appear on their screen prompting them to select the current project. The timing and duration for the appearance of this dialog box is configured here:

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

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

Hide projects option from menu

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

Support Environment Variable

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

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

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

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

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

Project creation

In order to create a new project, open the EasyAdmin web application.

  • Click the EasyAdmin ‘Start’ Button, and navigate to “Users & Permissions” → “Projects”. The “Project List” dialog box appears.

  • Click the “Add project” icon, and type in a name for the new project, e.g. “Proj1”.

  • Click the “Members” icon. the “Users in Proj1” appears.

  • Click the green ‘Add’ icon to assign users to this new Proj1.

Selecting the active project

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

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

2. Another option for setting the Active project is by a pop-up window. The appearance of this pop-up is configurable by options in the OpenLM server configuration tool’s ‘Projects’ tab, elaborated above.

Please follow and like us:

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

General

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

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

Scope

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

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

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

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

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

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

Project usage reporting

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

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

Projects Settings

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

Notes:

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

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

The ‘Projects’ window appears:

Note:

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

Log Projects Information

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

Minimal Usage Duration for Project

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

Agent’s Behavior Settings

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

Hide projects option from menu

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

Projects window fades away after

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

Allow creation of projects in Agent

This option has been introduced in the OpenLM 1.8 version.

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

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

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

Show unassigned projects

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

Support Environment Variable

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

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

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

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

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

Selecting the active project

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

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

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

Display at license retrieval

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

Display periodically every

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

Project creation in EasyAdmin

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

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

  • Project name

  • Start and End time for the project

  • Number of working hours allocated to this project

  • The project’s priority, and

  • The project’s completeness percentage.

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

Editing existing projects

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

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

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

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

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

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

Attaching users and user groups to the project

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

Appendix A: Projects information logging in v1.7

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

Please follow and like us:

Troubleshoot Form: Broker Item 001 (Broker Service Not Starting)

Title Broker Service not starting.
Category Broker
Date Oct 05, 2011
Handled by Efrat, Rachel.
Relevant Links (link to mantis item, docs, customer correspondance etc.)
Symptoms Broker service failed to start,
No broker log file was written
Applies to license managers FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation Error when attempting to run the broker service via command line.
Trouble shoot process 1. Run the Broker as a Java application (Not a service) from a command line, to establish whether the problem is in the application or just with running the service:
– Succeeded.
2. Check the registry for the required key.
– Failed.
3. Import the key.
Solution Fo

Symptom

Observed

Run net start “OpenLM Broker” on the command line.
The following error was observed

In this case

-NO log file is created, since the service does not run the application.

-NOR errors in the EventViewer

Trouble shooting:

  1. Try running the Broker from the command line.

This is running the Broker as a Java application, not as a service.

java -jar “C:\Program Files\OpenLM\OpenLM Broker\OpenLMBroker.jar”

start “C:\Program Files\OpenLM\OpenLM Broker\broker.xml”

 

In this case, this procedure succeeded. This means there is a problem only with the service and not the application.

  1. Check the Registry:

a. Open the registry editor : type regedit in the start command line.

b. Navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker

c. check that you have a Parameters key, with an Application name.

The value of this name should be:

“C:/Program Files/Java/jdk1.6.0_25/bin/java.exe” -Xrs -jar “C:\Program Files\OpenLM\OpenLM Broker/OpenLMBroker.jar” start “C:\Program Files\OpenLM\OpenLM Broker/broker.xml”

  1. If this key does not exist, save the following marked text in a .reg file, and import it under key OpenLM Broker:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker\Parameters]
“Application”=”\”C:/Program Files/Java/jdk1.6.0_25/bin/java.exe\” -Xrs -jar \”C:\\Program Files\\OpenLM\\OpenLM Broker/OpenLMBroker.jar\”  start \”C:\\Program Files\\OpenLM\\OpenLM Broker/broker.xml\””

Please follow and like us:

Application Note 1001_b: Configuring OpenLM to interface the Sentinel RMS license manager

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Sentinel RMS License Manager, and obtain reliable license reports and usage statistics.

Enabling the OpenLM server to work with RMS

In order to configure OpenLM to work with  Sentinel RMS, please follow this procedure:
1. Download lsmon.exe and lsapiw32.dll . These files aren’t included in the OpenLM installation package. For information on how to obtain these files, please contact OpenLM on support@openlm.com.
2. Copy these files to “C:\Program Files\OpenLM\OpenLM Server\LM”
3. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RMS.
4. Type in the full path of the executable file, i.e.:  “C:\Program Files\OpenLM\OpenLM Server\LM\lsmon.exe” in the “RMS executable file” text box.

See the following image for further clarification:

Introducing a new Sentinel RMS server

After configuring the OpenLM configuration tool to work with Sentinel RMS as elaborated above, the user may introduce an new  Sentinel RMS server under the License Servers tab:
1. Select the “License Servers” tab.
2. Select the RMS type from the “Type” dropdown list.
3. Type in a meaningful description in the “Description” text box.
4. Type in the appropriate “Hostname” and “Port” numbers. The Sentinel RMS default port is 5093.
5. Check the “Enabled” check box.
6. Click the “Apply” button. The  Sentinel RMS server is now ready to interface the OpenLM.

OpenLM Broker configuration for RMS

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the RMS license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RMS license manager type from the ‘Type’ dropdown list.
In the port’s Commands list make sure the ‘status’ command is
lsmon <License Server Name>

Document Revision Table

Version Author Date Changes
0.1 Orik May1, 2012 Preliminary
1.0 Orik Jun3, 2012 Revised.
1.1 Orik Jun6, 2012 Added Broker

 

Please follow and like us:

Application Note 1026: Basic OpenLM Server configuration for FlexLM

General

OpenLM supports the monitoring of a wide, and ever growing variety of license servers. Among those are Flexera FlexLM (Flexnet) , Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This is an description of the basic procedure for configuring the Openlm server to interface a FlexLM license manager, to monitor Flexnet reporting.

Procedure

Please first refer to this Application Note. It gives a general description of the OpenLM system; what should be installed where, and who needs to communicate with whom.

Install the latest version of the OpenLM server. It is found on the OpenLM site.

  1. Configure the OpenLM server so that it would communicate with the License server:
  • Open the “OpenLM server configuration window, On the “License Servers” tab (see image below).

  • Click the ‘Add’ button, and type in the license server parameters (Type, Host name (or IP), port & time zone). In order to find the Server name and port, please refer to this post.
  • You can type in a descriptive name to make recognizing the sever easier
  • In the image above, these parameters are: FLEXlm, olm-lm-arcgis10, 27000, UTC+08, “ArcGIS 10 Head Office”.
  • Click the ‘Apply’ button. Select ‘Restart now’. That’s it: the OpenLM server is
  1. Check the connection of the OpenLM server to the license server; click the ‘Check’ button. A text would follow. This text is a query of the License server. It indicates whether a connection to that server is established.
  1. Now open the EasyAdmin web application. Click start -> Management -> License servers. The “License servers” window appears. Verify that the configured license managers appear on the list. Circle nodes indicate a connection to a license server. Square nodes indicate a connection to a Broker which is installed on the License server machine.


Please follow and like us: