You can migrate a Version 2 UDDI registry that uses a DB2® database and runs on WebSphere® Application Server Version 5.1.x to a Version 3 UDDI registry that runs on WebSphere Application Server Version 7.0. WebSphere Application Server Version 6.x already includes the Version 3 UDDI registry, so if you are migrating from Version 6.x, you do not need to use this procedure.
You can run the Version 2 UDDI registry that is supplied in WebSphere Application Server Version 5, on a WebSphere Application Server Version 7.0 server only if you are running in a mixed cell migration mode. In this configuration, the WebSphere Application Server Version 7.0 deployment manager manages the Version 5.1.x nodes, and supports the Version 2 UDDI registry for migration purposes only; the registry is not supported for normal operation.
If the UDDI registry is deployed in a clustered application server and you migrate to WebSphere Application Server Version 7.0, you cannot 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 cannot run the UDDI registry in the Version 7.0 servers of WebSphere Application Server Version 7.0. This is because the UDDI data must 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, Network Deployment configuration, or from a WebSphere Application Server Version 5.1.x stand-alone application server, the steps are very similar. For a WebSphere Application Server, Network Deployment migration to a WebSphere Application Server Version 7.0 WebSphere Application Server, Network Deployment configuration, a number of choices are available, including having a mixed-version cell where the WebSphere Application Server Version 7.0 deployment manager can manage application servers at different levels. In this way, you can migrate individual application servers when it is convenient, in a step-by-step manner.
CWUDQ0003I: UDDI registry migration has completed
CWUDQ004W: UDDI registry not started due to migration errorsCheck the error logs for the problem and, if you cannot resolve the error, refer to WebSphere Application Server Support Web page. After you resolve the problem, you can complete the migration by clicking Initialize again.
In this information ...Subtopics
Related reference
Related information
| IBM Redbooks, demos, education, and more(Index) |