Removing a UDDI registry node

Removing a UDDI registry node

You can remove a UDDI registry node completely, or just remove the UDDI registry application, delete the UDDI registry database, or move a UDDI registry to another server or profile.

Overview
To remove a UDDI registry node completely, remove the UDDI registry application and delete the UDDI registry database. However, there might be situations where you want to perform only one of these tasks:

Removing the UDDI registry application from an appserver.

You might want to do this to reinstall the application, either because it has become corrupted, or to apply service. See also Reinstalling the UDDI registry application.

Deleting the UDDI registry database

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

Moving a UDDI registry to another server or profile

You might want to do this after you create a new profile and you want to move the UDDI registry to the new profile.

Completely removing a UDDI registry node from an appserver

You might want to do this to remove a UDDI registry that was used for testing.

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

Procedure
Removing a UDDI registry application
To remove the UDDI application from an appserver, run the wsadmin script uddiRemove.jacl, as shown, from the app_server_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):
If running in a network deployment configuration, the command must be run using the deployment manager profile.
wsadmin [-profileName profile_name] -f uddiRemove.jacl
               {node_name server_name | cluster}
               [default]
              
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.

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.

'default' is optional and is applicable only for Cloudscape in a standalone appserver environment, and then only if the default option was used when the uddiDeploy.jacl script was run to deploy the UDDI registry. Specifying default will remove the UDDI Cloudscape datasource but not the UDDI Cloudscape database.

By default, output appears on screen. 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 -profileName myProfile -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 -profileName myProfile -f uddiRemove.jacl MyCluster
You can also remove the UDDI registry application using the console in the usual way, by selecting the application in the Enterprise Applications view and clicking Uninstall.
Deleting a UDDI registry database Note that this action destroys all UDDI data in that UDDI registry.

Stop the server that is hosting the UDDI registry application.

Delete the database:

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

For Oracle, delete the schemas IBMUDDI, IBMUDI30 and IBMUDS30.

For Cloudscape, delete the directory tree containing the UDDI database. By default, this directory tree is located in profile_root/databases/com.ibm.uddi/UDDI30.

Moving a UDDI registry to another server or profile

Verify the UDDI database will still be accessible. For example, if you are using a remote database, make sure that the new server can access it. If your database will not be accessible, or it will be deleted after the move, copy it to a new, accessible location. For example, if you want to move the UDDI registry to a new profile and then delete the old profile, any databases stored in the profile (such as a Cloudscape database created as part of the creation of a default UDDI node) will also be deleted.

Remove the UDDI registry application by running the uddiRemove.jacl script as described above.

If you ran the uddiRemove.jacl script using the default option, the datasource and related objects have already been deleted. If the default option was not valid for the 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.

In the new server create a J2C authentication data entry (if appropriate), JDBC provider and datasource, to reference the existing database (for more information see the relevant steps in Setting up a customized UDDI node).

Deploy the UDDI registry application as described in Deploying the UDDI registry application, noting that you should not specify the default option even if you previously used this option to set up a default UDDI node. If you use the default option, you might encounter an error during deployment, or in some circumstances your existing UDDI data might be overwritten.
The UDDI node name will remain the same as before. If the UDDI node name included the node name and server name of the original server, there will be a mismatch between the UDDI node name and the node name and server name of the new server. However this name mismatch will not affect the functioning of the UDDI registry node.

Check that the UDDI data can be accessed. If you are using a copy of the original UDDI registry database, you can now delete the original as described above.

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

Remove the UDDI registry application by running the uddiRemove.jacl script as described above.

Delete the UDDI registry database, as described above.

If you ran the uddiRemove.jacl 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 the 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.
Related tasks

Removing and reinstalling the UDDI registry