Local License Server H2 Database Migration Steps
Migrating the FlexNet Embedded Local License Server H2 database from 1.4.x to 2.x is a two-step process:
|
•
|
Export—Run export on the old 1.4.x server to generate a migration data file. |
|
•
|
Import—Run import on the new 2.x server to load the data into a new database. |
Key Concepts Required for Successful Migration
You should understand the following key concepts in order to perform a successful migration.
Trusted Storage Directory
The database location is determined at runtime from either:
|
•
|
producer-settings.xml (server.trustedStorageDir) or |
|
•
|
Base directory overrides defined in configuration |
This directory contains:
|
•
|
H2 database file (flexnetls_licenses.mv.db) |
|
•
|
Keystore file (flexnetls_licenses.ks) |
|
•
|
Migration file (flexnetls-h2-1-4-x-migration-source.data) |
Role of the Keystore File
The flexnetls_licenses.ks file:
|
•
|
Is created when the 1.x service starts. |
|
•
|
Is required to open the encrypted H2 database during export. |
|
•
|
Must be present during import to create/read the new database. |
The same flexnetls_licenses.ks file must be used for both export and import. It must be copied when migrating to a new machine.
Producer Settings Requirement
The same producer-settings.xml must be used for both export and import. This ensures that the migration file can be decrypted successfully.
Import Behavior
Import is idempotent: If data already exists, import is skipped safely.