Use this topic to migrate to a Version 3 UDDI Registry that uses a DB2 database, from a previous version of the UDDI Registry.
Before you begin
Use this topic to migrate to a Version 3 UDDI Registry that uses a DB2 database, from a Version 2 UDDI Registry (as defined in UDDI Registry Terminology).If you are migrating from IBM WebSphere UDDI Registry Version 1.1 or 1.1.1, which ran on WebSphere Application Server Version 4, you should first migrate to UDDI Version 2 running on WebSphere Application Server Version 5 (as described in the WebSphere Application Server Version 5 Information Center), then complete the steps described in this topic.
You can only run the Version 2 UDDI Registry (supplied in WebSphere Application Server Version 5) in a WebSphere Version 6 server if you are running in a mixed cell migration mode. In this configuration, the WebSphere Application Server Version 6 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.
This task describes in detail the process of migrating from a Version 2 UDDI Registry running on WebSphere Application Server Version 5, to a Version 3 UDDI Registry running on WebSphere Application Server Version 6.
If you have the UDDI Registry deployed in a clustered application server and you migrate to WebSphere Application Server Version 6, 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 servers of WebSphere Application Server until all nodes in the cluster have been migrated to WebSphere Application Server Version 6. 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 Network Deployment configuration, a number of choices are available, including having a mixed version cell where the WebSphere Application Server version 6 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. See Migration and coexistence overview elsewhere in this Information Center for more details.
To migrate a Version 2 UDDI Registry to UDDI Version 3, running in WebSphere Application Server Version 6, complete the following steps (this is assuming that you have migrated the WebSphere Application Manager Version 5 Deployment Manager to Version 6 first):
Steps for this task
CWUDQ0003I: UDDI registry migration has completed
Should the following error appear:
CWUDQ004W: UDDI registry not started due to migration errors
it means that an unexpected error has occurred during migration. The UDDI Registry node will not be activated. Check the error logs for the problem and, if it cannot be fixed contact your IBM representative for advice.
Related tasks
Setting up a customized UDDI node
Using the UDDI Registry