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\””

Multiple Server license management constellations

Flexera’s FlexLM (Flexnet)Three Server Redundancy (Triad)

IBM’s High Availability Licensing (HAL)

Dassault Systemes DSLS cluster for “Failover” mode

Scope:

License management tools such as IBM and Flexera both a method of employing multiple license servers in a cluster as part of their attempt to assure a fault-free license management solution. This article summarizes the operative measures required for implementing each of these solutions, and attempts to compare them in terms of pros and cons.

The OpenLM Utilizer license monitoring tool supports both configurations. OpenLM is designed to extract license statistics from multiple servers over WAN. It has been tried and confirmed for Flexera’s Triad configuration. At the time of writing this revision (Rev 1.0), It has not yet been verified with the IBM LUM HAL.

Flexera’s Three Server Redundancy constellation

General:

The Flexnet constellation is consisted of Three license servers, all inter-connected by TCP/IP. These machines are adequately named “Primary”, “Secondary” & “Tertiary”. Any one of the two first machines (Primary or Secondary) may be defined as the “Master”; which is counter intuitive, as it gets to do all the work while the other two basically sit on their hands. All licenses are served by this Master machine, and the Report & Debug logs are also accumulated by it.

Upon system start-up, the three FlexLM license servers are started up separately according to their order, and the Master role is set according to this order or according to a designated flag: “PRIMARY_IS_MASTER”.

The  FlexLM license Servers inter-communicate by a “Heartbeat” messages over TCP/IP, using the same port number. A machine which fails to receive a response to its sent Heartbeats turns down the vendor daemon and can not serve licenses. When the Master server (Primary or Secondary) fails, the Master role is passed to the other (Secondary or Primary) server. The new Master assumes the license management role for all the FlexEnabled applications, and accumulates new Debug and Report logs.

Configuration of a Three Server Redundancy constellation:

  • First, a set of three stable machines needs to be identified, and reliable communication needs to be set between them.
  • The software vendor must receive the HostID and Host name of the machines that consist the Triad. In return, they should provide system – specific license server files. Some changes may need to be done in the license file according to this new information, such as the PRIMARY_IS_MASTER value, the communication port number and the HEARTBEAT_INTERVAL which is effectively the timeout for license servers to be knocked out of the triad.
  • The license server package needs to be copied to each of the three participating servers.

Limitations:

  • There should always be at least two machines up and running. If any two machines halt – then the Triad is stopped as a whole, and no “FlexEnabled” applications are served. This is quite an odd limitation, as the system basically employs a single machine at a time anyway.
  • The “Tertiary” machine never gets to play “Master”. I find this an odd planning, because this in effect renders this machine useless.
  • This configuration puts a strain on one machine at a time. It does not share the work, and is prone for errors especially in busy environments.


IBM’s High Availability Licensing (HAL)

General

The IBM HAL is based on the “License server Cluster” concept. A cluster is a group of 3 to 12 license servers, that jointly manage licensed applications. The management activity load is dynamically and equally shared among most of the servers, while one or two other servers remain on-hold, waiting to pitch in in case an active server becomes unavailable.
Network license servers that participate in a cluster can simultaneously serve server-bound licensed applications,  as well as cluster bound applications.

Configuring HAL

  • Select a set of interconnected license servers as cluster members. These members need to be stable machines, that stay on permanently. Network stability is also crucial in order to assure faultless system activity. It is recommended to maintain the machines in the same geographical vicinity, and that they all run the same operation system type.
  • Instal LUM on each of the license servers.
  • Create the cluster from one of the servers in the cluster. This may be done using the i4blt -H command or the GUI. In the following example, cluster ThisCluster was created, and it contains 3 servers: Server1, Server2 & Server3.
    • i4blt -H c -N ThisCluster -T 3 -n “Server1 Server2 Server3”
  • Activate each member of the cluster. The 1st member is already enabled by default following the cluster definition. This example enables Server2:
    • i4blt -H a -N ThisCluster -n Server2

In order to Deactivate a Server2, use

  • i4blt -H a -N ThisCluster -n Server2
  • Get a HAL Enrollment Certification File (ECF) from the license vendor. In order to do so, You must send him the “Cluster ID”. This ID can be obtained by typing in the status cmmad:
    • i4blt -H s -N ThisCluster.
  • Enroll the HAL ECF just like as for regular license servers, using the GUI or the i4blt command line. for example:
    • i4blt -a -n ThisCluster -f <ECF> -T <NumberOfLicenses>
  • Configure all clients to recognize all the cluster members.

Dassault Systemes DSLS

The DSLS license manager also implements a cluster structure, for “Failover mode”. Its characteristics are a mix of the two types mentioned above;

  • A server may not perform as part of a cluster AND as a stand alone server at the same time.
  • The number of license servers that participate in the cluster are exactly 3.
  • The OS on each server may be either Unix or Windows.
  • At least two machines should be up and running, and interconnected  in order to serve licensed applications.
  • There is no ‘Master’ here: all machines have the same role of license management.
  • The three machines each log the license activity independently. They update each other when usage conditions change.


Summary

It seems that the IBM LUM solution for multiple server constellations is more comprehensive than that of Flexera’s. Its main ‘Pro’ characteristics include:

  • Equal sharing of the workload.
  • Dynamic redistribution of license management as a function of server availability
  • Configurable amount of servers; a maximal 12 server constellation, in comparison to 3 (effectively 2) Flexera servers.

The main ‘con’ on the IBM LUM list is its lack of popularity in comparison to Flexnet (FlexLM). This has manifested in a trend of licensed application vendor’s migration from LUM to various other license management tools, e.g. FlexLM and DSLS.

 

Further Reading:

http://www-01.ibm.com/software/awdtools/lum/hal.html

http://kb.flexerasoftware.com/doc/DocumentRepository/Licensing/FLEXnet_Publisher/FLEXnet_Publisher_11.6/03_ISV/Product%20Manual/LicenseAdministration.pdf

http://communities.mentor.com/mgcx/servlet/JiveServlet/previewBody/2877-102-1-5407/licensing_bp_wp-10.8.pdf

http://pdir.technodat.cz/r21/install_v5doc/doc21/online/basil_C2/pdf/DSLS.pdf

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.

 

 

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

 

AutoDesk FlexNet feature codes, March 2012

Feature codes

FlexNet (FlexLM) uses a predefined set of codes in order to manage multiple licensed Features. Each of these features is given a unique code, by which FlexNet grants license requests, and keeps track of the license pool.

OpenLM Also makes use of these feature codes during FlexLM reporting in order to monitor and optimize Autodesk license usage. As versions progress and features are added, the code tables need constant updating. The following is a complete list of AutoDesk codes, updated to March 2012. It was taken from Autodesk’s official site.

Autodesk code table

AutoCAD 2013 85871ACD_2013_0F
AutoCAD Architecture 2013 85883ARCHDESK_2013_0F
AutoCAD Civil 3D 2013 85976CIV3D_2013_0F
AutoCAD Design Suite Premium 2013 85969DSPRM_2013_0F
AutoCAD Design Suite Standard 2013 85970DSSTD_2013_0F
AutoCAD Design Suite Ultimate 2013 85971DSADV_2013_0F
AutoCAD ecscad 2013 85889ECSCAD_2013_0F
AutoCAD Electrical 2013 85890ACAD_E_2013_0F
AutoCAD for Mac 2013 85989ACDMAC_2013_0F
AutoCAD Inventor LT Suite 2013 85958INVLTS_2013_0F
AutoCAD LT 2013 85872ACDLT_2013_0F
AutoCAD LT Civil Suite 2013 85991ACDLTC_2013_0F
AutoCAD LT for Mac 2013  86021ACDLTM_2013_0F
AutoCAD Map 3D 2013 85981MAP_2013_0F
AutoCAD Map 3D Enterprise 2013 85982MAP3DE_2013_0F
AutoCAD Mechanical 2013 85885AMECH_PP_2013_0F
AutoCAD MEP 2013 85887BLDSYS_2013_0F
AutoCAD P&ID 2013 85977PNID_2013_0F
AutoCAD Plant 3D 2013 85978PLNT3D_2013_0F
AutoCAD Raster Design 2013 85952ARDES_2013_0F
AutoCAD Revit Architecture Suite 2013 85954REVITS_2013_0F
AutoCAD Revit MEP Suite 2013 85955REVSYP_2013_0F
AutoCAD Revit Structure Suite 2013 85957REVSU_2013_0F
AutoCAD Structural Detailing 2013 85943STRDET_2013_0F
AutoCAD Utility Design 2013 86027UTLDESN_2013_0F
Autodesk 360 Vault Collaboration 2013 85983VLTC_2013_0F
Autodesk 360 Vault Collaboration AEC 2013 85984VTCAEC_2013_0F
Autodesk 360 Vault Office 2013 85986PCOFFI_2013_0F
Autodesk 360 Vault Professional 2013 85987VLTM_2013_0F
Autodesk 360 Vault Workgroup 2013 85988VLTWG_2013_0F
Autodesk 3ds Max 2013 858923DSMAX_2013_0F
Autodesk 3ds Max Design 2013 85893MAXDES_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Premium 2013 85918MXECSP_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Standard 2013 85920MXECS_2013_0F
Autodesk Alias Automotive 2013 85881AUTOST_2013_0F
Autodesk Alias Design 2013 85896DESNST_2013_0F
Autodesk Alias Surface 2013 85895SURFST_2013_0F
Autodesk Animation Academy 2013 85922AAA_2013_0F
Autodesk Building Design Suite Premium 2013 85946BDSPRM_2013_0F
Autodesk Building Design Suite Standard 2013 85947BDSS_2013_0F
Autodesk Building Design Suite Ultimate 2013 85948BDSADV_2013_0F
Autodesk Entertainment Creation Suite Premium 2013 Exclusives 86043ECSPE_2013_0F
Autodesk Entertainment Creation Suite Standard 2013 Exclusives 86044ECSSE_2013_0F
Autodesk Entertainment Creation Suite Ultimate 2013 85926ENCSU_2013_0F
Autodesk Factory Design Suite Premium 2013 85965FDSPRM_2013_0F
Autodesk Factory Design Suite Standard 2013 85966FDSS_2013_0F
Autodesk Factory Design Suite Ultimate 2013 85967FDSADV_2013_0F
Autodesk Infrastructure Design Suite for Education 2013 85974ESCSE_2013_0F
Autodesk Infrastructure Design Suite Premium 2013 85992IDSP_2013_0F
Autodesk Infrastructure Design Suite Standard 2013 85993IDSS_2013_0F
Autodesk Infrastructure Design Suite Ultimate 2013 85994IDSU_2013_0F
Autodesk Infrastructure Map Server 2013 86014IMS_2013_0F
Autodesk Infrastructure Modeler 2013 86013INFMDR_2013_0F
Autodesk Inventor 2013 85998INVNTOR_2013_0F
Autodesk Inventor Factory Premium 2013 85999INVFPR_2013_0F
Autodesk Inventor Factory Ultimate 2013 86000INVFAD_2013_0F
Autodesk Inventor LT 2013 86004INVLT_2013_0F
Autodesk Inventor OEM 2013 86002INVOEM_2013_0F
Autodesk Inventor Professional 2013 86001INVPROSA_2013_0F
Autodesk Inventor Publisher 2013 85979INVPUB_2013_0F
Autodesk Maya 2013 85857MAYA_2013_0F
Autodesk Maya Entertainment Creation Suite Premium 2013 85928MYECSP_2013_0F
Autodesk Maya Entertainment Creation Suite Standard 2013 85930MYECS_2013_0F
Autodesk MotionBuilder 2013 85936MOBPRO_2013_0F
Autodesk Mudbox 2013 85869MBXPRO_2013_0F
Autodesk Navisworks Manage 2013 86022NAVMAN_2013_0F
Autodesk Navisworks Simulate 2013 86023NAVSIM_2013_0F
Autodesk Plant Design Suite Premium 2013 85995PDSPRM_2013_0F
Autodesk Plant Design Suite Standard 2013 85996PLTDSS_2013_0F
Autodesk Plant Design Suite Ultimate 2013 85997PDSADV_2013_0F
Autodesk Product Design Suite for Education 2013 85961ESME_2013_0F
Autodesk Product Design Suite Premium 2013 85962PDSP_2013_0F
Autodesk Product Design Suite Standard 2013 85964PDSS_2013_0F
Autodesk Product Design Suite Ultimate 2013 85963PDSU_2013_0F
Autodesk Quantity Takeoff 2013 86024AQTO_2013_0F
Autodesk Revit 2013 85950RVT_2013_0F
Autodesk Revit Architecture 2013 85862REVIT_2013_0F
Autodesk Revit Structure 2013 85866REVITST_2013_0F
Autodesk Robot Structural Analysis 2013 86005RSA_2013_0F
Autodesk Robot Structural Analysis Professional 2013 85975RSAPRO_2013_0F
Autodesk Showcase 2013 85956SHOWCASE_2013_0F
Autodesk Showcase Professional 2013 85949SHOWPRO_2013_0F
Autodesk Simulation CFD 2013 86025SCFD_2013_0F
Autodesk Simulation CFD 2013 Advanced 86028SCFDA_2013_0F
Autodesk Simulation CFD 2013 Connection for ACIS 86045SCACIS_2013_0F
Autodesk Simulation CFD 2013 Connection for NX 86030SCFDNX_2013_0F
Autodesk Simulation CFD 2013 Connection for Parasolid 86047SCFDP_2013_0F
Autodesk Simulation CFD 2013 Connection for Pro/E 86032SCPROE_2013_0F
Autodesk Simulation CFD 2013 Design Study Environment 86034SCDSE_2013_0F
Autodesk Simulation CFD 2013 Motion 86036SCFDM_2013_0F
Autodesk Simulation DFM 2013 86056SIMDFM_2013_0F
Autodesk Simulation Mechanical 2013 85940ASMES_2013_0F
Autodesk Simulation Moldflow Adviser Premium 2013 86006MFAM_2013_0F
Autodesk Simulation Moldflow Adviser Standard 2013 86008MFAD_2013_0F
Autodesk Simulation Moldflow Adviser Ultimate 2013 86007MFAA_2013_0F
Autodesk Simulation Moldflow CAD Doctor 2013 86009MFCD_2013_0F
Autodesk Simulation Moldflow Design Link 2013 86010MFDL_2013_0F
Autodesk Simulation Moldflow Insight Premium 2013 86038MFIP_2013_0F
Autodesk Simulation Moldflow Insight Standard 2013 86042MFIB_2013_0F
Autodesk Simulation Moldflow Insight Ultimate 2013 86040MFIA_2013_0F
Autodesk Simulation Moldflow Synergy 2013 86012MFS_2013_0F
Autodesk Simulation Multiphysics 2013 85942ASPRO_2013_0F
Autodesk SketchBook Designer 2013 85990ALSK_2013_0F
Autodesk Softimage 2013 85934SFTIM_2013_0F
Autodesk Softimage Entertainment Creation Suite Standard 2013 85932SIECS_2013_0F
mental ray Standalone 2013 86019MRSTND_2013_0F

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.


