You can change the environment of the UDDI registry application
after you deploy it. For example, you can evaluate a UDDI registry
using one database, then put it into production using a different
database.
About this task
After you deploy a UDDI registry application, you might want
to change its environment. For example, you might perform initial
evaluation of the UDDI registry using an Apache Derby database, and
then put the UDDI registry into production using a DB2® database.
Procedure
- Optional: To move from a default UDDI node
to a customized UDDI node, delete the UDDI registry database and recreate
it by completing one of the following tasks, ensuring that you do
not use the default node options where specified:
Note: Any data that is saved in the default node (policies, properties,
and user data) is lost when you delete the database. If you do not
want to delete the database, create an entirely new customized UDDI
node in a separate application server. The default UDDI node still
exists for you to use for test purposes.
- Optional: To change the database type for the
UDDI registry, perform the following steps:
- Stop the UDDI registry application. Click , select the relevant check box, then click Stop.
- Either change the Java Naming and Directory Interface
(JNDI) name of the existing data source from datasources/uddids to
another value, or delete the data source. To display the data source
properties, click .
- Create the new database by referring to one of the following
topics:
- To transfer your UDDI data, use the capabilities of
the database product to export the data from the old database, and
import it into the new one.
- Create the new data source. See Creating a data source for the UDDI registry.
- Restart the UDDI registry application.
- Check that you can access your UDDI data, for example
use the UDDI registry installation verification test, then delete
the old database.