WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

             Personalize the table of contents and search results

Uninstalling a fix pack, an interim fix, a test fix using the silent uninstall

This topic describes how to uninstall the fix pack, an interim fix, or a test fix using the silent installation option from the Update Installer.

Before you begin

[AIX HP-UX Linux Solaris Windows] Use the Update Installer program from the same user ID that installed the product that you are updating. Otherwise, the file ownership mismatches might require correction by the root user. See Using root or non-root when installing with the Update Installer for more information.

About this task

To uninstall using the Update Installer, the response file needs to be provided. Refer to the example response file, located at the bottom of this topic, for more details.

The following steps lead you through the process of uninstalling maintenance using the silent mode.

Procedure

  1. Edit a response file. The one located at the bottom of the pane can be used as an example.
  2. Specify the location of the product that will be uninstalled in the response file.
  3. Specify the choice of Uninstall maintenance in the response file.
  4. Specify the maintenance pack to be uninstalled in the response file.
    This is the same filename as the package that was originally installed. A maintenance package can only be uninstalled if a backup package exists, such as, -W backup.package="PQ20029.pak"
    Note: If no package is specified, a default of the last installed maintenance (#) package will be used.

    To uninstall a maintenance pack using the silent mode, the order of uninstalling needs to be in reverse order of installing.

    [AIX HP-UX Linux Solaris Windows] For more information, see Logic used by the Update Installer for uninstalling.

  5. Ensure that all running processes have been stopped.
  6. [i5/OS] Verify that the host server jobs are started on your iSeries server. The host server jobs allow the installation code to run on iSeries. Enter this command on a CL command line: STRHOSTSVR SERVER(*ALL).
  7. Launch the Update Installer.
  8. Review the log file to verify maintenance has been uninstalled successfully. The log can be found at WAS_HOME\logs\update\<Maintenance name.install>.

Results

One of the following results will appear in the log.
INSTCONFSUCCESS
The operation was a success.
INSTCONFPARTIALSUCCESS
The operation was partially successful, refer to the log for more details.
INSTCONFFAILED
The operation failed, refer to the log for more details.

Example

The following response file demonstrates how to uninstall a fix pack in the silent mode.

################################################################################
#
# This is the silent install response file for uninstalling maintenance packages
# using the update installer.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, *uncomment* and modify the parameters defined within.
#
# Use the following command line when running the wizard from the update 
# installer directory:
# 
#    update -options responsefiles/uninstall.txt -silent
#
# Enclose all values within a single pair of double quotes.
#
################################################################################


################################################################################
#
# Used to input the maintenance backup package filename to be uninstalled. 
# This is the same filename as the package that was originally installed.
# A maintenance package can only be uninstalled if a backup package exists.
#
# For example: -W backup.package="PQ20029.pak"
#
# Note: If you do not specify a package, then a default of the last installed maintenance 
#       package is used, as the following example demonstrate:
# 
-W backup.package="6.1.0.1-WEBSV-FEP-WinX32-FP000001.pak"


################################################################################
#
# Used to modify the product install location that will be updated. 
# This value should be left commented out if the Update Installer is 
# being run from the recommended location, as the following example demonstrates:
#
# For example: -W product.location="C:\Program Files\IBM\WebSphere\AppServer"
#
# Note: The product install location needs to be specified, and it needs to 
#       be the full path.
#
-W product.location="D:\IBM\WebSphere\AppServerNonroot3"


################################################################################
#
# AIX Non-root user limitation
#
# The AIX user account running the Update Installer program also must be able to 
# run the slibclean command; otherwise, a root user must run the slibclean command
# before the Update Installer program runs. 
#
# Uncomment the following option to notify the installer that a root user has run
# the slibclean command before the Update Installer program runs.
#
#-OPT rootUserHasRunSlibcleanCommandSuccessfully="true"


################################################################################
#
# Do not edit these values.
#
-W update.type="uninstall"



In this information ...


Related reference

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tins_updi_unsilfixpk.html