End Google Tag Manager (noscript) -->
USA +1 866 806 2068 | UK +44 203 1292 513 | JAPAN +81 3 45208991 担当:萩原 info@openlm.com

Downloading files from, and uploading files to the license server machine – AN4057

General

The OpenLM EasyAdmin web application enables users to access text files located on remote License Server machine. This includes:

  • Fetching the said text files onto the local machine on which the EasyAdmin web application is running, and
  • Editing and uploading FlexLM license files onto the license server machine, followed by an invocation of a license server ‘re-read’ or ‘restart’ action.

These capabilities have been proven useful in environments of restricted access, where OpenLM users are separated from license administration capabilities.

Supported file formats

The OpenLM Broker is installed on the license server machine. It is configured to interface specific files, relevant for different aspects of license management and monitoring. At the time of writing this document, These files include:

  • FlexLM License server log files
  • DSLS License server log files
  • LM-X License server log files
  • Reprise RLM License server log files
  • FlexLM License files
  • FlexLM Options files
  • FlexLM – ArcGIS Audit log files
  • Reprise RLM License files

File fetching mechanism

EasyAdmin users can configure the OpenLM Server to issue a file fetching request to the OpenLM Broker. The OpenLM Broker will respond with the required text file content, and the EasyAdmin web application will enable downloading it onto the local web-browser machine. See the image below for clarification.

 

Interface

The Start → Widgets → “License servers” window displays the files visible by the Openlm Broker. Click the ‘Files’ hyperlink, and select a file to download. The image below demonstrates downloading an options file for Solidworks:

 

Configuration

The URL and physical location to which the file will be downloaded are set in the EasyAdmin Start → Administrator → “File fetching” window:

 

 

Changing one of the fields;  “File fetching URL” configuration or physical location (“Download directory”) will require a respective change in the other field. These fields are interconnected.

LightTPD

When using the default LightTPD web server, these fields are connected in the lightTpd configuration file, normally located at:

C:\Program Files (x86)\OpenLM\OpenLM Server\WebServer\LightTPD\conf\lighttpd.conf

The default string relating the Physical location with the URL address is:

alias.url = ( “/openlm_downloads” => “C:\ProgramData\\OpenLM\\Downloads” )

IIS

When using the IIS web server, the linkage between the URL line and the physical directory is done explicitly.

Outcome

After clicking the ‘Download’ button, the user will be presented with the download URL, and will be prompted to download the file to a physical location. This is presented in the image below.

FlexLM License file upload

As mentioned above, OpenLM enables administrators to edit and override FlexLM license files onto the remote FlexLM license server machine.

License file upload mechanism

In this configuration, the OpenLM Server will upload the required file through its communication channel with the Broker to the license server machine. The OpenLM Broker will override the existing license file with the new edition, and invoke either a license server ‘Restart’ or ‘Re-Read’ action, for the change to take effect. Please refer to the image below for clarification.

18

Interface

The Start → Widgets → “License servers” window displays the files visible by the Openlm Broker.

  • Click the ‘Files’ hyperlink, to present the “Files on Server” window.
  • Select a specific license file to upload, as shown in the image below.

6

  • Select new license file edition to be uploaded
  • Select whether to invoke a “Re-Read” or ‘Restart’ action on the remote license server.

And that’s it – the new license file is on its way to the license server machine.

Outcome

After applying the license file upload and the subsequent re-read or restart actions the license manager will relate to the new license file. The execution of the said re-read or restart actions will be evident in the license manager’s debug log file.