Migrate the UDDI registry

With most scenarios, existing UDDI registries are migrated automatically when you migrate to the current level of WAS. However, if the existing UDDI registry uses a network Apache Derby database or a DB2 UDDI V2 database, there are some manual steps that take.

Migrate the installation of WAS. Ensure that you select the option to migrate applications, so that the UDDI registry application will be migrated.

If the existing UDDI registry uses an Oracle, embedded Apache Derby or DB2 UDDI V3 database, you do not have to perform any manual migration; the registry is migrated automatically when you migrate WAS and start the UDDI node for the first time after migration.

If the existing UDDI registry uses a network Apache Derby database or a DB2 UDDI Version 2 database, complete some manual steps to migrate the registry.

If the UDDI database uses Apache Derby V 10.2, migrate the database. For details, see the topic in the related links.

 

• If the UDDI registry uses a DB2 UDDI Version 2 database, follow the steps in Migrate to V3 of the UDDI registry and sub-topics.

• If the UDDI registry uses a network Apache Derby database...

  1. If we have a cluster that contains servers at different levels of WAS, ensure that any UDDI registries are running on servers that are at WAS V7.0. For example, if we have a cluster that spans two nodes, we can upgrade one node to WAS V7.0 while the other node remains at a previous level, provided that any servers that are running a UDDI registry are at Version 7.0.

  2. Initialize the relevant UDDI node. The initialize process will perform some of the UDDI registry migration.

  3. Enter the following commands as the database administrator, from APP_ROOT/derby/lib.

     java -cp db2j.jar;db2jtools.jar com.ibm.db2j.tools.ij
      connect 'jdbc:db2j:uddi_derby_database_path';
      run 'APP_ROOT/UDDIReg/databaseScripts/uddi30crt_drop_triggers_derby.sql';
     
     quit;
      cd APP_ROOT/derby/migration
      java -cp db2j.jar;db2jmigration.jar;../lib/derby.jar com.ibm.db2j.tools.MigrateFrom51 
       jdbc:db2j:uddi_derby_database_path
     
     
     

     where

     • uddi_derby_database_path is the absolute path of the existing Apache Derby database, for example APP_ROOT/profiles/profile_name/databases/com.ibm.uddi/UDDI30
     • APP_ROOT is the root directory for the installation of WAS

 

Results

The UDDI database and data source are migrated, and the UDDI node is activated.

When you migrate WAS, the post-upgrade log for the profile indicates that the migration of the UDDI database is partially complete, and is missing the steps for triggers, aliases, and stored statements. If we initially enabled the debug function, the debug log for the database indicates that there was a failure creating triggers. Ignore these messages; the UDDI node completes the migration of the database when the UDDI node starts.

See about these log files, see Verifying the Cloudscape automatic migration. Also refer to this topic if other errors appear in the logs. If the migration of the UDDI database completes successfully, the following message appears in the server log:

CWUDQ0003I: UDDI registry migration has completed

If the following error appears, an unexpected error occurred during migration. The UDDI registry node is not activated. Check the error logs for the problem and, if we cannot solve it, refer to IBM software support.

CWUDQ004W: UDDI registry not started due to migration errors

Migrate a UDDI database that uses Apache Derby

 

Related tasks

Migrate to V3 of the UDDI registry
Verifying the Cloudscape automatic migration
Use the UDDI registry