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:

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:

OpenLM Version 1.8 Preview

The upcoming OpenLM release version 1.8 is a major milestone in the development process of the OpenLM license management system. This version has been in preparation since October 2011, when version 1.7 was released, and is expected to be officially released by the end of 2012.

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

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

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database:

  • Archive or delete old data,

  • Extract irrelevant users, delete unnecessary groups, or even

  • Use multiple OpenLM servers on a single Database. This is a prerequisite for providing support for cloud – computing license management environments.

EasyAdmin

Many changes have been made to the EasyAdmin administrative interface, making the presentation of usage reports more efficient, robust and better designed. Here are some of these enhancements:

  • Support of the Apple Safari Browser
  • License Expiration date filtering
  • License Manager Up-time logging
  • Improvements in License usage reporting (e.g: Flexnet / FlexLM reporting).
  • Improvements Feature usage reporting: accessible from every workstation.

Packages

Software packages are automatically recognized, and populated by the software product  which are members  of these packages.

User Group monitoring

The group monitoring tool would be integrated into OpenLM v1.8, and enhance OpenLM’s ability to provide clear group-related license statistics.

Support of new License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 already incorporates the support of FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta LM, Mathematica LM (MathLM), and Easycopy, and the list is constantly expanding.

Version 1.8 has seen the addition of Beta-LM, Mathematica LM (MathLM), and DSLS. In addition to that, support of some license management tools was enhanced, for example – the IBM_LUM license manager has been added expiration date and license denial indications.

Please follow and like us:

OpenLM – LM-X license server support

OpenLM version 1.6 supports the LM-X license manager. The configuration of LM-X license managers is as easy as adding FLEXlm servers.

There is a known issue with version 3.5 of lmxutil, it does not detail users in the license output. When OpenLM is monitoring a software licensed using LM-X version 3.5 it will only report licenses, not users.

This bug is fixed in version 1.6 of LM-X. Software systems using version 1.6 of LM-X are fully supported in OpenLM.

Please follow and like us: