Changing the UDDI registry application environment after deployment

We can change the environment of the UDDI registry application after you deploy it. This means we can evaluate a UDDI registry using one database, then put it into production using a different database, or we can move from a standalone application server to a network deployment cell.

 

About this task

After you deploy the UDDI registry application, you might want to change its environment. For example, you might perform initial evaluation of the UDDI registry using a Cloudscape database, and then want to put the UDDI registry into production using a DB2 database, or you might want to move from a standalone application server to a network deployment cell.

 

Procedure

1. Optional: To incorporate a standalone application server into a network deployment cell, run the addNode command included with WebSphere Application Server. Use the includeapps parameter to ensure that the UDDI registry application, and any other applications on the server, are included in the move. See the addNode command for details.

2. 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:

   • Creating a DB2 distributed database for the UDDI registry

   • Creating an Oracle database for the UDDI registry

   • Creating a DB2 for z/OS database for the UDDI registry

   • Creating a Cloudscape database for the UDDI registry

   Note: Any data saved in the default node (policies, properties and user data) will be lost when you delete the database. If you do not want to delete the database, we can instead create an entirely new customized UDDI node in a separate application server. The default UDDI node will still exist for you to use for test purposes.

3. Optional: To change the database type for the UDDI registry, perform the following steps:

   1. Stop the UDDI registry application (click Applications > Enterprise Applications, select the relevant check box and click Stop).

   2. Either change the JNDI name of the existing datasource from datasources/uddids to another value, or delete the datasource. To display the datasource properties click JDBC providers > database_type JDBC Provider > Data sources > uddi_datasource.

   3. Create the new database by referring to one of the following topics:

      • Creating a DB2 distributed database for the UDDI registry

      • Creating an Oracle database for the UDDI registry

      • Creating a DB2 for z/OS database for the UDDI registry

      • Creating a Cloudscape database for the UDDI registry

   4. To transfer your UDDI data, use the standard capabilities of the database products to export the data from the old database, and import it into the new one.

   5. Create the new datasource. See Creating a data source for the UDDI registry .

   6. Restart the UDDI registry application.

   7. Check that we can access your UDDI data, then delete the old database.

 

See also

Creating a DB2 distributed database for the UDDI registry

Creating a DB2 for z/OS database for the UDDI registry
Creating a Cloudscape database for the UDDI registry
Creating an Oracle database for the UDDI registry
Related tasks
Using the UDDI registry Installation Verification Program (IVP) Setting up and deploying a new UDDI registry Related reference
addNode command

 

---