WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Reinstalling the UDDI Registry application

Why and when to perform this task

Perform this task if you want to continue providing UDDI services with your existing UDDI database, but require that the UDDI application code be changed.

Steps for this task

  1. Make a note of any changes that you have 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 will be lost during the reinstallation process; any changes that you wish to keep will need to be reapplied later.
  2. Run the wsadmin script uddiDeploy.jacl from the install_root/bin directory, as shown, noting that:
    • You should not specify the default option even if you previously used this option 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] –f uddiDeploy.jacl 
                   node_name 
                   server_name 
    [Version 6.0.1 and later]
    wsadmin [-conntype none] –f uddiDeploy.jacl 
                   {node_name server_name | cluster_name} 
    where
    • '-conntype none' is optional, and is only needed if the application server or deployment manger is not running.
    • node_name and server_name are the names of the WebSphere node and application server in which the UDDI application is deployed (these are the names that you specified when you ran uddiDeploy.jacl to install the UDDI application).
    • [Version 6.0.1 and later]cluster_name is the name of the WebSphere cluster in which the UDDI application is deployed. This is the name that you specified when you ran uddiDeploy.jacl to install the UDDI application.

    The output from this command can optionally be redirected to a log file by adding '> log_name.log' at the end of the command, where log_name.log is the name of the log file to be created.

    The command removes the existing UDDI application and reinstalls it.

    Note: Your existing JDBC provider, datasource and any J2C authdata entry will be unchanged by this procedure . Your existing UDDI Registry data, including UDDI entities as well as property and policy settings, will also be unaffected.
  3. If you noted any changes in step 1, reapply them now.
  4. Start or restart the application server for the reapplied changes to take effect.



Related tasks
Setting up and deploying a new UDDI Registry
Setting up a default UDDI node with a default datasource
Setting up a default UDDI node
Setting up a customized UDDI node
Creating a DB2 database for the UDDI Registry
Creating a Cloudscape database for the UDDI Registry
Creating an Oracle database for the UDDI Registry
Using the UDDI Registry

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/twsu_reinstall.html

© Copyright IBM Corporation 2003, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)