Application Note 1032: Monitoring FlexLM license denials

General:

OpenLM monitors and optimizes the usage of various license managers (e.g.: FlexLM / Flexnet publisher, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc).

As part of FlexLM license monitoring, OpenLM also produces license denial reports, i.e.: an account of instances where the vendor daemon has declined an application’s license request. License denial is a key parameter in license maintenance and in the planning of additional license procurement.

The Denials report window

License denial information is clearly presented in the OpenLM EasyAdmin web interface, in the Reports → Denials window. It includes the details of the denial event (Denied user, Denied workstation, Time, License Server, Denied Feature, and vendor) as well as the cause for denial (e.g.: limit of available licenses reached or User on Option file exclude list)

Set up OpenLM to monitor license denials

In order to produce denial reports for monitored licenses, please:
1. Set up the OpenLM Server to monitor the License server. In this case, the host is vmw_win2008_64, its type is FlexLM, the Server port is 27000, and the time zone is Central:

2. Install the OpenLM Broker on the License server machine:
Application Note 1004: OpenLM Broker quick start guide
Make sure that the License server name is exactly (case sensitive) the same as configured in the OpenLM server configuration tool (e.g.: vmw_win2008_64). The OpenLM server in this example resides in 102.101.100.135. The Broker communication port is (by default) 7016.

3. Set the OpenLM Broker to read the Denials’ information from the Monitored application’s debug log file: Type in the filename and click the ‘Enabled’ check box in the image below. Click ‘Apply’ and “Restart Broker” to finalize the configuration.

4. Make sure the Broker indication in the EasyAdmin “License Servers” window turns green. Note the green rectangle adjacent Server name vmw_win2008_64 in the image below. If it isn’t so – wait a while and refresh the “License servers” window. If it is still red – recheck your configuration, and check for alerts in the Easy Admin → Start → Management → Alerts window.

License number surpassed: Case study

In case the number of licenses has been surpassed – the vendor daemon would deny the license request, and a license denial notification will be produced. In the case of AutoCad: this is Network license error -96.

The debug log file shows this too as a string
Licensed number of users already reached. (-4,342)
Note the last denial report at 4:12:22 (Central time US):

It would also be apparent on the EasyAdmin Denial reports window at 11:12:22, according to the difference in time zones between the location of the OpenLM Server (Europe) and the AutoCad License server (Central time, US).

This same information can be presented as a column or pie chart, according to Users, Servers, Vendors, Features or time of occurrence.

Troubleshoot: Denials do not appear in the Flexnet debug log

Denial reports may not appear in the FlexLM debug log if the application’s option file contains a NOLOG line, with a DENIED flag. If this is the case, edit the option file to exclude this flag, and restart the license server. See this document for more information.

Document Revision Table

Version Author Date Changes
0.1 – Preliminary Orik Oct 25, 2012 Preliminary
1.0 Orik Dec 17, 2012 Added troubleshoot

 

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:

IBM LUM i4blt command reference

Scope:

Even though the IBM LUM license monitoring tool has decreased in popularity over the passed several years, it is still a widely spread tool for monitoring and tracking license usage of many CAD applications.

The OpenLM license monitoring tool extracts information from a variety of license managers, such as Flexnet / FlexLM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and – of course IBM LUM. OpenLM extracts comprehensive license reports and obtains license statistics for all these lisence managers.

In order to interface the IBM LUM license manager, OpenLM employs the i4blt command.
The i4blt command is very versatile; its usage depends on the attached i4blt flag options. The following document is a reference to some of these flags.

Syntax:

There are several syntax rules to be met:
1. Named strings containing spaces must be presented within single quotation marks.
2. Names are case sensitive
3. Listed values must be presented within double quotation marks, e.g.:
i4blt -lp -n my_server -v “‘Vend A’ ‘Vend B'”
4. Parameters that appear within options are position specific, e.g.: vendor information in the i4blt -E (Enrollment) option include vendor_name, vendor_id, and vendor_password.

Command reference

The following diagram is a reference to some of the main i4blt options. The Yellow rectangle is a complete reference to the primary i4blt command options. the turquoise rectangles contain elaboration for some of these primary options.

Usage examples:

The following are usage examples of the i4blt command. The examples are taken from real workstations, and include genuine usage information. They were cleared of any user identification markings.

i4blt -s -lc

In order to obtain current license usage information, OpenLM employs the i4blt -s -lc option.

i4blt -ln

The list display option with the ‘n’ flag lists the servers which are monitored by the IBM LUM.

i4blt -r1 -e

The r1 report type enables the extraction of  further information. This example shows license related event logging, in this case: license release.

Forward reading

I have found the following links helpful:
From the University of Alberta

A bit about HAL (High – Availability licensing) : i4blt -H.

Please follow and like us:

License manager ports: FlexLM(Flexnet), DSLS, IBM LUM, LM-X, Sentinel HASP, Sentinel RMS, Reprise RLM.

General

Licensed applications communicate with license management tools over predefined ports. system administrators need to know these port numbers, verify that these ports are open and communication via these ports is kept functional.

The OpenLM Utilizer tool interfaces various license managers in order to extract license statistics and usage reports. The license manager ports are different for each tool as elaborated below, and need to be configured correctly in the OpenLM modules.

How do I know the port I need is open for communication ?