How do I know the FlexLM license manager port number ?

OpenLM employs the Flexnet / FlexLM reporting mechanism to monitor and optimize concurrent license usage, and obtain license statistics. The FlexLM license manager interfaces licensed applications via predefined ports. You can verify that a port number is set correctly by:

1. Using Flexera’s LMTOOL utility: Select the “Server Status” tab, and click the “Perform Status inquiry” button. the port number would appear on the line that begins with “License server status:” e.g.:

License server status: 27000@My_server

2. You can also find the server name and port number (If defined as static) directly in the license file, in the SERVER line e.g.:

SERVER <ServerName> <hostId> <PortNumber>

USE SERVER

The path and name of the license file is set in the LMTOOLS, under the “Config Services” tab.

FlexNet vulnerability: lmgrd Remote Code Execution

Zero Day has reported that a security vulnerability has been discovered in FlexNet License Server Manager installations. This vulnerability enables attackers to execute arbitrary code on remote FlexNet License Server managers. Authentication is not required to exploit this vulnerability. The flaw was reported by Luigi Auriemma and Alexander Gavrun.

The specific flaw exists within lmgrd license server manager. lmgrd listens by default on TCP port 27000. A specially crafted packet sent to the server will cause a stack overflow allowing for remote code execution under the context of the server.

Flexera Software has issued an update to correct this vulnerability and also provided license administrators best practices for mitigating risk exposure.

More details can be found at:

http://www.flexerasoftware.com/pl/13057.htm

Flexera FLEXnet license management implementation in ESRI ArcGIS 10

Licensing ArcGIS version 10

It is a common misconception that migrating to ArcGIS version 10 replaces the licensing software. This is incorrect; ESRI has only upgraded the old FLEXlm version to a newer one. The FLEXlm licensing software has gone through many changes during the passed several years, and is now called FLEXera FLEXnet for publishers. For every practical term – it is still the same good old FLEXlm software.

The main changes

The main changes that have been implemented in the ESRI ArcGIS licensing scheme include:

  • The FLEXlm (Flexnet) license management tool was upgraded from version 7.* to version 11.6.
  • The license file was replaced with trusted storage, in order to enhance security.
  • The FLEXlm LMTOOLS UI is not provided with the ESRI ArcGIS 10 package. ESRI provides it’s own management tools.
  • Borrowing licenses is made possible in ESRI ArcGIS 10.

Problems

Some problems have appeared in FlexLM reporting alongside these changes:

  • Due to the use of FLEXera trusted storage some imporant FLEXlm management tools are malfunctioning, for example, lmutil.
  • The FlexLM ‘lmremove’ utility has been omitted from the pool of license management commands. This is a known ESRI ArcGIS version 10 issue.
  • ArcGIS 10 monitors Borrowed licenses on its proprietary interface. The license output file tends to be inaccurate when it comes to reporting Borrowed licenses. The Identity of the users who borrowed licenses is also concealed from the output file.

Effect of these issues on OpenLM

