With most scenarios, migration of existing UDDI registries happens
automatically when you migrate to the current level of WebSphere Application
Server. However, if your existing UDDI registry uses a network Cloudscape
database or a DB2 UDDI Version 2 database, there are some manual steps that
you must take.
Before you begin
Migrate your installation of WebSphere Application Server; ensure
that you select the option to migrate applications, so that the UDDI registry
application will be migrated.
About this task
If your existing UDDI registry uses an Oracle, embedded Cloudscape
or DB2 UDDI Version 3 database, you do not need to perform any manual migration;
migration happens automatically when you migrate WebSphere Application Server
and start the UDDI node for the first time after migration.
If your
existing UDDI registry uses a network Cloudscape database or a DB2 UDDI Version
2 database, you must complete some manual steps to migrate the registry.
Procedure
- If your UDDI registry uses a DB2 UDDI Version 2 database, follow
the steps in Migrating to Version 3 of the UDDI registry and
sub-topics.
- If your UDDI registry uses a network Cloudscape database, complete
the following steps.
- If you have a cluster that contains servers at different levels
of WebSphere Application Server, ensure that any UDDI registries are running
on servers that are at WebSphere Application Server Version 6.1. For
example, if you have a cluster that spans two nodes, you can upgrade one node
to WebSphere Application Server Version 6.1 while the other node remains at
a previous level, provided that any servers that are running a UDDI registry
are at Version 6.1.
- Initialize the relevant UDDI node. The initialize
process will perform some of the UDDI registry migration.
- Enter the following commands as the database administrator,
from app_server_root/cloudscape/lib.
java -cp db2j.jar;db2jtools.jar com.ibm.db2j.tools.ij
connect 'jdbc:db2j:uddi_cloudscape_database_path';
run 'app_server_root/UDDIReg/databaseScripts/uddi30crt_drop_triggers_cloudscape.sql';
quit;
cd app_server_root/derby/migration
java -cp db2j.jar;db2jmigration.jar;../lib/derby.jar com.ibm.db2j.tools.MigrateFrom51
jdbc:db2j:uddi_cloudscape_database_path
where
- uddi_cloudscape_database_path is the absolute path of the existing
Cloudscape database, for example app_server_root/profiles/profile_name/databases/com.ibm.uddi/UDDI30
- app_server_root is
the root directory for the installation of WebSphere Application Server
Results
The UDDI database and data source are migrated, and the UDDI node
is activated.
Note: When you migrate WebSphere Application Server, the
post-upgrade log for the profile indicates that the migration of the UDDI
database is partially complete, and is missing the steps for triggers, aliases,
and stored statements. If you initially enabled the debug function, the debug
log for the database indicates that there was a failure creating triggers.
Ignore these messages; the UDDI node completes the migration of the database
when the UDDI node starts. For more information about these log files, see
Verifying the Cloudscape v10.1.x automatic migration.
Also refer to this topic if other errors appear in the logs.
If the
migration of the UDDI database completes successfully, the following message
appears in the server log:
CWUDQ0003I: UDDI registry migration has completed
If
the following error appears, an unexpected error occurred during migration.
The UDDI registry node is not activated. 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