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:

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.

Please follow and like us:

Automatically Release “Orphan” ArcGIS and Autodesk licenses

Users of network licensed ESRI ArcGIS and Autodesk (AutoCAD) applications report cases in which licensed application were closed, but the licenses remained “hanging”, and were not returned to the license pool.

This condition may be caused by broken communication between the FlexLM license server and the workstation on which the application is running, or any other “glitch” for that matter. The answer given by the vendors to this condition is that the system administrator should manually release the checked-out license via the license administrator tool or Flexera’s LMTOOLS UI.

But this is wrong.

This problem does not manifest in any apparent error message or visible notification, so this condition may persist indefinitely. Because of that:

  • There is no way for manually and routinely tracking down and fixing this condition. This condition is only captured when there is an obvious “leak” in the amount of available licenses.
  • On top of not being able to utilize the full extent of the acquired software licenses, this condition may also cause exaggerated billing for users.

An automatic solution for the identifying and fixing this condition is therefore required, and is supplied by OpenLM. On the OpenLM EasyAdmin web application, there is a check box which is configured to do just that. It configures the OpenLM system to track down ArcGIS and Autodesk applications’ licenses which are checked out but not used, and retrieve them.

This option is set active by default. The configuration check box is found as follows:

  • Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.
  • Select the “Active Agent” icon. The “Active Agent” window opens.
  • Select the “Extension dedicated” tab, and check the “Solve license manager errors” box.

That’s it. You wouldn’t have to worry about hanging “Orphaned” licenses for ArcGIS and Autodesk applications any more.

 

Please follow and like us:

FAQ: Flexera lmgrd log file is very big


The lmgrd log file collects all license check out / check in activity. This log would continue to increase in size and as long as the licensed service is running.

The log is cleared when the licensed service is restarted.
This can be done via Flexera’s LMTOOLS UI.

On The “Services/License File” tab choose the licensed service. e.g.: Autocad.

On the “Config Services” tab – you can view the log (e.g: Autocad.log) and its path.

On the “Start/Stop/Reread” tab, use the marked buttons. This would clear the service log file (Autocad.log) and restart logging.

One of the advantages of the OpenLM system is that the accumulation of large amounts of data in this log file is made redundant. The OpenLM Broker is a component in OpenLM’s system which reads the licensed log file, and reports its content to the OpenLM server. There this information is processed and exhibited in a clear and negotiable manner.

 

 

Please follow and like us:

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.

Please follow and like us: