+

Search Tips   |   Advanced Search

 

uninstall.txt

 

The Update Installer for WebSphere Software can use an options response file to uninstall maintenance packages from a command line interface.

The uninstall.txt file has one directive that identifies the backup file for uninstalling a service update. Comments in the file describe how to set the string value.

The Update Installer for WebSphere Software wizard reads the options file to determine uninstall choices. The Update Installer uninstalls the maintenance package in silent mode, instead of displaying a graphical user interface.


 

Related tasks


Uninstall maintenance packages

 

Related Reference

 

Location of the response file

The sample options response file is named uninstall.txt. The file is in the updi_root/responsefiles directory after you unzip the Update Installer for WebSphere Software into the installation root directory of the WebSphere software product.

 

Uninstall silently

The options file supplies the values to the Update installer wizard when uninstalling silently. The wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt to provide uninstall option responses during a silent uninstall:

./update.sh -options "responsefiles/myresponsefile.txt" -silent

If you do not use the -silent option, the wizard uses the response file to provide initial values for the graphical interface:

./update.sh -options "responsefiles/myresponsefile.txt"

 

Response file user entry validation

In a silent uninstall, response file validation has been coded into the uninstall process. If the validation does not pass, the failure is recorded in the log files in the app_server_root/logs/update/tmp directory.

Location of the maintenance package to be uninstalled

Default directive setting

-W backup.package=""

Valid setting

Set this directive to the location of the backup file. The backup file reverses the application of the maintenance. For example, you might specify the following location on a Linux system:

/opt/properties/version/nif/backup/maintenance_package_to_uninstall

Error identifiers:

  • The maintenance package cannot be uninstalled. Uninstalling the maintenance would break the following superseding maintenance packages. Uninstall the superseding maintenance packages first: list_of_superseding_maintenance_packages

  • This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the package that you are attempting to uninstall: list_of_dependent_maintenance_packages

  • This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the APARs you are attempting to uninstall: list_of_dependent_maintenance_packages

  • No installation backup packages are available for uninstalling maintenance.

Product location

Although uninstalling maintenance from another product is possible, always use the Update installer wizard from the directory structure of the product that you are updating if possible. Problems can occur when a mismatch between product SDKs occurs, for example.

Do not use this directive unless absolutely necessary.

Default directive setting

-W product.location="SPECIFY_PRODUCT_INSTALL_LOCATION_HERE"

Valid setting

Set this directive to the installation root directory of the alternate product. For example, you might specify the following location on a Linux system:

/opt/IBM/WAS/AppServer2

Error identifiers:

  • The maintenance package cannot be uninstalled. Uninstalling the maintenance would break the following superseding maintenance packages. Uninstall the superseding maintenance packages first: list_of_superseding_maintenance_packages

  • This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the package that you are attempting to uninstall: list_of_dependent_maintenance_packages

  • This maintenance package cannot be uninstalled. The following maintenance packages are dependent on the APARs you are attempting to uninstall: list_of_dependent_maintenance_packages

  • No installation backup packages are available for uninstalling maintenance.

 

Usage notes

 

Example uninstall.txt file

Edit the version of the file that is included in the Update Installer for WebSphere Software ZIP file. The following example is not guaranteed to be an accurate representation of the actual file.

################################################################################
#
# 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
#
# Please 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.
#
# ie. -W backup.package="PQ20029.pak"
#
#

If no package is specified, a default of the last installed maintenance # package will be used. # #-W backup.package="" ################################################################################ # # 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 # # ie. -W product.location="C:\Program Files\IBM\WebSphere\AppServer" # #

WAS install location should always been specified, and it should # always be the full path. # -W product.location="<SPECIFY_PRODUCT_INSTALL_LOCATION_HERE>" ################################################################################ # # Do not edit these values. # -W update.type="uninstall"

 

Reference topic