Change the UDDI registry application environment after deployment

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

After you deploy a UDDI registry application, we might want to change its environment. For example, we 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.

Alternatively, we might want to move from a standalone appserver to an ND cell.

 

1. To incorporate a standalone appserver into an ND cell, run addNode.sh that is included with WAS. Use the includeapps parameter to verify 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, ensuring that you do not use the default node options where specified:
   • Create a DB2 distributed 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 2005 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 appserver. The default UDDI node still exists for you to use for test purposes.

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

   1. Stop the UDDI registry application. Click Applications > Application Types > WebSphere enterprise apps, select the relevant check box, then click Stop.

   2. 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 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
      • 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 2005 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. See Create a data source for the UDDI registry.

   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.

Create a DB2 distributed 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 2005 database for the UDDI registry
Create an Oracle database for the UDDI registry

 

Related tasks

Use the UDDI registry installation verification test (IVT)
Set up and deploying a new UDDI registry

 

Related

addNode