Upcoming Webinar: Register now >>

15th

January

2025

Must-attend SAM event of the year

15th

January

2025

Must-attend SAM event of the year

Application Note 1034: Migrating OpenLM to a new Server

Subscribe to our blog

Loading

General

OpenLM gathers license statistics information from a variety of license managers, such as Flexnet publisher (FlexLM), RMS, RLM, DSLS, HASP, IBM LUM, and LM-X.

Users often require a procedure to migrate OpenLM to a new computer, and maintain the license usage information that has been gathered during a long period of time. This migration may be accompanied with an OpenLM release version migration (i.e. 1.6XX to 1.7XX), or not. This article provides the required procedure for both cases,

Migrating between servers, maintaining OpenLM version 1.7.X.X

1. Stop the OpenLM server service on the old server.

2. Save a backup of the entire OpenLM server directory:
C:Program FilesOpenLMOpenLM Server to a safe place.

3. Download and install the latest OpenLM server version 1.7 from the OpenLM site on the new server.
This would create a new empty database in the
C:Program FilesOpenLMOpenLM Serverdb directory.

4. Towards the end of the installation, the OpenLM server configuration window opens. Close this window, and finalize the installation process.

5. Stop the OpenLM service on the new server.

6. Copy the OpenLM database from the old server,
C:Program FilesOpenLMOpenLM Serverdb
directory, and replace the empty database in the new server.

7. Restart the OpenLM server service on the new server.
Now you’re done with the OpenLM server migration, and need to configure OpenLM peripherals to point to the new OpenLM server.

8. OpenLM Broker: Upgrade the OpenLM Brokers installed on the License server machines. Configure the brokers to point to the new OpenLM server machine.
Please refer to this application note. Observe the “OPENLM SERVERS – CONFIGURING THE SERVER” paragraph.

9. Update the OpenLM Agent version (Utilizer Agent or Active Agent, depending on what you’ve acquired).
In case you are applying silent OpenLM Agent installation to all workstations, please refer to this guide. You would need the Agents to point to the new OpenLM Server, so select the ‘SERVER NAME’ parameter accordingly.
In case of a single Agent installation – set the OpenLm server name in the Agent configuration window (‘support1’ in the image below).

Migrate from 1.6.X.X to 1.7.X.X on a new server

1. Stop the OpenLM server service on the old server.

2. Save a backup of the entire OpenLM server directory:
C:Program FilesOpenLMOpenLM Server to a safe place.

3. Upgrade the OpenLM server on the old machine to OpenLM v 1.7. Use this Application note, and make sure to backup your database directory first. At the end of this process, the OpenLM database would migrate to the new 1.7 version format.

4. Install the new OpenLM server version 1.7 from the OpenLM site on the new server.
This would create a new empty database in the
C:Program FilesOpenLMOpenLM Serverdb directory.

5. Towards the end of the installation, the OpenLM server configuration window opens. Close this window, and finalize the installation process.

6. Stop the OpenLM Server service on the new server.

7. Copy the migrated database from the old server,
C:Program FilesOpenLMOpenLM Serverdb
directory, and replace the empty database in the new server.

8. Restart the OpenLM server service on the new server. Now you’re done with the OpenLM server migration, and need to configure OpenLM peripherals to point to the new OpenLM server.

9. Upgrade the OpenLM Brokers installed on the License server machines.
Please refer to this application note.

10. Finally – Update the OpenLM Agent version (Utilizer Agent or Active Agent, depending on what you’re acquired). In case you are applying silent OpenLM Agent installation to all workstations, please refer to this guide. You would need the Agents to point to the new OpenLM Server, so select the ‘SERVER NAME’ parameter accordingly.
In case of a single Agent installation – set the OpenLm server name in the Agent configuration window (‘support1’ in the image above).

Skip to content