![[V5.1 and later]](../../v51x.gif)
Migrating from a previous version of IBM WebSphere UDDI Registry
Overview
Migrating from the IBM WebSphere UDDI Registry on WebSphere Application Server 4.0
If you have previously installed the IBM WebSphere UDDI Registry V1.1 (or later refreshes) on WebSphere Application Server V4.0, take the following steps in order to migrate to the UDDI Registry that is available as part of WebSphere Application Server for Network Deployment.
- If you have made any changes to the configuration properties in the file
uddi.properties, which is located in the properties subdirectory of your WebSphere
Application Server install tree, make a copy of this file (or make a note
of all the changes), so that you can reapply the changes to the file after
you have installed WebSphere Application Server V5.0.
- If you have made any other configuration changes, for example to the UDDI
user console style sheets or to the SOAP interface properties, make a note
of them, and reapply them after upgrading to the new UDDI version.
- Uninstall the IBM WebSphere UDDI Registry using Add/Remove Programs on
Windows platforms, or rpm -e IBMWebSphere-UDDI on Unix platforms. This removes
the application, but preserves the UDDI Registry database.
- If you wish to continue using DB2 as the persistence store for the UDDI
Registry, and you have any data in the UDDI Registry that you wish to preserve,
not run the DB2 setup wizard to create the DB2 version of the UDDI
Registry database, but will instead be able to continue using the database
that you already have. However, if you do run the wizard, you are prompted
to keep the database or overwrite it.
- Now follow the instructions on installing (or upgrading) IBM WebSphere
Application Server and "Installing the UDDI
Registry component".
- After completing the installation procedure, edit the uddi.properties
file to reflect any changes that you require to the configuration properties.
You should not replace this file with your previous copy from the IBM
WebSphere UDDI Registry V1.1 or later refreshes. You can also reapply any
other configuration changes as necessary.
- If you are migrating from V1.1 of the IBM WebSphere UDDI registry,
then there have been a few minor changes to the EJB interface which means
that you may need to modify your EJB client applications. If you are migrating
from later refreshes of the IBM WebSphere UDDI Registry (such as V1.1.1),
then not need to make any changes to your EJB clients.
The changes for V1.1 relate to saving a new service through the EJB interface either using saveBusiness or saveService. You should not set the serviceKey before calling saveBusiness or saveService.
In the IBM WebSphere UDDI Registry V1.1 the term 'service type' was used to refer to a 'technical model' or 'tModel', for example, in various of the panels in the UDDI user console. This term has now been replaced by the term 'technical model'.
Migrating
from IBM WebSphere Network Deployment V5.0x - federated nodes - to Version
5.1
For a Network Deployment configuration with federated nodes, IBM WebSphere Application Server supplies facilities to migrate to Version 5.1 from V5.0x either as part of the installation process, or as a post installation procedure. For instructions on how to do this refer to Migrating V3.5.x and V.4.0.x to Network Deployment elsewhere in this Information Center.
As part of the migration process, IBM WebSphere Application Server will automatically install the new UDDI version supplied in V5.1, but will migrate the uddi.properties (from your previous Version 5.0x system) for use in your new setup. If you are using DB2 as your persistence store, the same database used in V5.0x can be used in V5.1. Ensure your version of DB2 is supported by IBM WebSphere Application Server V5.1.
If you are using Cloudscape as your persistence store, you can also use the V5.0x database in V5.1 but review the Cloudscape instructions elsewhere in this Information Center for guidance on upgrading to a supported Cloudscape version.
By default, the newly migrated Application Server contains a JDBC provider that points to your 'old' pre-migration UDDI20 Cloudscape database (which is in your pre-migration WebSphere filing system). This is acceptable, however you may wish to copy your old UDDI20 database to the newly migrated Application Server filing system (in <NewAppServer-install-dir>/bin/UDDI20
In either case you will also need to make some updates to your JDBC provider to complete the migration, before starting the new Application Server. This can be done via the administration console.
- Update the JDBC provider resource as follows:
- update the Classpath to point to the new location for db2j.jar which is
<NewAppServer-install-dir>/cloudscape/lib/db2j.jar
- update the Classpath to point to the new location for db2j.jar which is
- update the version 4 datasource for this
- update the 'database name' path to point to the new location in the new Application Server, but only if you have moved it.
- update the custom properties
- update the property 'database name' to point to the new location in the
new Application Server, but only if you have moved it.
- add the new custom property 'connectionAttributes' with a vlaue of 'upgrade=true'.
- update the property 'database name' to point to the new location in the
new Application Server, but only if you have moved it.
If you have made other configuration changes to the UDDI user console style sheets for example, or other SOAP interface properties, you will have to manually reapply them.
Migrating
from IBM WebSphere Application Server V5.0x to IBM WebSphere Application
Server 5.1 in a single appserver only environment
In contrast with the Network Deployment migration, which is mostly automatic, some manual steps are required to upgrade from a WebSphere 5.0x single appserver configuration to a WebSphere 5.1 single appserver configuration.
In this case it is assumed that you have installed WebSphere Network Deployment to obtain the UDDI application and have installed UDDI into a standalone application server. It is assumed you wish to migrate your 5.0x appserver only.
Refer to the migration instructions elsewhere in this Information Center (see Migrating V3.5.x and V.4.0.x to Network Deployment) but here are the general steps you will need to follow:
- Stop the WebSphere 5.0x appserver containing the UDDI
- Install IBM WebSphere Application Server V5.1 Network Deployment
on to your system of choice. This will be needed to obtain the new UDDI application
and associated files.
- Install IBM WebSphere Application Server V5.1 Application Server
selecting the migration option. Once completed you will have a new 5.1 Application
Server, with your configuration (other applications) migrated. This will include
the UDDI application from your old 5.0x system.
- Copy across the new UDDI application and associated files from the new Version
5.1 Network Deployment to your new 5.1 Application Server. This is effectively
following the same instructions as supplied in Installing and setting up a UDDI Registry, but
in summary you will need to copy the following files and directories:
- uddi.ear to <NewAppServer-install-dir>/installableApps
- uddiresourcebundles.jar to <NewAppServer-install-dir>/lib
- setupuddimessages.jar to <NewAppServer-install-dir>/lib
- uddicloudscapeuserfunc.jar to <NewAppServer-install-dir>/lib
- the UDDIReg/scripts directory to <NewAppServer-install-dir>
The uddi.properties file, including any modifications you have made are copied across by the migration process and requires no further action.
- uddi.ear to <NewAppServer-install-dir>/installableApps
- Database migration consideration
- DB2 users. If you are using DB2 as your persistence store, the
same database used in V5.0x can be used in V5.1, but
review the supporting software information to confirm your DB2 version is
a supported level for IBM WebSphere Application Server V5.1
- Cloudscape users. If you are using Cloudscape as your persistence
store and want to continue to use the database (and the data in it) from your
old WebSphere, copy your old UDDI20 to the newly migrated Application Server
filing system (<NewAppServer-install-dir>/bin/UDDI20).
- Start the new appserver and run the appropriate appserversetupuddi.jacl command (for DB2 or Cloudscape) ensuring the paths refer to your new Version 5.1 Application Server. This installs the new V5.1 UDDI into your server. For details of the syntax of the appropriate commands see Setting up the UDDI Registry to use Cloudscape in a single appserver or Setting up the UDDI Registry to use DB2 in a single application server and then return to this point.
- DB2 users. If you are using DB2 as your persistence store, the
same database used in V5.0x can be used in V5.1, but
review the supporting software information to confirm your DB2 version is
a supported level for IBM WebSphere Application Server V5.1
- If you have made other configuration changes, to the UDDI user console
style sheets for example or other SOAP interface properties, manually reapply
them.
- Restart, and use, the new Application Server.
Enabling Universal Description, Discovery and Integration (UDDI)