Reinstalling the UDDI registry application

 

Use this to remove the existing UDDI application and reinstall it with the existing UDDI database.

 

Overview

Perform this task if you wish to change the UDDI application code, but you want to continue to provide UDDI services with your existing UDDI database.

 

Procedure

1. Make a note of any changes that you made to the installed UDDI application that you wish to keep, for example changes to security role mappings, changes to the deployment descriptor (web.xml) in v3soap.war, v3gui.war, v3soap.war, or soap.war, or customization of the UDDI user interface (GUI). All such changes are lost during the reinstallation process; if there are changes that you wish to keep, reapply them later.

2. Run the wsadmin script uddiDeploy.jacl from the app_server_root/bin directory, as shown. Note the following points:

   • do not specify the default option, even if you used this option previously to set up a default UDDI node using Cloudscape. If you use the default option, you might encounter an error during deployment, or in some circumstances your existing UDDI data might be overwritten.

   • if you are deploying the UDDI registry into a network deployment scenario, ensure that the deployment manager is the target.

   At a command prompt, enter:

   wsadmin [-conntype none] [-profileName profile_name] –f uddiDeploy.jacl 
                  {node_name server_name | cluster} 
   

   where

   • '-profileName profile_name' is optional, and is the name of the profile in which the UDDI application is deployed. If you do not specify a profile, the default profile is used.

   • '-conntype none' is optional, and is needed only if the appserver or deployment manger is not running.

   • node_name and server_name are the names of the WebSphere node and appserver in which the UDDI application is deployed (these are the names specified when you ran uddiDeploy.jacl to install the UDDI application).

   • cluster is the name of the WebSphere cluster in which the UDDI application is deployed. This is the name specified when you ran uddiDeploy.jacl to install the UDDI application.

   Optionally, you can redirect the output from this command to a log file. To do this, add '> log_name.log' at the end of the command, where log_name.log is the name of the log file to create.

   The command removes the existing UDDI application and reinstalls it.

   This procedure does not change your existing JDBC provider, datasource and any J2C authdata entry. Your existing UDDI registry data, including UDDI entities as well as property and policy settings, are also unaffected.

3. If you noted any changes in step 1, reapply them now.

4. For the reapplied changes to take effect, start or restart the appserver.

---

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

Setting up and deploying a new UDDI registry
Setting up a default UDDI node
Setting up a customized UDDI node
Removing and reinstalling the UDDI registry