Migrate to V3 of the UDDI registry

 

Use this topic to migrate a V2 UDDI registry that uses a DB2 database, running in WAS V5 or later, to a V3 UDDI registry running in WAS Version 6.x. The following constraints apply to this procedure:

• Your existing registry must use a DB2 database.

• Your existing registry must run in WAS Version 5 or later. If you are migrating from UDDI registry V1.1 or 1.1.1, which ran on WAS V4, first migrate to UDDI V2 running on WAS V5 (as described in the WAS V5 Information Center), then complete the steps described in this topic.

• You must have already migrated the WebSphere Application Server V5 deployment manager to V6.x.

You can only run the V2 UDDI registry, supplied in WAS V5, in a WebSphere Application Server V6.x server if you are running in a mixed cell migration mode. In this configuration, the WAS V6.x deployment manager manages the version 5.x nodes, and the V2 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 appserver and you migrate to WAS V6.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 V5 of WAS, but you will not be able to run the UDDI registry in the V6.x servers of WAS until all nodes in the cluster have been migrated to WAS V6.x. This is because the UDDI data needs to be migrated from the UDDI V2 format to the UDDI V3 format.

If you are migrating the UDDI registry from a WAS version 5.x ND configuration, or from a WAS version 5.x standalone appserver, the steps are very similar. For a ND migration to a WAS version 6.x ND configuration, a number of choices are available, including having a mixed version cell where the WAS version 6.x Deployment Manager can manage appservers at different levels. In this way, individual appservers 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 appserver. 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/nodes/node/servers/server directory on your WAS Version 5.x system (or in the properties subdirectory if you are migrating a standalone appserver).

3. Migrate the server from WAS V5.x to V6.x. This results in a new directory tree for the migrated V6.x appserver.

4. Start the new, migrated V6.x appserver.

5. Create a new data source for the V2 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 V3 registry and migrate the V2 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 V3 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 V2 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.

---

Setting up a UDDI migration datasource

 

Related tasks

Migrating the UDDI registry
Setting up a customized UDDI node
Migrating and coexisting
Use the UDDI registry

 

Related Reference

UDDI registry terminology