The OpenLM Java Agent is an end-user tool that enables OpenLM to interact with the end user in order to promote license availability. System administrators are granted full control over any functions available to the end user.
The OpenLM Java Agent is a “lightweight” software component. It is apparent on screen as an icon, located on the end users “System tray bar”. The Java Agent facilitates the following abilities:
Query license availability, license users and full users details.
Receive license availability notifications.
Report any active projects.
This article elaborates the installation process of the Java Agent.
The OpenLM Java Agent can run on any Java supported system. It is primarily intended for UNIX or Linux OS. OpenLM provides a native Windows agent recommended for a Windows environment.
It is necessary to have the Java Runtime Environment (JRE) version 1.6 (or newer) installed.
1. Unzip the Openlm Java Agent zip file and copy all files from the Agent directory to a folder.
Ensure that the target folder does not have “read only” permissions.
2. Run the software using a terminal on the Unix \ Linux workstation:
cd to the target folder, and run the command:
java -jar openlm_agent.jar &
If the following message appears, make sure that the Java software is in the system path or uses full path.
The OpenLM Agent icon appears on the “system tray”.
OpenLM Agent in a connected state:
OpenLM Agent in a disconnected state:
The OpenLM Agent may be set to start with your system; this setting is available in all UNIX/Linux systems.
Right click on the agent icon and select ‘OpenLM Agent Configuration’. The Agent configuration window opens.
Click the “Check connectivity to OpenLM server” button.
Logger Configuration File: Type in the location of the Agent Log File.
Logging Level: Adjust the Agent’s logging level.
Skip Double Instances Alert: This option either enables or blocks alerts when trying to open two agent sessions simultaneously. This option is set active by default.
Use Local Computer’s Proxy Settings: This setting may solve issues that originate using a proxy server. This option is set inactive by default.
Shut Agent when products Are inactive… : These parameters are relevant for VM servers. When OpenLM closes a licensed application, the VM (e.g: Citrix) is kept in use by the workstation, unnecessarily consuming a license. This configuration shuts down the OpenLM Agent after INACTIVITY_TIME, thus releasing the VM license.
The OpenLM Java Agent window
The OpenLM Java Agent window shows the Feature usage status, per Server, Vendor and User name. Individual user data is also available through the Agent; Mark a chart line and click the “Show Users” button to get more information on the user who is currently using the license. (See license usage information below)
ESRI has announced the release of ArcGIS 10 Service Pack 4. The new service pack is now available for download from ESRI’s patches and Service Packs download site. Download and installation of the new service pack is straightforward, and the software update runs seamlessly.
As far as OpenLM is concerned, Service Pack 4 does not incorporate fixes to the ArcGIS License Manager. Hence, transition to the new Service Pack should be transparent to OpenLM as a monitoring tool of floating licenses.
Please note that previous Service packs have included fixes to the ArcGIS License Manager. Here is a full list of the issues that were addressed and solved in ArcGIS 10 Service Pack 4, as well as in previous Service Packs.
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.
Version 184.108.40.206 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We recommend that users to whom these problems may be relevant to upgrade their system to this version.
In order to upgrade to version 220.127.116.11:
Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
Stop the OpenLM Server service
Make sure ALL windows are closed; especially the services window.
Install the new version on top of the existing one.
What’s new in version 18.104.22.168 ?
Changes made to the Readme text, apparent during the OpenLM Server installation.
EasyAdmin: Fixed User Details for user names with special characters.
Mobile: The OpenLM EasyAdmin Mobile application has been added to the installation files. The Mobile application enables system administrators to keep track of the license management systems, while being out of office.
Working days computing error was fixed.
EasyAdmin: Color selection problem on report charts was fixed.
HASP: Errors in reading certain formats of the HASP license output files were fixed.
Tesera Systems – a customer of OpenLM has implemented an advanced cloud based computing & licensing system. FLEXlm (FLEXnet) licensed software such an ESRI Desktop software (ArcInfo, ArcEditor & ArcView) and Safe FME software is used by cloud instances or end user workstations over the cloud. The licensing system is managed and enhanced by OpenLM software ensuring the high availability and effective usage of licenses.
Tesera Systems is an employee-owned company that provides a wide range of quality services related to resource planning, analysis, information systems and environmental management. Our innovative IT and collaboration and infrastructure allow us to effectively manage and operate high performing distributed teams (required to provide the best solution). Tesera has branch offices throughout western Canada, specifically: Victoria, Penticton, and Prince George (British Columbia) and Cochrane, and Calgary (Alberta). Tesera’s staff have access to virtual desktops and secure, redundant and centralized data storage allowing them to operate as though they were in the office regardless of where they work from.
Requirements: There are certain pre-requisites or requirements which must be fulfilled before upgrading the Autodesk Network License Manager to IPv6 version support.
You must have Autodesk Network License Manger already installed on your server before applying IPv6 support update.
So, make it sure that installed software is working good otherwise install a new one by referring Network Licensing Guide which is available in Help System.
The server must be stopped before carrying out software update or any other administratively critical maintenance activity on Network License Manger server; server should be restarted after the successful completion of activity.
You must be logged into the system with administrator rights for stopping, updating and restarting the services on the server.
Limitations: Though this update is very excellent tool but it has following limitations which should be considered while deciding or working with Autodesk Network License Manger.
It supports the operating system with 64-bit configuration; supported Operating systems are Microsoft® Windows® Server 2008 and 2008 R2 64-bit, Windows Vista® 64-bit and Windows7 64-bit.
This supports either a mixed environment of IPv4/IPv6 or IPv6-only.
This implementation does not support IPv4 –only environment.
Updating procedure: You must make it sure that all the requirements are fulfilled for upgrade activity. Now follow the step by step task given below for updating the Autodesk Network License Manger for IPv6 support.
Download NLM_IPv6Support_Win64.exe file and save on the desk top of the server.
One the desktop of the server, right click on LMTOOLS.exe and choose Run as Administrator; the LMTOOLS program will start.
On LMTOOLS select ‘start/stop/reread’ tab and choose stop server and wait for 15 seconds, then close the LMTOOLS program. Your server has stopped now.
The default location of Autodesk Network License Manager is C:\Program Files\Autodesk Network License Manager; you have to locate lmtools.exe, lmutil.exe, lmgrd.exe, and adskflex.exe files to take the backup of Autodesk Network License Manager Files.
After taking the backup of above mentioned files, double click the downloaded file NLM_IPv6Support_Win64.exe placed on the desktop of the server.
The NLM_IPv6Support_Win64.exe file will be extracted automatically on ‘C:\install\Autodesk\NLMIPv6Support_Win64’ location; extracted updated files are lmtools.exe, lmtools.exe, lmutil.exe, lmgrd.exe, and adskflex.exe.
Copy all above mentioned updated files and paste them into existing Autodesk Network License Manager Folder whose default location is C:\Program Files\Autodesk Network License Manager\.
System will prompt for replacing the existing file; click yes to confirm.
Right click again on LMTOOLS.exe available at desktop and choose run as Administrator.
On LMTOOLS program click Start/Stop/Reread tab and choose start server tab; this will restart your server with updated support to IPv6 on 64-bit windows operating systems.