Preparing for reinstallation after failed uninstallation on HP-UX systems

This procedure cleans an HP-UX system if uninstallation of WebSphere Process Server fails. After running the uninstallation program, these manual steps remove registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not perform this task.

Before you begin

Before performing this procedure, ensure you have uninstalled WebSphere Process Server using the Uninstallation wizard or silently, and that the procedure was not completely successful. If the procedure was successful, you do not need to perform this task.

Determine the install_root directory for the product so that you remove the correct product and produce a clean system.

Default directories are shown in Table 1:

Table 1. Planning table for identifying actual location of product installation
Identifier Default directory location Actual location
install_root /opt/IBM/WebSphere/ProcServer or /opt/IBM/WebSphere/AppServer  
profile_root /opt/IBM/WebSphere/ProcServer/profiles /profile_name or /opt/IBM/WebSphere/AppServer/profiles /profile_name

A character space was added to these entries to enable them to fit in the table cell. The actual entries do not include a character space.

 
The Installation wizard and the Profile wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
  • The ~/.WBIRegistry file identifies the installation root for all installed WebSphere Process Server products; the ~/.WASRegistry file, for all WebSphere Application Server products. These files are located in the home directory of the user ID from which the product was installed.
  • The install_root/logs/wasprofile/wasprofile_create_profile_name.log file for each created profile identifies the installation location in the stanza with the <method>invokeWSProfile</method> tag.
Uninstalling the product leaves the profile_root directory, including the profile_root/logs directory with the pcatLog<timestamp>.txt file, where profile_root represents the installation location of the profile. It leaves the install_root/logs directory as well.

Why and when to perform this task

Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, you can delete all files and registry entries to completely remove WebSphere Process Server. A clean system lets you reinstall the product into the original directory without coexistence.

Important: Throughout this procedure, steps address removing artifacts left after uninstallation of both WebSphere Process Server and WebSphere Application Server or WebSphere Application Server Network Deployment. The WebSphere Application Server product addressed is assumed to be the one underlying the installation of WebSphere Process Server.

Perform the following procedure to produce a clean system.

Steps for this task

  1. Log on as root.
  2. Use the kill command to kill all Java processes that are running.
    If you are running Java processes that are not related to WebSphere Process Server or WebSphere Application Server products and it is not possible to stop them, stop all WebSphere Process Server and WebSphere Application Server product-related processes. Use the following command to determine all processes that are running:
    ps -ef | grep java
    Stop all WebSphere Process Server and WebSphere Application Server product-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.
  3. Use the HP-UX System Administration Manager (SAM) utility to remove packages.
    1. Start the SAM utility and verify that your DISPLAY and TERM environment variables are set properly.
    2. Select Software management.
    3. Select View installed software.
    4. Look for WebSphere Process Server, WebSphere Application Server, or IBM HTTP Server entries in the SD list.
    5. Close the SD list.
    6. Select Remove local host software.
    7. Select any of the following instances that are displayed in the SD Remove List:
      • WSEAA60
      • IBM HTTP Server
      • WSBAA60
      • WSPAA60
      • WSCAA
      • gsk7bas
    8. Select Actions > Mark for remove.
    9. Select Actions > Remove.
    10. Select OK in the Remove analysis dialog box.
    11. Select Logs to display real-time removal of selected packages.
    12. Select Done when all packages are removed.
    13. Exit SAM.
  4. Search for the packages to verify their removal.

    Type swlist | grep WS to show packages for WebSphere Process Server and WebSphere Application Server.

    To narrow your query to search for WebSphere Process Server packages only, type the following command:
    swlist | grep WSEAA60 
  5. Remove any profile directories that are not located in the installation root (install_root) directory.

    To determine the locations of profile directories, first use the wasprofile -listProfiles command to display profile names. Then, to determine where profile directories are located, use the wasprofile -getPath -profileName profile_name command, where profile_name is the name of the profile corresponding to a given directory.

  6. Remove the installation root directory.
    Type rm -rf install_root to remove WebSphere Process Server directories. Ensure you specify the correct install_root for the product you uninstalled. For example, if you uninstalled WebSphere Process Server from the default installation directory /opt/IBM/WebSphere/ProcServer, issue the following command:
    rm -rf /opt/IBM/WebSphere/ProcServer
  7. Edit the .WBIRegistry and .WASRegistry files. These files are located in the home directory of the user ID from which the product was installed.

    The .WBIRegistry file contains a one-line entry for each WebSphere Process Server product installation; the .WASRegistry file, for each WebSphere Application Server product installation.

    You can delete these files if there is just one line in each that identifies the product that you removed. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you removed. Leave the other lines intact. Do not delete the .WBIRegistry and .WASRegistry files unless you removed all of the installations listed in the files.

Result

This procedure results in having a clean system. You can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.

What to do next

After you have cleaned your system, go to Installing the software to choose an installation procedure.


Last updated: Wed 01 Nov 2006 07:47:12

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)