You can remove the UDDI registry application, delete the
UDDI registry database, move a UDDI registry to another server or
profile, or remove a UDDI registry node completely.
About this task
A UDDI registry node consists of the following elements:
- An enterprise application.
- A store of data that is referred to as the UDDI registry database
and that uses a relational database management system.
- A way to connect the application to the data, that is, a data
source and related elements.
All the data that relates to UDDI is stored in the UDDI database
and therefore that data is separate from the UDDI application. Therefore,
there are several options when you remove a UDDI registry node:
To start a new UDDI registry node, you do not need to remove
the UDDI application. Instead, you create a replacement node by changing
the data source that the UDDI application uses to access the new UDDI
database.
Depending on what you want to do, complete one of
the following steps.
Procedure
- To remove a UDDI registry node from the application
server without deleting the database, do one of the following:
- To delete a UDDI registry database, complete
the following steps. Remember that all UDDI data in the UDDI registry
is deleted.
- Stop the server that hosts the UDDI registry application.
- Delete the database.
- For DB2 for iSeries, use either iSeries Navigator
or a 5250 session to delete the IBMUDI30 and IBMUDS30 schemas.
- For Oracle, delete the IBMUDDI, IBMUDI30
and IBMUDS30 schemas.
- For Cloudscape, delete the directory tree
that contains the UDDI database. By default, this directory tree is
in the profile_root/databases/com.ibm.uddi/UDDI30
directory.
- To move a UDDI registry to another server or profile, complete
the following steps:
- Ensure that the UDDI registry database remains accessible
after the move. You might need to copy the database to a suitable
new location. For example, if the database is remote, the
new server must be able to access it. Also, the database might be
deleted after the move. This situation occurs if you move the UDDI
registry to a new profile and then delete the old profile, because
any databases that were stored in the profile are also deleted. An
example of such a database is a Cloudscape database that is created
as part of creating default UDDI node.
- Remove the UDDI registry application. See the step to remove a UDDI registry node from an application server.
- Optional: Delete the
data source and related objects.
For the Cloudscape
database, if you ran the
uddiRemove.jacl script and used the
default option
to remove the UDDI registry application, the data source and related
objects are deleted already and you do not need to complete this step.
In all other situations, delete the following objects:
- The UDDI data source that references the UDDI registry database,
that is, the data source that was created when you set up the UDDI
registry.
- Any UDDI JDBC provider that was created if you did not reuse an
existing JDBC provider.
- Any J2C authentication data entry.
- In the new server, if appropriate, create a J2C authentication
data entry, and create a JDBC provider and a data source to reference
the existing database. See the relevant steps in Setting up a customized UDDI node.
- Deploy the UDDI registry application. See Deploying the UDDI registry application.
If you use the supplied script, do not use the default option
even if you used this option previously to set up a default UDDI node.
Do not use the default option because an error might occur during
deployment, or, in some circumstances, existing UDDI data might be
overwritten.
Note: The UDDI node name does not change. If the UDDI
node name includes the node name and server name of the original server,
after the move there is a mismatch between the UDDI node name, and
the node name and server name of the new server. However, this mismatch
does not affect the UDDI registry node function.
- Check that the UDDI data can be accessed. If you are
using a copy of the original UDDI registry database, you can now delete
the original database. See the step to
delete a UDDI registry database.
- To remove a UDDI registry node completely, complete the
following steps:
- Remove the UDDI registry application. See the step to remove a UDDI registry node from the application server.
- Delete the UDDI registry database. See the step to delete a UDDI registry database.
- Optional: Delete the
data source and related objects.
For the Cloudscape
database, if you ran the
uddiRemove.jacl script and used the
default option
to remove the UDDI registry application, the data source and related
objects are deleted already and you do not need to complete this step.
In all other situations, delete the following objects:
- The UDDI data source that references the UDDI registry database,
that is, the data source that was created when you set up the UDDI
registry.
- Any UDDI JDBC provider that was created if you did not reuse an
existing JDBC provider.
- Any J2C authentication data entry.
What to do next
If you removed a UDDI registry node from the application
server without deleting the database, you might want to reinstall
the UDDI registry application.