- 1. Installation
- 2. Configuring the Applications Manager
The 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 Workstation 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.
OpenLM Applications Manager workflow.
1. Installation #
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.
1.1. System Requirements #
- Java 11*
- 64-bit OS
- Working install of OpenLM Server v21.7 or higher
- Working install of OpenLM Broker
* 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.
1.2. Unix / Linux Installation #
Preliminary steps #
1. Download the latest version of the Application Manager for Unix/Linux from the OpenLM website downloads section.
2. Extract the archive (OpenLM_AppManager_#.#.#.#.tar.gz) to a convenient location.
3. Open the settings.sh file in your editor of choice. This file holds all the variables required for AppManager to operate. It is mandatory to modify the JAVA_HOME variable so that it points to the path of your JDK 11 install.
The JAVA_HOME path must not end with a trailing slash.
Optionally, you can also edit the APPMANGERSRVNAMEUSER variable in case you need to launch the service from an account that is different from “root”. In this case, you must ensure that all the files in the “OpenLM_AppManager_X.X.X.X” folder have their ownership reassigned to the new user.
4. Save the file and continue following the installation steps below, depending on your Linux distribution.
Installing AppManager as a service #
If your Linux version supports systemd, the following steps will install OpenLM AppManager as a service which starts automatically on system start up:
1. Install the AppManager as a service:
sudo ./appmanager.sh install
2. Test the status of the AppManager service:
sudo ./appmanager.sh status
3. Run the AppManager detection script. Alternatively, if your Linux install has a desktop user interface, you can run the GUI AppManager Configuration tool with:
sudo ./appmanager.sh config
Running AppManager as a background process #
If your Linux version does not support systemd, the following steps will run OpenLM AppManager as a background process instead:
1. Run the AppManager process with:
To open the AppManger configuration screen:
1.3. Windows Installation #
- Obtain the latest Windows installer from our Downloads page.
- Double-click the OpenLM Applications Manager installation file to launch the installation wizard.
Figure 1: The Applications Manager Setup wizard.
- Click Next and the License agreement screen will appear
- Read the license agreement, then check the “I Accept the Terms of the License Agreement” box.
Figure 2: The License Agreement screen.
- Click Next to advance to the Java Selection Screen. You have two options:
- Install Application Manager with Java OpenJDK
- If you already have it installed, browse to the path where it is installed:
Figure 3: The Java Selection screen.
- Click Next to accept the configuration and advance to the “Install Location” screen.
Figure 4: The “Choose Install Location” screen.
- Select the installation path. The default is: C:\Program Files\OpenLM\OpenLM App Manager\
- Provide the OpenLM Server hostname and listener port – default port is 5015:
Figure 5: The Installation Completed screen.
- After installation is complete, click Next then Finishto complete the installation:
Figure 6: The completion screen.
1.4. 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.
Figure 7: The “Java” tab in the OpenLM App Manager Config tool.
- Uncheck the “Use default” box.
- Click on the … box near the “Java Virtual Machine” field.
- Browse to the location of your sqljdbc_auth.dll file. (e.g., on a typical JDK11 installation, this is located at C:\Program Files\OpenLM\OpenLM Applications Manager\bin)
- Click Open then 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.
- Once the service has started, you can close the Services window.
2. 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 Workstation Agent. This section will show you how to configure each of these components separately.
2.1. 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 the 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. Go to License Managers Tab → ADD.
- Click Detect This will populate the options with detected configurations or it will use defaults. The Applications Manager license server and additional nodes will be added to the navigation panel.
Figure 8: The OpenLM Broker Configuration Tool and the “Detect” function.
- 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.
|LM Type||OpenLM App Manager|
|Hostname \ IP||Localhost|
|Log File||C:\Program Files\OpenLM\OpenLM App Manager\logs\lm-log.log|
Table 1: OpenLM Broker defaults for the Applications Manager
Click SAVE to commit the changes.
- Open the EasyAdmin User Interface of the Server and Open the License Servers window. Go to Start → Widgets → License Servers.
Figure 9: EasyAdmin User InterfaceLicense Servers screen.
- If the Broker has detected and added your Applications Manager, you should the AppManager with Pending Status as depicted in the screenshot above. Double click then select the timezone and click Approve.
2.2. OpenLM Workstation Agent Configuration for Applications Manager #
To enable the OpenLM Workstation Agent to intervene in software licensing distribution via the Applications Manager it must be configured in the Workstation Agent. This can be done in two ways: before or after the Workstation Agent.
- While installing the Workstation Agent one of the prompts will ask whether or not you are using the App Manager. Check the Use Applications Manager box, and provide its host and port as depicted below:
Figure 10: The OpenLM Workstation Agent installation promt with Applications Manager settings
- For the full Workstation Agent installation guide, follow this link
- 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 is set correctly, and lastly, that your license file has support for the Applications Manager extension. If the problem persists, please contact OpenLM support (email@example.com)
- Click the Apply button. This will accept the changes and close the Agent Configuration screen.
At this point configuration is complete.
See this document for more in-depth information.