OpenLM Applications Manager provides a solution for intervening in excessive license consumption and avoiding unplanned license expenditure or breach of license compliance.
The Applications Manager is a Java application that acts as a hub for all OpenLM Agents. The OpenLM Server queries the Broker component, which in turn queries the Application Manager to obtain usage data. Because of this, the Broker component is mandatory and must be installed on the same machine as the Applications Manager.
This document covers:
- Installing the OpenLM Applications Manager on Linux/Unix and Windows
- Upgrading an existing installation
- Configuring the OpenLM Applications Manager
The OpenLM Applications Manager is implemented in Java so it can be installed on any machine that supports it. Both Windows and Unix / Linux installations are covered in this section.
- Java 11*
- 64-bit OS
- Working install of OpenLM Server v4.5
- Working install of OpenLM Broker v4.5
* Java 11 is optionally bundled with the Applications Manager installer so no additional download is required.
For the most optimal hardware configuration depending on your organization’s needs, please consult the Applications Manager hardware guide.
Unix / Linux Installation
The Linux package is delivered as a zip file (e.g. openlm-app-manager-#.#.##-bin.zip). The installation process requires extracting files, editing certain configuration files and setting appropriate permissions for the scripts.
- Obtain the latest Linux binaries from our Downloads page.
- Once the download has finished, unpack the zip file to a convenient location.
- Revise the openlm-app-manager.properties configuration file before running the binaries. When editing, please note the following variables:
- Define the OpenLM server hostname or IP in the openlm.server.host (mandatory)
- Define the openlm.server.user and openlm.server.password (if using admin login on the OpenLM Server)
- Modify run.sh as needed to restart the Applications Manager via init.d or systemd
- Grant run.sh the executable attribute with
chmod +x run.sh
- Execute run.sh to start the Applications Manager
- Obtain the latest Windows installer from our Downloads page.
- Double-click the OpenLM Applications Manager installation file to launch the installation wizard (see Figure 2).
- Click [Next] and the License agreement screen will appear (see Figure 3).
- Read the license agreement, then check the “I Accept the Terms of the License Agreement” box.
- Click [Next] to advance to the Service Configuration screen (see Figure 4).
- Check the Host (default: localhost) and Port (default: 7014) to make sure that they reflect the details of your OpenLM Server installation. Fill in the User and Password fields if you have set up admin login for OpenLM Server.
- Click [Next] to accept the configuration and advance to the “Install Location” screen.
- Check the installation path. The default is: C:\Program Files\OpenLM\OpenLM App Manager\
- Click [Next] to advance to the Choose Components screen (see Figure 6).
- [Optional] All boxes on the Choose Components screen should be checked by default. If you prefer to use a different Java installation from the one that comes bundled with the installer, uncheck the JRE box. Doing so will produce a warning when the installation continues (see Figure 7). You will need to configure it later on manually using the instructions provided in the “Using an external JRE installation” section below.
- Click [Install] to begin the installation. A progress screen will appear (see Figure 8).
- After installation is complete, click [Next] then [Finish] to complete the installation.
Using an external JRE installation
If you have chosen to use an external JRE installation instead of the one bundled with the Applications Manager installer, you will need to follow additional steps to get the “OpenLM App Manager” service to work. Please make sure that your Java installation is at least version 11 as per the listed system requirements. To configure an external JRE with the Applications Manager:
- Locate your Applications Manager installation and open the bin folder (by default, the full path is C:\Program Files\OpenLM\OpenLM App Manager\bin).
- Double-click on OpenLMLicenseManager.exe.
- Select the Java tab.
- Uncheck the “Use default” box.
- Click on the […] box near the “Java Virtual Machine” field.
- Browse to the location of your jvm.dll file. (e.g., on a typical JDK11 installation, this is located at C:\Program Files\Java\jdk-11.0.3\bin\server)
- Click OK.
- Open the Windows Services screen (open a Run dialog by pressing Windows + R, type services.msc and click OK)
- Locate the “OpenLM App Manager” service and select it.
- Click on “Start” in the top-left corner (see Figure 12)
- Once the service has started, you can close the Services window.
Prior to version 2.0 of the Applications Manager, a separate procedure and license file were required to activate it. The newer versions have removed this limitation as the Applications Manager will now automatically retrieve its license status from the OpenLM Server license file which has the appropriate extension (as long as your license type includes it). If you’re unsure or you cannot access the Applications Manager through the EasyAdmin UI (Start → Administration → OpenLM Applications Manager), please contact email@example.com so we can assist you.
Upgrading an existing Applications Manager installation
If you’re running an older version of the Applications Manager, you can easily upgrade to the latest version. To do so:
- Obtain the latest Windows installer from our Downloads page.
- Double-click the installation file to launch the installation wizard.
- The installer should automatically detect if there is a previous version of the Applications Manager present and prompt a dialog (Figure 13). Click [OK] to begin.
- The upgrade process and installation screens are virtually identical to the Installation process so please refer to the Install section above.
Please note that if you’re upgrading the Applications Manager from versions older than 2.0, the upgrade location will coincide with the original installation folder that is in the Program Files(x86) folder. This is only mandatory for upgrades. New installations will always opt for the default Program Files/OpenLM/OpenLM App Manager/ folder as the Applications Manager is 64-bit only now.
Configuring the Applications Manager
To run properly, the Applications Manager requires configuration of the various components that it interacts with. These include the OpenLM Server, OpenLM Broker and OpenLM Agent. This section will show you how to configure each of these components separately.
OpenLM Broker Configuration for Applications Manager
The OpenLM Broker facilitates the connection to the OpenLM Server. Once the Broker has been configured to interface with the Applications Manager, the settings will be passed along to the Server. For this reason, we recommend that configuration of the Applications Manager be done through the Broker first.
The Detect feature can be used to automatically detect license manager information and simplify OpenLM Broker configuration. The function will add information for new ports (e.g., commands and paths) depending on what is detected.
- Open the OpenLM Broker Configuration tool. Go to [Start] > [OpenLM] > [OpenLM Broker Configuration Tool].
- Click [Detect] on the bottom of the OpenLM Broker Configuration Tool screen. This will populate the Command options with detected configurations or it will use defaults. The Applications Manager license server and additional nodes will be added to the navigation tree in the navigation panel.
- Review the auto-detected license managers to make sure the information corresponds to your installation. These items include the Applications Manager Host Name \ IP (License Server node), Port number and License Manager Type (Port node), command line paths to ‘status’ (Commands > Status node) and ‘data_inquiry’ (Commands > data_inquiry node), and log file path (Log Files node). See the defaults listed in Table 1.
Item Default Hostname \ IP localhost Port Number 27080 License Server Type OpenLM App Manager Status C:\Program Files\OpenLM\OpenLM App Manager\lmstat.bat. [NOTE: Linux configurations should point to the lmstat.sh file.] Data_Inquiry C:\Program Files\OpenLM\OpenLM App Manager\lmstat.bat [NOTE: Linux configurations should point to the lmstat.sh file.] Log File C:\Program Files\OpenLM\OpenLM App Manager\logs\lm-log.log
Table 1: OpenLM Broker defaults for the Applications Manager
Click [Apply] to commit the changes.
- Click [Restart Broker] button to restart the Broker and make the changes live. A confirmation screen will appear. Click [OK] to close it.
- Click [Exit] to close the OpenLM Broker Configuration Tool screen. A confirmation dialog will appear. Click [Yes] to close the confirmation and exit the tool.
- Open the EasyAdmin UI of the Server by either going to http://localhost:7019/ (if you’re currently on the OpenLM Server) or the http://<OpenLM Server IP or hostname>:7019/ if accessing through any other location.
- Open the License Servers window. Go to Start → Widgets → License Servers (see Figure 15)
- If the Broker has detected and added your Applications Manager, you should now see a red row with its details. Hover over it and click on [Approve] to finalize configuration.
OpenLM Server Configuration for Applications Manager
If you have followed the previous section and successfully configured the Broker to interface with the Applications Manager, you can skip this step because the Broker will have automatically passed the configuration details to the Server as well. However, if for some reason you cannot use EasyAdmin or you prefer to use the standalone Server Config Tool instead, here are the steps for configuring the Server with Applications Manager:
- Launch the OpenLM Server Options tool ([Start] → [OpenLM] → [OpenLM Server]).
- Click “Add” then choose OpenLM App Manager for the license manager type from the drop-down list.
- Enter a descriptive name for the license manager in the Description field.
- Choose the timezone of the Applications Manager server from the drop-down list.
- Enter the Applications Manager’s address (IP or hostname) in the Hostname field.
- Enter the Applications Manager’s port number in the Port field (e.g., default 27080). See Figure 16 for a complete setup.
- Click [Apply] to accept the changes.
- Click [Close] to exit the OpenLM Server Options tool.
OpenLM Agent Configuration for Applications Manager
To enable the OpenLM Agent to intervene in software licensing distribution via the Applications Manager it must be configured in the Agent Configuration interface. For additional information about configuring OpenLM Agent, please see OpenLM Agent End User Interface guide.
- Open the OpenLM Agent Configuration screen. Click on the [Show Hidden Icons] arrow in the tray → right-click the OpenLM Agent icon → [OpenLM Agent Configuration] (see Figure 17). The Agent Configuration screen will open displaying the General tab (see Figure 18)
- Click the OpenLM Applications Manager tab (see Figure 19). Defaults will be displayed as per Table 2.
Item Default Enable (checkbox) Checked OpenLM Applications Manager Server localhost Port 27080
Table 2: Default values for OpenLM Applications Manager in OpenLM Agent Configuration.
- [Recommended] If not already set, change the Applications Manager server address to the actual hostname or IP address where it is installed.
- Check the connectivity to the OpenLM License Manager by clicking the [Check Connectivity Status] button. This should return a success screen. If it returns a failure, check to see that the Applications Manager service is running, that the configuration for the Port and License Server in the Broker are set correctly and lastly, that your license file has support for the Applications Manager extension. If the problem persists, please contact OpenLM support (firstname.lastname@example.org)
- Click the [Apply] button. This will accept the changes and close the Agent Configuration screen.
At this point configuration is complete. Additional information on monitoring licenses can be found in the EasyAdmin Web App documentation.