Removing a UDDI Registry node

 

Overview

To completely remove a UDDI Registry node we need to remove the UDDI Registry application and delete the UDDI Registry database. However there may be situations where you only want to perform one of these tasks:

Removing the UDDI Registry application from an application server.

You might want to do this in order to reinstall the application because it has become corrupted for some reason, or to apply service. See also the topic on Reinstalling the UDDI Registry application.

Delete the UDDI Registry database

You might want to do this in order to use a different database product as the persistence store for your UDDI data, to delete all your UDDI Registry data in order to publish fresh data (for example, if you have completed a test cycle), or to cause the UDDI Registry node to re-initialize with new UDDI property settings (for example, to move from a default UDDI node to a customized UDDI node). Note that deleting a UDDI Registry database will cause all UDDI data for that UDDI Registry to be lost.

Completely removing a UDDI Registry node from an application server

You might want to do this in order to move the UDDI Registry to a different application server, or to remove a UDDI Registry that has been used for testing.

Depending on what you wish to achieve, complete one of the following steps:

 

Procedure

  1. Removing a UDDI Registry application

    To remove the UDDI application from an application server, run the wsadmin script uddiRemove.jacl, as shown, from the install_root/bin directory.

    The syntax of the command is as follows (this is a Windows platform example; for Unix or Linux platforms, add the .sh suffix to the wsadmin command): 

    wsadmin -f uddiRemove.jacl
               node 
               servername
               [default]
              

    wsadmin -f uddiRemove.jacl
               {node servername | cluster_name}
               [default]

where

Output will appear on the screen by default. To direct the output to a log file, add '> removeuddi.log' (where removeuddi.log can be any log name of your choice) to the end of the command.

For example, to remove the UDDI application from server 'server1' running in node 'MyNode' on a Windows system, and send any messages to the file removeuddi.log 

wsadmin -f uddiRemove.jacl MyNode server1 > removeuddi.log

To remove the UDDI application from cluster 'MyCluster' on a Windows system, and send any messages to the screen 

wsadmin -f uddiRemove.jacl MyCluster

Note: If running in a network deployment configuration, the command must be executed against the deployment manager profile.

  • Delete a UDDI Registry database

    Note that this will cause all UDDI data in that UDDI Registry to be destroyed.

    1. Stop the server that is hosting the UDDI Registry application.

    2. Delete the database:

      • For DB2, use the database facilities to delete the UDDI database.

      • For Oracle, delete the schemas IBMUDI30 and IBMUDS30.

      • For Cloudscape, delete the directory tree containing the UDDI database. By default, this will be located in install_root/profiles/profile/databases/com.ibm.uddi/UDDI30.

  • Completely removing a UDDI Registry node

    To completely remove a UDDI Registry node from an application server, we need to remove the UDDI registry application and database, and also the resources that were used to reference the UDDI Registry database.

    1. Run the uddiRemove.jacl script as described above, to remove the UDDI Registry application.

    2. Delete the UDDI Registry database, as described above.

    3. If you ran the uddiRemove script using the default option, the datasource and related objects have already been deleted so no further action is required. If the default option was not valid for your configuration, delete the following objects:

      • the UDDI datasource that references the UDDI Registry database (this was created when you set up the UDDI Registry).

      • any UDDI JDBC provider that was created (if you did not reuse an existing JDBC provider).

      • any J2C Authentication Data Entry that was created.