Upcoming Webinar: Register now >>

Trouble Shoot Form: Broker Item 002 (Broker commands not showing)

Subscribe to our blog

Loading

Trouble Shoot form: Item 01.002

Title Broker commands not showing.
Category Broker
Date Oct 11, 2011
Handled by
Relevant Links
Symptoms
Applies to license managers FLEXlm, FLEXera FLEXnet publisher, IBM LUM, LM-X
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process Troubleshooting
Solution

General

Upon start-up, the OpenLM Broker compiles lmutil commands that are installation specific. These commands would later be used for interfacing the license server, and sending information over to the OpenLM server. These commands are โ€˜Statusโ€™, โ€˜Data inquiryโ€™, โ€˜Startโ€™, โ€˜Stopโ€™ and โ€˜Rereadโ€™. In the image below, The command set of two license servers are highlighted, and the โ€˜Statusโ€™ command respective to the ArcGIS License manager is shown.

The Broker has the capability of self extracting information regarding the License Serverโ€™s port, and the location of the License file and lmutil executables in order to compile the commands. At the time of writing this document, This capability is only available for Windowsโ€™ license servers (OpenLM Broker version 1.7xx).

Symptom

The Command lines are blank

Troubleshooting

  1. Unix servers: As mentioned above, auto compiling of lmutil commands is only available on Windows servers. Solution:
    1. Add a Windows License server and get the commands there.
    2. Modify the commands so that they comply with the Unix format.
    3. Following are the commands as they appear on my Windows Broker (as an example), followed by the respective Unix command templates:

Status:

Windows: “C:PROGRA~2ESRILicensearcgis9xlmutil” lmstat -c 27004@olm2008

Unix: <installationFolder>/lmutil lmstat -c <port>@licenseServerName

Data inquiry:

Windows: “C:PROGRA~2ESRILicensearcgis9xlmutil” lmstat -a -c 7004@olm2008 -i

Unix: <installationFolder>/lmutil lmstat -a -c <port>@licenseServerName -i

Start:

Windows: “C:PROGRA~2ESRILicensearcgis9xlmgrd” -z -c “C:Program Files (x86)ESRILicensearcgis9xViewer9.lic”

Unix: <installationFolder>/lmgrd -z -c <license file>

Stop:

Windows: “C:PROGRA~2ESRILicensearcgis9xlmutil” lmdown -q -c ย “C:Program Files (x86)ESRILicensearcgis9xViewer9.lic”

Unix: <installationFolder>/lmdown -q -c <license file>

Reread:

Windows: “C:PROGRA~2ESRILicensearcgis9xlmutil” lmreread -c ย “C:Program Files (x86)ESRILicensearcgis9xViewer9.lic” -all

Unix: <installationFolder>/lmreread -c <license file> -all

  1. The automatic detection capability is only applied when a license manager is installed on the same machine as the OpenLM Broker. If no such installation is noted in the registry, no Broker commands would be automatically compiled.
  2. In the OpenLM Brokerโ€™s installation folder, under the โ€˜toolsโ€™ directory (i.e.: C:Program FilesOpenLMOpenLM Brokertools) there is a default lmutil executable file. This file is referred to when no other lmutil executable file is set. Note its existence in order to avoid problems arising from multiple code reference.
  3. View the Broker.xml file under the Brokerโ€™s installation folder ( i.e.: C:Program FilesOpenLMOpenLM Broker) in order to extract information regarding the Brokerโ€™s whereabouts. See the following code cut-out as a reference to the required Brokerโ€™s behavior
Skip to content