Migrating to Version 3 of the UDDI registry

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

The following constraints apply to this procedure:
  • Your existing registry must use a DB2 database.
  • Your existing registry must run in WebSphere Application Server Version 5 or later. If you are migrating from UDDI registry Version 1.1 or 1.1.1, which ran on WebSphere Application Server Version 4, 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 must have already migrated the WebSphere Application Server Version 5 deployment manager to Version 6.x.

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.

Procedure

  1. Stop the UDDI registry application that is running in your Version 5.x application server. This prevents further UDDI requests being directed to the UDDI registry and ensures that no new data is published during the migration process.
  2. Record information about the uddi.properties values being used. This file is located in the DeploymentManager_install_dir/config/cells/cell_name/nodes/node_name/servers/server_name directory on your WebSphere Application Server Version 5.x system (or in the properties subdirectory if you are migrating a standalone application server).
  3. Migrate the server from WebSphere Application Server Version 5.x to Version 6.x. This results in a new directory tree for the migrated Version 6.x application server.
  4. Start the new, migrated Version 6.x application server.
  5. Create a new data source for the Version 2 UDDI database. This data source is known as the UDDI migration data source. The JNDI name must be datasources/uddimigration. To complete this step see Setting up a UDDI migration datasource.
  6. Set up the UDDI Version 3 registry and migrate the Version 2 data.
    Follow the instructions in Setting up a customized UDDI node, including the subtopic that relates to node initialization. The topic describes how to perform the following actions:
    • Create the Version 3 DB2 database
    • Create the J2C authentication data entry
    • Create the JDBC provider and data source
    • Deploy the UDDI registry application
    • Start the server
    • Configure and initialize the node. The UDDI registry node initialization detects the UDDI migration data source, and migrates the Version 2 data as part of the UDDI node initialization processing. This data migration can take some time, depending on the amount of data in your UDDI registry.

Results

The UDDI registry is migrated. If the UDDI node remains in a state of initialization pending, migration pending or value set creation pending, check the server log for errors. If the following message appears, an unexpected error occurred during migration. 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.
CWUDQ004W: UDDI registry not started due to migration errors
After the problem is fixed, you can complete the migration by clicking Initialize again.

Verify that the migration process completed successfully by checking for the following message in the server log:

CWUDQ0003I: UDDI registry migration has completed

What to do next

After migration is complete you can remove the UDDI migration data source, and the registry is available for use.



In this information ...


Related reference

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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=twsu_migrate
File name: twsu_migrate.html