Migrating the UDDI registry

With most scenarios, existing UDDI registries are migrated automatically when you migrate to the current level of WebSphere® Application Server. However, if your 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.

Before you begin

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

About this task

If your existing UDDI registry uses an Oracle, embedded Apache Derby or DB2 UDDI Version 3 database, you 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 your 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, you must migrate the database. For details, see the topic in the related links.

Procedure

Results

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

Note: 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 you 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. For more information about these log files, see the topic about 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 you cannot solve it, refer to the problem determination information on the WebSphere Application Server support Web page.
CWUDQ004W: UDDI registry not started due to migration errors



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=twsu_migrate_all
File name: twsu_migrate_all.html