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

Database Migration: Firebird to MySQL 2.0 – AN3008c

Scope

OpenLM is a license management tool that provides application usage monitoring for a variety of concurrent license servers. OpenLM provides an embedded Firebird database  as part of the software installation. It also supports different types of external databases, such as MS-SQL, Oracle and MySQL. This document is intended for system administrators who wish to perform an OpenLM database migration from the default Firebird database to the MySQL database. It elaborates the process and tools required for such a migration. This document is closely related to the Guide to OpenLM Data Migration Tool, OpenLM Database Configuration Form  and Backing Up Your OpenLM DB documents, which are recommended for further reading.

Back up the database

Backing-up the database is mandatory, since the database upgrade process is sensitive to hardware and software malfunctions. Upgrade the OpenLM Server without backing up the database file may compromise the accumulated data. Stop the “OpenLM Server” Windows’ Service, and backup the database file, typically located at “C:\Program Files (x86)\OpenLM\OpenLM Server\db”.

Older versions

Migrating older versions of OpenLM (e.g. 1.8.x.x) Firebird Databases to the latest version on MySQL is done in 2 stages:
1. Upgrading to the latest Firebird database.
2. Migrating the updated Firebird database to an external database.

Migrating the database

1. Creating the MySQL tables

The first stage in migrating the OpenLM database is to create a new empty database with OpenLM tables in MySQL. In order to do so, OpenLM provides dedicated DDL scripts (*.SQL files) to be applied in the MySQL application.

1.1. Please contact OpenLM support to obtain the DDL scripts for MySQL.

1.2. Open the MySQL workbench, on the SQL Editor.

1.3. Create a new schema, e.g.: new_schema

1.4. Click the New SQL icon, and open the SQL script downloaded in step (2)

1.5. Change the schema’s name in the 1st line of the script (e.g.: new_schema) and click the flash icon to run the SQL script.

1.6. Wait until you see the last line configured: INSERT INTO olm_vendors_definition … as in the image above.

2. Data Migration

Now we get to the actual migration of data from Firebird to MySQL.

2.1. Make sure that the Firebird database is backed up, according to the “Back up the database” section above.

2.2. Open the “OpenLM Data Migration” tool.

2.3. On the Source frame:

2.3a. Select “Firebird”. The “Database Credentials” window appears.

2.3b. Enter the Firebird database path in the appropriate text box.

2.3c. Select your Firebird database(*.FDB) and enter the user name and password. By default, the user name is set to ‘sysdba’ and the password is ‘masterkey’.

2.4. On the Target frame:

2.4a. Type in the MySQL database hostname.

2.4b. Check the MySQL radio button. The “Database Credentials” window appears.

2.4c. Type in the schema name (e.g.: new_schema), MySQL user name and password in the appropriate text boxes.

2.5. After configuring the Source and Target databases, the migration process may begin. Click the “Transfer” button. At the end of the migration process, a notifier window appears. Please refer to the “Guide to OpenLM Data Migration Tool” document for further information.
3. Configuring Openlm to work with the MySQL Database

Now the OpenLM server must be made to point to the new MySQL database.

3.1. Open the “OpenLM Database Configuration” tool:

(Start → All Programs → OpenLM → Server → OpenLM Database configuration).

3.2. Click the DB provider drop-down menu. Choose the MySQL option.

3.3. Fill in the information in the blank text boxes:

3.3a. Database – type in the hostname where the database resides.

3.3b. Data source – the new scema (e.g.: new_schema).

3.3c. User ID and password – of the MySQL user.

3.4. Click “Check” to check the OpenLM server’s connection to MySQL.

3.5. Click “Apply” to finish the configuration.

Please refer to “OpenLM Database Configuration Form” for further information.

Epilog

That’s it. The database has been upgraded and migrated to the latest version.

It is now recommended to

  • Stop and start the OpenLM Server service and
  • Perform a sanity – check to the OpenLM system’s functionality; Open the EasyAdmin web application, and review the License servers’ status and usage reporting windows.