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:

Setting FlexLM port numbers statically

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

Please follow and like us:

Application Note 1022: Products and Packaged licenses in OpenLM

Scope

This Article deals with two adjacent subjects: Renaming licensed features as products, and gathering these features into licensed packages.

The OpenLM license monitoring tool is designed to extract license usage reports, and obtain license statistics. In order for these reports not to be confusing, the following points need to be considered:

  • Many features are only named as serial or coded strings, which bear little or no meaning for the end user. Renaming features is required in order to enhance readability and improve the understanding of EasyAdmin license reports.
  • Package or Suit licenses are, as their name implies, a set of features which are licensed together as a package. These kind of licenses should be dealt differently than individual licenses, in order to avoid confusion.

The Products/Packages window

The interface for handling Product names Packages in EasyAdmin is the “Products/Packages” window. Open this window:
Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.

Click the “Products/Packages” icon. The “Products/Packages” window opens.


Product names

The “Products/Packages” window enables users to define a meaningful product name to be displayed alongside a feature name. For example, the feature “40300MAP_5_0F” corresponds to the product “Map R5” in the image above. In order to edit the product name, click the Product name column for the row of that feature. There the product name is editable. Click the Save icon to commit your changes. The Add and Delete buttons at the top right can be used to insert or remove feature/product name combinations.

The “Products/Packages” window provides an interface to OpenLM’s translation table between Feature Names and Product Names. If this translation table is well maintained then the data reported on the EasyAdmin screens will be more comprehensible.

Setting up a Package in EasyAdmin

Here is a frequently asked customer question:
“We subscribed our application as a design Suite / Package. Each suite license includes licenses to several products. OpenLM indicates that we have a lot more licenses than we actually have. Moreover: having drawn a certain number of licenses, OpenLM indicates a smaller percentage of license usage than expected.”
This kind of complaint directly indicates a misconfiguration of packaged licenses.

Important Note:

Prior to OpenLM Server version 1.7.1.9, deleting a populated package resulted in an error. Make sure not to mark a populated package for deletion prior to this version .

Autodesk case study

In order to organize licensed features in packages, use the “Products/Packages” window. In this example, we’ll study the case of the “Autodesk Design Product Suite Ultimate 2012” Package.

  • In  the “Products/Packages” window, select the “Autodesk Design Product Suite Ultimate 2012” and check the “Is Package” checkbox.
  • Click the “Save” button.
  • Close and reopen the “Products/Packages” window. It is necessary to close and reopen the window after marking a product as a package.

  • Add each product in the suit to the list:
    • Select an item in the list, or click “Add” to add the product if you can’t find it there.
    • Select “Autodesk Design Product Suite Ultimate 2012” as the “Parent Package”. In the example below, the product suit corresponds with feature # 85796PDSU_2012_0f.
    • Click the “Save” button.
    • Repeat this for each item in the Package.



Revision Table

Revision Author Date Note
0.1 – Preliminary Orik Jan05, 2012 Preliminary
 1.0  Orik  Jun06, 2012  Slight changes

Please follow and like us: