WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Uninstalling WebSphere ESB for z/OS

Uninstall WebSphere® ESB for z/OS® by running the shell script zSMPInstall.sh with the keyword -uninstall. These instructions describe how to run the install script with the uninstall keyword from a OS/390® UNIX® command shell. Alternatively you can run the script and keyword from a prompt using telnet. These instructions assume you are using TSO, if you are using telnet use the equivalent commands. These instructions also assume that you have the default key mappings using the CTRL key to enter input. If you have changed this configuration, use whichever key you have mapped to enter information into TSO.

Before you begin

Note: There is no support for a partial or incremental uninstall.

Read the latest technote information on uninstalling WebSphere ESB for z/OS before running the uninstall script.

The WebSphere ESB for z/OS install process assumes that you have a working knowledge of z/OS UNIX System Services. Refer to the following documentation if you need more information:
Procedure
  1. Access the OS/390® UNIX® command shell. telnet into USS directly, or from TSO enter the TSO command OMVS at the ISPF Command Option 6 or TSO OMVS from any other ISPF panel. Once you are in the UNIX shell, a command prompt (usually a dollar ($) or pound (#) sign) indicates that the system is ready to accept input.
  2. Switch to the administrator user ID:
    su wsadmin
  3. Change to zos.config/bin in the product installation file system directory:
    cd /usr/lpp/zWESB/V6R2/zos.config/bin
  4. Add the current directory to the path:
    export PATH=.:$PATH
  5. From the command prompt, run the installation script with the uninstall command, for example:
    zSMPInstall.sh -smproot /wps/pathofWPScode/zWPS/V6R2 -runtime
     /WebSphere/V6R1M0/AppServer -uninstall -response
     /yourdrivename/yourfoldername/responsefilename.rsp

    Type in the absolute path name of the response file according to your system configuration. The path file names above assume the uninstaller is using the default response files. If the response file was customized, the path name must represent the absolute path of the customized file.

  6. Wait for the 'Configuration Manager for uninstall complete' message, and for the command prompt to return.

Results

Running the install script with the -uninstall parameter results in the following actions:

If any shared common components are being used by other applications the command line prompting warns that uninstalling the product may cause other applications to no longer function correctly.

If the uninstall command was not successful check the associated log file and trace files:
  • Standard out messages
    Standard output messages display directly on the screen. You can choose to redirect these messages to a file by using redirect symbol and a file name at the end of the command line. For example, adding the syntax >run.log to the end of the install command redirect the standard output messages to the file named run.log in the present working directory. The standard out messages display as follows:
    parsing command arguments...
    parsing arguments complete
    setting up configuration...
    runtimeRootDirName is: /WebSphere/V6R1M0/AppServer
    WAS_HOME is: /WebSphere/V6R1M0/AppServer
    WBI_HOME is: /WebSphere/V6R1M0/AppServer
    running Configuration Manager for uninstall...
    Configuration Manager for uninstall complete
    unaugmenting profile(s)...
    unaugmenting profile(s) complete
  • Log file

    Log messages are written to the zSMPInstall.log file in the run-time directory. The default location of this file is /WebSphere/V6R1M0/AppServer/logs/wbi/zSMPInstall.log.

  • Trace file

    Review the zSMPInstall.trace (ASCII) file in the run-time directory. The default location for this file is/WebSphere/V6R1M0/AppServer/logs/wbi/zSMPInstall.trace..

    There must be no error messages that have an "E" suffix..

You can also carry out the following troubleshooting actions:
  • Review the actions of the Update Configuration Manager task. The actions are written to the log file cmtInstall.log, which is in ASCII format. The default location for this file is /WebSphere/V6R0M0/AppServer/logs/wbi. Search in this log for the text >SEVERE< or >WARNING< level messages to determine which errors have occurred. Each Apache Ant script that runs from the install directory has a log that it writes to, which is in ASCII format.

    The default name of the directory that contains the Ant scripts is:/WebSphere/V6R1M0/AppServer/properties/version/install.wbi/6.0.0.0/config/full/uninstall. The resulting Ant logs are written to the product log directory. The default name for this directory is /WebSphere/V6R1M0/AppServer/logs/wbi. Ant logs include the following (review these logs to determine errors in processing) :

    • 90SDeleteFirstStepsFilesWBI.ant.log
    • 90SRemoveJavaOptions.ant.log
    • 90SUninstallCEI.ant.log
    • 98SUndeployBPCAdminConsolePlugins.ant.log
    • 98SUndeployServerAdminConsolePlugins.ant.log
    • 99SUndeployCoreAdminConsolePlugins.ant.log
    Each of these logs must contain a 'build successful' message when the uninstall has been successful.
  • Review the contents of the Unaugment Log. The unaugment profile task records the actions it has made by writing to a log file (ASCII). The log file name is wasprofile_unaugment_default.log.. The standard location for this file is /WebSphere/V6R0M0/AppServer/logs/wasprofile. Search this WebSphere Application Server profile augment log for >SEVERE< or >WARNING< level messages to determine overall error in processing. There should be no SEVERE messages.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tins_zos_rununinstall.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).