Change the UDDI registry application environment after deployment

We can change the environment of the UDDI registry application after we deploy it. For example, we can evaluate a UDDI registry using one database, then put it into production using a different database.

After we deploy a UDDI registry application, we might want to change its environment. For example, we might complete initial evaluation of the UDDI registry using an Apache Derby database, and then put the UDDI registry into production using a DB2 database.

Alternatively, we might want to move from a stand-alone application server to a WebSphere Application Server, Network Deployment cell.

Tasks

1. Optional: To incorporate a stand-alone application server into a WAS ND cell, run the addNode command that is included with WAS. Use the includeapps parameter to ensure that the UDDI registry application, and any other applications on the server, are included in the move.

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 we do not use the default node options where specified:
   • Create a DB2 distributed database for the UDDI registry
   • (iSeries) Create a DB2 for i database for the UDDI registry
   • Create a DB2 for z/OS database for the UDDI registry
   • Create an Apache Derby database for the UDDI registry
   • Create a Microsoft SQL Server database for the UDDI registry
   • Create an Oracle database for the UDDI registry

   Any data that is saved in the default node (policies, properties, and user data) is lost when you delete the database. If we 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.

3. Optional: To change the database type for the UDDI registry:

   1. Stop the UDDI registry application. Click Applications > Application Types > WebSphere enterprise applications, select the relevant check box, then click Stop.
   2. Either change the 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...

              Resources > JDBC > JDBC providers > database_type JDBC Provider > [Additional Properties] Data sources > uddi_datasource.

   3. Create the new database by referring to one of the following topics:
      • Create a DB2 distributed database for the UDDI registry
      • (iSeries) Create a DB2 for i database for the UDDI registry
      • Create a DB2 for z/OS database for the UDDI registry
      • Create an Apache Derby database for the UDDI registry
      • Create a Microsoft SQL Server database for the UDDI registry
      • Create an Oracle database for the UDDI registry

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

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

   6. Restart the UDDI registry application.

   7. Check that we can access your UDDI data, for example use the UDDI registry installation verification test, then delete the old database.

Subtopics

• Create a DB2 distributed database for the UDDI registry
  Complete this task to use DB2 on the Windows, Linux, or UNIX operating systems as the database store for our UDDI registry data.
• (iSeries) Create a DB2 for i database for the UDDI registry
  Complete this task to use DB2 for i as the database store for our UDDI registry data.
• Create a DB2 for z/OS database for the UDDI registry
  Complete this task to use DB2 for z/OS as the database store for our UDDI registry data.
• Create an Apache Derby database for the UDDI registry
  Complete this task to use an Apache Derby database as the database store for our UDDI registry. Use an embedded or network Apache Derby database, and the database store can be local or remote.
• Create a Microsoft SQL Server database for the UDDI registry
  Complete this task to use Microsoft SQL Server 2005, 2008 or 2008 R2 as the database store for our UDDI registry data.
• Create an Oracle database for the UDDI registry
  Complete this task to use Oracle as the database store for our UDDI registry data.

Use the UDDI registry installation verification test (IVT)

Create a data source for the UDDI registry

addNode command