Use this topic to migrate a Version 2 UDDI registry that uses a DB2 database, running in WebSphere Application Server Version 5 or later, to a Version 3 UDDI registry running in WebSphere Application Server Version 6.x.
Before you begin
You can only run the Version 2 UDDI registry, supplied in WebSphere Application Server Version 5, in a WebSphere Application Server Version 6.x server if you are running in a mixed cell migration mode. In this configuration, the WebSphere Application Server Version 6.x deployment manager manages the version 5.x nodes, and the Version 2 UDDI registry is supported only for migration purposes; it is not supported for normal execution.
If you have the UDDI registry deployed in a clustered application server and you migrate to WebSphere Application Server Version 6.x, you will not be able to run UDDI across the mixed-version cluster. You can continue to run the UDDI registry on the server or servers that remain at Version 5 of WebSphere Application Server, but you will not be able to run the UDDI registry in the Version 6.x servers of WebSphere Application Server until all nodes in the cluster have been migrated to WebSphere Application Server Version 6.x. This is because the UDDI data needs to be migrated from the UDDI Version 2 format to the UDDI Version 3 format.
If you are migrating the UDDI registry from a WebSphere Application Server version 5.x Network Deployment configuration, or from a WebSphere Application Server version 5.x standalone application server, the steps are very similar. For a Network Deployment migration to a WebSphere Application Server version 6.x Network Deployment configuration, a number of choices are available, including having a mixed version cell where the WebSphere Application Server version 6.x Deployment Manager can manage application servers at different levels. In this way, individual application servers can be migrated when convenient in a step by step manner.
Steps for this task
CWUDQ0003I: UDDI registry migration has completed
If you see the following error :
CWUDQ004W: UDDI registry not started due to migration errors
an unexpected error occurred during migration. The UDDI registry node is not activated. Check the error logs for the problem and, if it cannot be fixed, see the IBM software support Web site at http://www.ibm.com/software/support.
Related concepts
Overview of migration and coexistence
Related tasks
Setting up a customized UDDI node
Using the UDDI registry
Related reference
UDDI registry terminology