Changing the UDDI registry application environment after deployment

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.

Alternatively, 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 that is 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. 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.
  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, 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 JDBC providers > database_type > JDBC Provider > Data sources > uddi_datasource.
    3. Create the new database by referring to one of the following topics:
    4. 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.
    5. Create the new data source. See Creating a data source for the UDDI registry.
    6. Restart the UDDI registry application.
    7. Check that you can access your UDDI data, for example use the UDDI registry installation verification test, then delete the old database.



In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=twsu_base_to_nd
File name: twsu_change_env.html