+

Search Tips   |   Advanced Search

Migrate to V3 of the UDDI registry


We can migrate a V2 UDDI registry that uses a DB2 database and runs on WAS Version 5.1.x to a V3 UDDI registry that runs on WAS V7.0. WAS Version 6.x already includes the V3 UDDI registry, so if we are migrating from V6.x, you do not need to use this procedure.

The following constraints apply to this procedure:

We can run the Version 2 UDDI registry that is supplied in WAS V5, on a WAS V7.0 server only if we are running in a mixed cell migration mode. In this configuration, the WAS V7.0 dmgr manages the V5.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 appserver and you migrate to WAS V7.0, we cannot run UDDI across the mixed-version cluster. We can continue to run the UDDI registry on the server or servers that remain at V 5 of WAS, but we cannot run the UDDI registry in the V7.0 servers of WAS until all nodes in the cluster are migrated to WAS V7.0. This is because the UDDI data must be migrated from the UDDI V 2 format to the UDDI V3 format.

If migrating the UDDI registry from a WAS V5.1.x ND configuration, or from a WAS Version 5.1.x stand-alone appserver, the steps are very similar. For an ND migration to a WAS V7.0 ND configuration, a number of choices are available, including having a mixed-version cell where the WAS V7.0 dmgr can manage appservers at different levels. In this way, we can migrate individual appservers when it is convenient, in a step-by-step manner.

 

  1. Stop the UDDI registry application that is running in the Version 5.1.x appserver. This action prevents further UDDI requests from 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 that are used. The location of this file is in the DeploymentManager_install_dir/config/cells/cell_name/nodes/node_name/servers/server_name directory on the WAS V5.1.x system, or in the properties subdirectory if we are migrating a stand-alone appserver.

  3. Migrate the server from WAS V5.1.x to V7.0. A new directory tree is created for the migrated V7.0 appserver.

  4. Start the new, migrated, V7.0 appserver.

  5. Create a new data source for the V2 UDDI database. This data source is known as the UDDI migration data source.

    The Java Naming and Directory Interface (JNDI) name must be datasources/uddimigration. To complete this step, see Set up a UDDI migration data source.

  6. Set up the UDDI V3 registry and migrate the V 2 data. Follow the instructions in Set 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 Java 2 Connector (J2C) authentication data entry.

    • Create the JDBC provider and data source.

    • Deploy the UDDI registry application.

    • Start the server.

    • Set 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. The data migration might take some time, depending on the amount of data in the UDDI registry.

 

Results

The UDDI registry is migrated. Verify that the migration process completed successfully by checking for the following message in the server log:

CWUDQ0003I: UDDI registry migration has completed

If the UDDI node remains in one of the following states, check the server log for errors:

If the following message is displayed, an unexpected error occurred during migration:

CWUDQ004W: UDDI registry not started due to migration errors
Check the error logs for the problem and, if we cannot resolve the error, refer to WAS Support Web page. After you resolve the problem, we can complete the migration by clicking Initialize again.

 

Next steps

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


Set up a UDDI migration data source

 

Related tasks


Migrate the UDDI registry
Set up a customized UDDI node
Use the UDDI registry

 

Related


UDDI registry terminology

 

Related information


WAS Support Web page