+

Search Tips   |   Advanced Search

install.txt


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

The Update Installer for WebSphere Software reads the response file to determine installation choices. The Update Installer installs the maintenance package in silent mode instead of displaying a GUI.

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

Location of the response file


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

Install silently


The response file supplies the values to the Update installer when installing silently. The Update Installer reads the response file to determine responses and does not display the GUI.

The following command uses a copy of the response file named myresponsefile.txt to provide installation option responses during a silent installation: 

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

If we 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 installation, response file validation is coded into the installation. If the validation does not pass, the failure is recorded in the log files in the APP_ROOT/logs/update/tmp directory.

Location of the maintenance package to be installed

Default directive setting

-W maintenance.package=""

If no package is specified, maintenance packages from the default folder (such as, UpdateInstaller_HOME\maintenance) are installed.

Valid setting

Set this directive to the location of the maintenance package PAK file. For example, we might specify the following location on a Linux system: 

/IBM/WAS/AppServer/updateinstaller/maintenance/PQ20029.pak

Error identifiers:

  • Maintenance package maintenance_package_name is already installed on the system.

  • Selected product is not supported.

  • Configuration failed. The config action that failed was: configuration_action.

  • Install the following prerequisite APARs before installing the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ install

  • Install the following prerequisite maintenance packages before installing the package we are currently attempting to install: list_ of_ prerequisite_ maintenance_ packages_ to_ install

  • Uninstall the following APARs before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall

  • Uninstall the following maintenance packages before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall

  • Unable to locate the correct version of the_update_installer. Looking for version version_identifier.

  • Maintenance_package is not a valid maintenance package.

Product location

Default directive setting

-W product.location="SPECIFY_PRODUCT_INSTALL_LOCATION_HERE"

Valid setting

Set this directive to the installation root directory of WAS ND. For example, we might specify the following location on a Linux system: 

/IBM/WAS/AppServer2

Error identifiers:

  • Maintenance package maintenance_package_name is already installed on the system.

  • Selected product is not supported.

  • Configuration failed. The config action that failed was: configuration_action.

  • Install the following prerequisite APARs before installing the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ install

  • Install the following prerequisite maintenance packages before installing the package we are currently attempting to install: list_ of_ prerequisite_ maintenance_ packages_ to_ install

  • Uninstall the following APARs before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall

  • Uninstall the following maintenance packages before applying the current maintenance to the target product: list_ of_ prerequisite_ maintenance_ packages_ to_ uninstall

  • Unable to locate the correct version of the_update_installer. Looking for version version_identifier.

  • Maintenance_package is not a valid maintenance package.

  • Alternate_product_directory could not be validated as an existing directory.

Usage notes


Example install.txt file


Edit the version of the response 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 installing 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/install.txt
#
# Please enclose all values within a single pair of double quotes.
#
################################################################################


################################################################################
#
# This section describes how to apply a maintenance package using the full filename specifications to be installed. 
# There are three ways we can specify installing a maintenance package.  They are the following:
# (Use the examples below and edit where appropriate.)
#
# 1. Specify a single maintenance package full filename to be installed.
# 
#    For example:
#    -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak"
#
# 2. Specify a multiple maintenance package full filename to be installed. 
#    -  Use a semicolon to separate the full filename specifications.
#    -  Update Installer will install the latest applicable maintenance in the order listed. 
#
#    For example:  
#    -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20029.pak;
#    /QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance/PQ20030.pak";"
#
# 3. Specify a full folder name that contains the maintenance packages.
#    Update Installer will install the latest applicable maintenance in the order listed in the folder.
#
#    For example:
#    -W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance"
#
# Notes: If no package is specified, maintenance packages from the default folder (such as, UpdateInstaller_HOME\maintenance )
#        will be installed.
#
#-W maintenance.package=""


################################################################################
# 
# Prerequisite Checking
# 
# The update installer checks the system for prerequisites by default.
# 
# Uncomment the following option to notify the installer to continue with
# the update and log the warnings even though prerequisite checking
# failed.
# 
#-OPT disableNonBlockingPrereqChecking="true"


################################################################################
#
# Used to input WAS install location that will be updated.
#
# ie. -W product.location="/QIBM/ProdData/WebSphere/AppServer/V61/Express"
#
# 

 WAS ND v7.0 install location should always been specified, and it should
# always be the full path.
#
-W product.location=""



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



Related information


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