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.
Procedure
- 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.
- 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).
- 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.
- Start the new, migrated Version 6.x application server.
- 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.
- 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. 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.