WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Sample options response file: install.txt

You can install an update silently using the options response file.

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.

The Update Installer for WebSphere Software 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 for a silent installation:

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

If you do not use the -silent option, the response file provides initial values for the graphical interface.

Important: Throughout this topic, certain directory paths are shown only in Linux and UNIX format for simplicity. The equivalent Windows paths are identical except for the direction of the slashes.

Location of the response file

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

Installing silently

The options file supplies the values to the Update Installer Wizard when installing 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 for a silent installation:

update -options "myresponsefile.txt" -silent

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 install_root/logs/update/tmp directory.

Location of the maintenance package to be installed
Default directive setting
-W maintenance.package=""
Valid setting
You must set this directive to the location of the PAK file. For example, you might specify the following location on a Linux system:
install_root/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 you 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 location

Although applying maintenance to another product is possible, always use the Update Installer Wizard within the directory structure of the product that you are updating. Do not use this directive unless absolutely necessary.

Default directive setting
-W product.location=""
Valid setting
You must 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/WebSphere/ProcServer2
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 you 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 file that is included in the Update Installer for WebSphere Software zipped 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 -silent
#
################################################################################
################################################################################
#
# Used to input the maintenance package full filename specification to be installed. 
# Edit as appropriate.
#
# ie. -W maintenance.package="C:\Program Files\IBM\WebSphere\ProcServer\
#          updateinstaller\maintenance\PQ20029.pak"
#
# Note: If no package is specified, a default of the last downloaded maintenance 
# package will be used (based on timestamp).
#
#-W maintenance.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\ProcServer"
#
# Note: If no location is specified, the parent directory to update installer 
# will be used as default
#
#-W product.location=""
################################################################################
#
# Do not edit these values.
#
#
-W update.type="install"

Reference topic

Terms of Use | Rate this page

Timestamp iconLast updated: 12 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\rins_rf_apply_service.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)