OpenLM is a license management tool that provides application usage monitoring for a variety of Concurrent license servers. These include FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy.
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 to MS-SQL. 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.
Backup the current OpenLM database
It is good practice to begin with backing up the OpenLM database prior to migrating its content. In order to do so:
1. Navigate to the windows services (you can do that by searching for services.msc in the start menu’s search line).
2. Select the “OpenLM Server” service, and Click the Stop icon.
3. Backup the OpenLM database. Please refer to the “Backing Up Your OpenLM DB” document for a more detailed explanation.
Important note: Planning the workflow: Firebird 1.7 to MS-SQL 1.8
There are two routes for migrating Firebird 1.7 to MS-SQL 1.8:
Workflow 1: Migrate Firebird 1.7 to MS-SQL 1.7, and then upgrade MS-SQL 1.7 to MS-SQL 1.8
Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8, and then migrate Firebird 1.8 to MS-SQL 1.8.
We will relate to these two routes throughout this document.
At the time of writing this revision (Rev 1.0), only Workflow 1 is supported, but both are described in this document. Please follow through the steps required according to your selected workflow.
Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8
Upgrading of the Firebird database OpenLM Server version 1.7 to Firebird database OpenLM Server version 1.8 is done by simply installing the later OpenLM Server version over the old one. It is important to keep a copy of the database prior to this upgrade. For more information, please refer to this document:
Workflows 1 & 2: Creating a new MS-SQL Database (Building the tables)
Create a new empty database with OpenLM tables in MS-SQL. In order to do so, OpenLM supplies dedicated DDL scripts (*.SQL files) to be applied in the MS-SQL Database control application.
1. For Workflow 1: The DDL scripts for MS-SQL 1.7 databases are available for download here. The Downloaded file contains two files for MS-SQL servers.
For Workflow 2: The DDL scripts for MS-SQL 1.8 databases are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.8 section, and choose the DDL scripts. The Downloaded file contains two files for MS-SQL servers.
2. Open the Microsoft SQL Server Management Studio
(Start → All Programs → Microsoft SQL Server → SQL Server Management Studio).
3. Create a new DB: Right click the “Databases” icon. select “New Database” from the pop-up menu, as shown below.
4. Enter a new name for the database (e.g.: db_name) and click OK.
5. For workflow 1: Drag the “OpenLM_SQLServer.SQL” file from the downloaded directory over to the Microsoft SQL Management Studio window. The Contents of “OpenLM_SQLServer.SQL” is displayed. (The file can also be opened by clicking “File → Open → File…” and selecting “OpenLM_SQLServer.SQL” from the unzipped folder).
For workflow 2: Drag the “OpenLM_SQLServer_1.8.0.SQL” file from the downloaded directory over to the Microsoft SQL Management Studio window. The Contents of “OpenLM_SQLServer_1.8.0.SQL” is displayed. (The file can also be opened by clicking “File → Open → File…” and selecting “OpenLM_SQLServer_1.8.0.SQL” from the unzipped folder).
6. Enter the new database name after the word “use” as shown below (e.g.: db_name) and click “Execute”
7. Wait until you see the message “Query executed successfully” as shown below:
Workflows 1 & 2: Data Migration
Now we get to the actual migration of data from Firebird to MS-SQL:
1. Make sure that the original Firebird DB is backed up, according to this document.
2. Open the “OpenLM Data Migration” tool.
For workflow 1: Data migration is done from Firebird 1.7 → MS-SQL 1.7. Use the data migration 1.7 version.
For workflow 2: Data migration is done from Firebird 1.8 → MS-SQL 1.8. Use the data migration 1.8 version.
3. On the Source frame:
3a. Select “Firebird”. The “Database Credentials” window appears:
3b. Enter the Firebird database path in the appropriate text box.
3c. Select your database(*.FDB) and enter the username and password. By default, the username is set to ‘sysdba’ and the password is ‘masterkey’
4. Target frame actions:
4a. Type in the MS-SQL Server name.
4b. Select the ‘MS-SQL’ radio button. The “Database Credentials” window appears.
4c. In the “MS-SQL Service” text box type in the MS-SQL instance name.
4d. The MS-SQL default port is set to 1521
4e. Set the Username and Password, and click OK.
5. After configuring the Source and Target databases, click the ‘Transfer’ button to begin the migration process. At the end of the migration, a notifier window appears.
Please refer to the “Guide to OpenLM Data Migration Tool” document for further information.
Workflow 1: Upgrade MS-SQL 1.7 to MS-SQL 1.8
Upgrading the MS-SQL 1.7 database to 1.8 is done by applying the 2nd SQL script (‘OpenLM_SQLServer_1.8.0_Upgrade.sql’) downloaded as part of the “Workflows 1 & 2: Creating a new MS-SQL Database (Building the tables)” section above. Drag it over to the Microsoft SQL Management Studio, and run it. The OpenLM MS-SQL schema is upgraded to version 1.8.
Configuring Openlm to work with the SQL server
Now the OpenLM server must be made to reference the new SQL Server.
1. Open the “OpenLM Database Configuration” tool:
(Start → All Programs → OpenLM → Server → OpenLM Database configuration)
2. Click the DB provider drop-down menu. Choose one of the options: “SQL Server Authentication” or “Windows Authentication mode”. The “OpenLM Database Configuration” window changes accordingly:
3. Fill in the information in the blank text boxes.
4. Click “Check” to check the OpenLM server’s connection to SQL Server.
5. Click “Apply” to finish the configuration.
Please refer to “OpenLM Database Configuration Form” for further information.
Rev 1.0, May 30 2013.