Change the UDDI registry application environment after deployment

We can evaluate a UDDI registry using one database, then put it into production using a different database. We can move from a stand-alone application server to a WAS Network Deployment cell.

1. To incorporate a stand-alone application server into a WAS 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.

2. 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. Do NOT use the default node options where specified:
   • Create a DB2 distributed 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 saved in the default node (policies, properties, and user data) is lost the database is deleted. 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 use for test purposes.

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

   1. Stop the UDDI registry application...
      Applications | Application Types | WebSphere enterprise applications | application (check box) | Stop

   2. Either change the JNDI name of the existing data source from datasources/uddids to another value, or delete the data source...
      Resources | JDBC | JDBC providers | database_type JDBC Provider | [Additional Properties] Data sources | uddi_datasource

   3. Create the new database...
      • Create a DB2 distributed 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 the 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.

   6. Restart the UDDI registry application.

   7. Check that we can access the 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
• 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

  
  

  Related tasks

  Use the UDDI registry installation verification test (IVT)
• Create a data source for the UDDI registry
• addNode command