The simplest method for verifying that a port is open for communication is by ‘Telnet’. The Telnet utility comes built in Windows XP, but needs to be installed on Windows 7. Open a command line prompt, and type in the following line: telnet <Hostname or IP> <Port number>. For example:
> telnet 123.123.123.123 27000 or > telnet My_Hostname 27000
If the cmd window remains blank, the port is open. Otherwise, an error string would appear.
In such a case, it is suggested to do the following:
1. Make a port exception in FireWall, or temporarily disable it altogether, to ascertain whether the Firewall is to blame.
2. Temporarily disable the Antivirus, to ascertain the same.
3. If a hostname was inserted in the command line, try typing in an IP instead.
4. Try a different port, or ‘ping’ the server:

Specific license management tools

Flexera FlexLM ports:

The OpenLM license monitoring tool provides unique abilities for monitoring and controlling Flex-enabled applications. The FlexLM ( Flexnet ) license manager communicates through ports 2080 and 27000 to 27009. In order to verify which ports are used, please read this short post.
The ports may also be altered, and set up statically by the system administrator.

Dassault Systemes DSLS ports:

DSLS employs three ports for License management:

  1. Administration port: default 4084. Connecting the License Administration Tool GUI to the Server.
  2. Licensing Port: default 4085. Used by clients to request licenses.
  3. Failover port: default 4086.Used for communication among cluster members.

IBM LUM ports:

LUM Network Client and Server communicate over UDP protocol on Network License Server port (by default 1515).

LM-X ports:

LM-X Network Clients and Servers communicate through port 6200 (default) over TCP.

Sentinel HASP ports:

The Sentinel HASP License Manager uses port 1947 to transfer data over TCP and UDP protocols.

Sentinel RMS ports:

  • The Sentinel RMS License Manager uses port 5093 to transfer data over UDP between Servers and clients.
  • Port 5099 is used for intercommunication between servers in a Server Redundancy constellation.

Reprise RLM port:

RLM uses port 5054. It was port 9000 prior to RLM version 6.

Please follow and like us:

Extracting DSLS information using command lines

OpenLM supports a wide variety of license managers for license statistics and the extraction of license usage reports. Among these license managers are Flexera Flexnet, DSLS, IBM LUM, LM-X, Sentinel RMS, and Sentinel HASP. During the development of OpenLM’s interface to Dassault Systemes’ proprietary license manager: DSLS, we needed to extract DSLS information using command lines.

The following is an account of the commands used in this process, and examples for commands’ output. The logs are typed in a manner that would fit this page, and are edited to be non-personalized.

Command:
DSLicSrv -admin [-I inputFile] [-t OutputFile]
Employ the DSLS license administrator tool in command line mode.

  • Optionally redirect the output to OutputFile
  • Optionally run the license administrator commands from a command file.

Outcome:
The DSLS administrator tool was employed in command line mode. The admin> prompt appeared.


Command:
connect <HostName> <port>
Connect the administration tool to a license server <HostName> on a specific port <port>.

Outcome:
The following was emitted on the screen:
License Administration Tool Version 6.210.0 Built on Oct 6, 2010 10:49:19 AM.
admin >connect <HostName> 4084

Software version : 6.210.0

Build date : Oct 6, 2010 10:49:19 AM

Standalone mode Ready : yes

Server name : <HostName>  

Server id : <ServerId>

Command:
getConfig
Get license server configuration

Outcome:
The following was emitted on the screen:

admin >getConfig
Server configuration Standalone mode
Computer name : <HostName>

Computer ID : <ServerId>

Licensing port : 4085

Administration port 4084

Password protected : no

Remote administration enabled : no

License usage statistics enabled : no

Command:
getLicenseInfo
Get license information

Outcome:

The following was emitted on the screen:

admin >getLicenseInfo

Status active

Editor Dassault Systemes

Model ConcurrentUser

Feature <Feature name>

Quantity 50

StartDate 2011-08-17.00:01.UTC

EndDate 2012-08-31.23:59.UTC

MaxReleaseNumber 1

MaxReleaseDate 2012-08-31.23:59.UTC

MaxUsageDuration 0

MaxUsagePeriod 0

LicenseType Floating

CommercialType STD

LicenseId <LicenseID>

RepGroupIndex 1

RepFileIndex 1

RepFileQuantity 2

ComputerId <ComputerID>

ComputerName unknown

CustomerSite <CustomerSite>

CustomerCountry USA

CustomerId <CustomerId>

GenerationDate 2011-08-18.20:20.UTC

GenCompany Dassault Systemes

GeneratorId <GeneratorId>

EditorId <EditorId>                             


Command:
getLicenseUsage -all
Show current license usage

Outcome:

The following was emitted on the screen:

admin >getLicenseUsage -all
Dassault Systemes <EditorId>

// 1st Feature
<FeatureName 1>  release : 1

type : ConcurrentUser

count : 50

inuse : 2

      // 1st usage table:

      consolidation : <HostName>/<HostName>

      granted since : Nov 28 2011 11:38:14

      <HostName> (<identifier>)  <UserName> <draftsighthelper directory>

      // 2nd usage table
      .
      .
      .

// 2nd Feature …
.
.
.
Command:
disconnect
Disconnect the DSLS administration tool from the license server.

 

 

Please follow and like us:

Where can I download Sentinel HASP and Sentinel RMS license managers ?

The Sentinel HASP and Sentinel RMS license management tools may be downloaded from the Products section on Safenet’s web site, under the “Licensing and Management” title.

The OpenLM server seamlessly interfaces both tools, in order to extract comprehensive license statistics reports.

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: