Before you begin
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,
you should 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, you should 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 Version 1.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 Version 1.1.1),
then you should not need to make any changes to your EJB clients.
The changes
for Version 1.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'.