Silently uninstalling fix packs, interim fixes, or test fixes

Use a response file to uninstall maintenance silently.

Use the Update Installer program from the same user ID that installed WAS that we are updating. Otherwise, the file ownership mismatches might require correction by the root user.

Refer to the example response file, located at the bottom of this topic, for more details.

Follow these steps to uninstall maintenance silently:

 

1. Edit a response file. Use the sample response file at the bottom of the pane as an example.

2. Specify the location of WAS 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"

   The commands for installing and uninstalling maintenance silently are different. Installation requires specifying the maintenance package using maintenance.package and uninstallation requires backup.package

   For example:

   • Install maintenance silently: update.bat -W maintenance.package="e: \IBM\WebSphere\AppServer \updateinstaller\maintenance\ PQ20029.pak"

   • Uninstall maintenance silently: update.bat -W backup.package="PQ20029.pak" -W update.type="uninstall"

   If no package is specified, a default of the last installed maintenance (#) package is used.

   To uninstall a maintenance pack using the silent mode, the order of uninstalling needs to be in the reverse order of installing. For example, if we installed maintenance packs A, B, and C in that order, you should uninstall C, B, and then A.

5. Ensure that all running processes have been stopped.

6. Launch the Update Installer and point to a response file.

7. Review the log file to verify maintenance has been installed 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 silently.

################################################################################
#
# 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"
#
# 
 If we 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 WAS install location that will be updated. 
# This value should be left commented out if the Update Installer is 
# being run from the recommended location...
#
# For example: -W product.location="C:\Program Files\IBM\WebSphere\AppServer"
#
# 
 WAS ND v7.0 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"

---

 

Related tasks

Install maintenance packages, interim fixes, fix packs, and refresh packs