These issues have imposed several limitations on the capabilities of OpenLM when interfacing ESRI ArcGIS 10.

  • Instead of the old ‘linger’ license output-file line, Borrowed licenses are marked with the “ACTIVATED LICENSE” line. These lines’ syntax excludes the identity of the user who borrowed the licenses.
  • The output-file lmutil lmstat information regarding license borrowing is inaccurate; “ACTIVATED LICENSE” lines are multiplied, effectively increasing the number of licenses reported as borrowed.
  • The absence of the “lmremove” utility implies that the ArcGIS license can not be removed, thus application the use of the “Suspend and Resume” method is not possible in OpenLM. Also, for the same reason, the “License removal” button in the “Active products” window is not functional.

The OpenLM Advantage

The OpenLM Active Agent may still “Save and Close” the ArcGIS 10 extension enabled application. This is regardless of the omission of the “lmremove” command. The closure process employs the applications’ own closure APIs, sent by the Active Agent, and applied by the OpenLM extension. Closing ArcGIS 10 may also be done via the “Close Application” button on EasyAdmin’s “Active Products” window.

This makes OpenLM the only solution for remotely saving & closing ArcGIS 10.

OpenLM Newsletter 2012 #01


Dear valued OpenLM users,

On this first edition of the OpenLM 2012 Newsletter I would like to greet you all, and wish you a happy and successful new year. 2011 has been very good for us here at OpenLM, all thanks to your support. Our team has grown bigger, and is now able to provide better support to our improved product.

We are proud to introduce the OpenLM Mobile touch interface. This interface may run on any mobile device operating system; e.g.: IOs, Android, Blackberry, Windows Mobile etc. With the help of some of our faithful customers, we have managed to perform a successful Beta trial for this interface. The OpenLM Mobile Touch interface is available to all customers under a valid maintenance agreement with no additional cost.

Based upon requests from our customers, and following Dassault Systemes migration from IBM-LUM to their proprietary DSLS license manager, OpenLM has quickly adapted to provide support to DSLS. We look forward to receiving further customer requests, in order to meet our users’ needs.

We have recently launched a new and enhanced company website. This site is clearer, more informative, useful and generally – nicer than our old one. Among other things, It features a new introductory animated video on OpenLM. We hope that you will like it.

Best Regards,

Oren Gabay, CEO


OpenLM updates

OpenLM goes mobile !

 

The OpenLM EasyAdmin Mobile application enables system administrators to keep track of the license management systems, while being out of office. This document describes the essentials of the OpenLM EasyAdmin for mobile application; installing the application, and running it on a Mobile set.Read more…

 

OpenLM Live Webinars

OpenLM is now hosting a couple of Online Webex Webinars each week. This Webinars give an overview of the OpenLM system; its components and capabilities, and is intended for newbies as well as for experienced users. Please check out the date for the next webex Webinar on OpenLM’s site.


OpenLM resources

OpenLM introductory video

 

 

 

 

 

OpenLM Video tutorials: OpenLM server configuration – License server tab

 

 

 

 

 

 

OpenLM Video tutorials: Active Directory Synchronization

 

 

 

 

 

 


Monthly Articles

Get more out of your floating licenses

Being this our first edition of the OpenLM Newsletter for 2012, We found it adequate to give a brief summary of what the OpenLM utilizer actually is. This is good reading material for Newbees, and nice to remember for more experienced users. Read more…

OpenLM system structure

Another important article for first timers, this one elaborates all about the OpenLM system structure; Where should every module be installed, and what are the interconnections between them. Read more…

Products and Packaged licenses in OpenLMs EasyAdmin web application

This Article deals with two adjacent subjects: Renaming features as products, and gathering these features into licensed packages in the OpenLM EasyAdmin web application. Read more…

Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

FLEXlm (Flexera FLEXnet) 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 files setting.

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


 

Points of interest

IBM Rational – FlexNet Token based licensing:

The IBM Rational License Server uses FLEXnet for licensing IBM Rational products. This article presents the main characteristics of FlexNet Token based licensing, and the benefits of this method. Read more…

Autodesk cascade licensing and the PLIST

Cascade Licensing allows a product to obtain a license from a network license manager pool when that license manager is servicing more than one product. Cascading was implemented primarily to address mixed-product environments where both suite and base products co-exist.

Read more…

FlexNet Producer Suite Is Distinguished by the Frost & Sullivan 2011 Market Share Leadership Award for Software-Enforced License Management

The Frost & Sullivan Award for Market Share Leadership is presented to the company that has demonstrated excellence in capturing the highest market share within a segment of its industry. Read more…