Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - UDDI registry > Administer the UDDI registry


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:

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


Procedure

  1. Note any changes that you 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 reapply changes that you want to keep later.
  2. Remove the existing UDDI application and reinstall it by running the uddiDeploy.jacl wsadmin script from the WAS_HOME/bin directory. Do not use the default option even if you used this option previously to set up a default UDDI node. If you use the default option, an error might occur during deployment, or, in some circumstances, existing UDDI data might be overwritten.

    If you deploy the UDDI registry into a WAS ND configuration, ensure that the dmgr is the target.

    Enter the following command at a command prompt: 

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

    where:

    • -conntype none is optional, and is needed only if the application server or dmgr is not running.
    • -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 Application server node and the application server in which the UDDI application is deployed. These are the names specified when you 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 you 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 that you choose for the log file: 
    > log_name.log

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

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


Related


Create a DB2 distributed database for the UDDI registry
Create a DB2 for z/OS database for the UDDI registry
Create an Apache Derby database for the UDDI registry
Create an Oracle database for the UDDI registry
Remove a UDDI registry node
Set up and deploying a new UDDI registry
Set up a default UDDI node
Set up a customized UDDI node
Use the UDDI registry

+

Search Tips   |   Advanced Search