r1 - 09 Jul 2008 - 15:09:57 - RandyLetnessYou are here: OSAF >  Documentation Web  >  ServerBundleAdministrator > ServerBundleInstallation > CosmoMigrationUsers

Cosmo Migration Information for Users

This page contains information about the migration code included with the server bundle that allows users to migrate existing data from an older version of the server to the latest version.


The server bundle includes a migration component located in $OSAFSRV_HOME/migration, which consists of a self-contained jar, a README file and migration.properties file.

File purpose
migration.jar self-containted jar containing all code and migration code and scripts
README.txt instructions on how to perform migration
migration.properties sample properties file that contains properties required for migration.

In a nutshell, the migration component is a java program designed to migrate from any previous version the the server to the latest version. The component is updated for each release of the server that contains a schema change.


The migration runner relies on properties defined in a properties file (migration.properties). The properties to set are:

property purpose
migration.dialect identifier for database dialect to use for migration (MySQL?, Derby, PostgeSQL?).
migration.datasource.driverClassName JDBC Driver class name
migration.datasource.url JDBC url to cosmo database
migration.datasource.username database username
migration.datasource.password datasource password

The included migration.properties has example configurations for derby, mysql, and postgres database. Uncomment the one that fits your database and plug in your values.

Running Migration

NOTE: Before attempting migration, BACK UP YOUR DATABASE!!

Although we'd like to think migration works perfectly, there is a possibility that your data will get corrupted, so please make a backup before running migration.

The migration runner is packaged as an all-in-one Java archive file (jar). You invoke the runner using java:

$java -jar migration.jar [-v] [path to migration.properties file]

So for example:

$java -jar migration.jar -v migration.properties

will look for migration.properties in the current directory and output extra debug info.

-- RandyLetness - 09 Jul 2008

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.