Migrating to Version 3 of the UDDI registry

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.

Before you begin

The following constraints apply to this procedure:
  • Your existing registry must use a DB2 database.
  • Your existing registry must run on WebSphere Application Server Version 5.1.x.

Procedure

  1. Stop the UDDI registry application that is running in the Version 5.1.x application server. 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 WebSphere Application Server Version 5.1.x system, or in the properties subdirectory if you are migrating a stand-alone application server.
  3. Migrate the server from WebSphere Application Server Version 5.1.x to Version 7.0. A new directory tree is created for the migrated Version 7.0 application server.
  4. Start the new, migrated, Version 7.0 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 Java™ Naming and Directory Interface (JNDI) name must be datasources/uddimigration. To complete this step, see Setting up a UDDI migration data source.
  6. Set up the UDDI Version 3 registry and migrate the Version 2 data.
    Follow the instructions in the topic about setting up a customized UDDI node, including the subtopic about node initialization. The topics describe how to complete the following actions:
    • Create the Version 3 DB2 database.
    • Create the Java 2 Connector (J2C) authentication data entry.
    • Create the Java Database Connectivity (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. 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:
  • initialization pending
  • migration pending
  • value set creation pending
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 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.

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    

Terms of Use | Feedback

Last updated: Oct 21, 2010 3:36:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-iseries&topic=twsu_migrate
File name: twsu_migrate.html