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 Version 2 database, there are some manual steps that you must take.
Migrate the installation of WAS. Ensure selected 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 Version 3 database, we do not have to complete any manual migration; the registry is migrated automatically when you migrate WebSphere Application Server 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, you must complete some manual steps to migrate the registry.
If the UDDI database uses Apache Derby Version 10.2, migrate the database. For details, see the topic in the related links.
If the UDDI registry uses a network Apache Derby database...
- If we have a cluster containing servers at different levels of WAS, ensure that any UDDI registries are running on servers that are at the current level of WAS. For example, if you 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 that any servers that are running a UDDI registry are at the current level.
- Initialize the relevant UDDI node. The initialize process will complete some of the UDDI registry migration.
- 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_pathwhere
- uddi_derby_database_path is the absolute path of the existing Apache Derby database, for example app_server_root/profiles/profile_name/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 you migrate WebSphere Application Server, 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
- Set up a UDDI migration data source
For DB2, we can set up a UDDI migration data source that we can use to reference a Version 2 UDDI registry database.
- Migrate a UDDI database that uses Apache Derby
If a UDDI database that uses Apache Derby was created with WAS v6.1 or earlier and now uses Apache Derby Version 10.2 or later, we need to migrate the database. If we have a UDDI database that uses any other supported database, including versions of Apache Derby earlier than Apache Derby Version 10.2, we do not need to undertake this procedure.
WebSphere Application Server Support