Reinstalling the UDDI registry application

We can remove and reinstall an existing UDDI registry application to change the UDDI application code but continue to provide UDDI services with the existing UDDI database.

A UDDI registry node consists of the following elements:

• A Java EE application.
• A store of data that is referred to as the UDDI database. The UDDI database uses a relational database management system.
• A way to connect the application to the data (a data source and related elements).

All the data that relates to UDDI is stored in the UDDI database and therefore that data exists, regardless of the UDDI application. Therefore, we can remove a UDDI registry node from the application server without deleting the database, then reinstall the UDDI registry application. We might do this if an application is corrupted, or to apply service changes.

Tasks

1. Note any changes that made to the installed UDDI application to keep, for example changes to security role mappings, changes to the deployment descriptor (web.xml) in the v3soap.war, v3gui.war, v3soap.war, or soap.war files, or customization of the UDDI user interface (GUI). All such changes are lost during the reinstallation process, so we must reapply changes to keep later.

2. Remove the existing UDDI application and reinstall it by running the uddiDeploy.jacl wsadmin script from the app_server_root/bin directory. Do not use the default option even if we used this option previously to set up a default UDDI node. If we use the default option, an error might occur during deployment, or, in some circumstances, existing UDDI data might be overwritten.

   If we deploy the UDDI registry into a WebSphere Application Server, Network Deployment configuration, ensure that the deployment manager is the target.

   Enter the following command at a command prompt:

   wsadmin [-conntype none] [-profileName profile] -f uddiDeploy.jacl 
            {node server | cluster_name} 
   

   (ZOS)

   wsadmin.sh [-conntype none] [-profileName profile] -f uddiDeploy.jacl 
              {node server | cluster_name} 
   

   where:

   • -conntype none is optional, and is needed only if the application server or deployment manager is not running.
   • -profileName profile is optional, and is the name of the profile in which the UDDI application is deployed. If we do not specify a profile, the default profile is used.
   • node and server are the names of the WebSphere Application server node and the application server in which the UDDI application is deployed. These are the names specified when we ran the uddiDeploy.jacl script to install the UDDI application.
   • cluster_name is the name of the WAS cluster in which the UDDI application is deployed. This is the name specified when we ran the uddiDeploy.jacl script to install the UDDI application.

   This procedure does not change the existing JDBC provider, data source and any J2EE Connector Architecture (J2C) authentication data entry. Your existing UDDI registry data, including UDDI entities, property settings, and policy settings, are also unaffected.

3. Optional: To direct the output to a log file, add the following option to the end of the command, where log_name.log can be any name chosen for the log file:

   > log_name.log
   

4. If we noted any changes in step 1, reapply them now.

5. For the reapplied changes to take effect, start or restart the application server.

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.

Removing a UDDI registry node

Set up and deploying a new UDDI registry

Set up a default UDDI node

Set up a customized UDDI node