+

Search Tips   |   Advanced Search

Migrate the UDDI registry

With most scenarios, existing UDDI registries are migrated automatically when we migrate to the current level of WebSphere Application Server. However, if our existing UDDI registry uses a network Apache Derby database or a DB2 UDDI v2 database, there are some manual steps that we must take.

Migrate the installation of WAS. Ensure that we select the option to migrate applications, so that the UDDI registry application is migrated.

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

If our existing UDDI registry uses a network Apache Derby database or a DB2 UDDI v2 database, we must complete some manual steps to migrate the registry.

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


Tasks

If our UDDI registry uses a network Apache Derby database.

  1. If we have a cluster containing servers at different levels of WAS, ensure any UDDI registries are running on servers that are at the current level of WAS. For example, if we have a cluster that spans two nodes, we can upgrade one node to the current level while the other node remains at a previous level, provided any servers that are running a UDDI registry are at the current level.
  2. Initialize the relevant UDDI node. The initialize process will complete some of the UDDI registry migration.

  3. Enter the following commands as the database administrator, from app_server_root/derby/lib. 
    java -cp db2j.jar;db2jtools.jar com.ibm.db2j.tools.ij

connect 'jdbc:db2j:uddi_derby_database_path';

run 'app_server_root/UDDIReg/databaseScripts/uddi30crt_drop_triggers_derby.sql';

quit;

cd app_server_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_server_root/profiles/profile/databases/com.ibm.uddi/UDDI30
    • app_server_root is the root directory for the installation of WAS

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

When we 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.

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 the problem determination information on the WAS support web page. 

CWUDQ004W: UDDI registry not started due to migration errors


Subtopics

  • WAS Support