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

install.txt

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

[AIX HP-UX Linux Solaris Windows] The Update Installer for WebSphere Software wizard reads the options file to determine installation choices. The Update Installer installs the maintenance package in silent mode instead of displaying a graphical user interface.

[i5/OS] The Update Installer for WebSphere Software wizard reads the options file to determine installation choices. The Update Installer installs the maintenance package in silent mode.

[AIX HP-UX Linux Solaris Windows] 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

[AIX HP-UX Linux Solaris Windows] The sample options 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.

[i5/OS] The sample options response file is named install.txt. The file is in the updi_root/responsefiles directory after you apply the latest WebSphere Application Server for i5/OS group PTF or after you install the Update Installer for WebSphere Software.

Installing silently

[AIX HP-UX Linux Solaris Windows] 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.

[i5/OS] The options file supplies the values to the Update installer wizard.

[AIX HP-UX Linux Solaris Windows] The following command uses a copy of the options file named myresponsefile.txt to provide installation option responses during a silent installation:
./update.sh -options "responsefiles/myresponsefile.txt" -silent
[AIX HP-UX Linux Solaris Windows] 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"
[i5/OS] The following command uses a copy of the options file named myresponsefile.txt to provide installation option responses during a silent installation:
update -options responsefiles/myresponsefile.txt
There is no need to specify the -silent parameter as it is already defined in the update script.

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

Location of the maintenance package to be installed
Default directive setting
-W maintenance.package=""
Valid setting
[AIX HP-UX Linux Solaris Windows] You must set this directive to the location of the maintenance package PAK file. For example, you might specify the following location on a Linux system:
/opt/IBM/WebSphere/AppServer/updateinstaller/maintenance/PQ20029.pak
[i5/OS] You might set this directive to the location of the maintenance package PAK file. If you do not specify a value for this setting, the default is the maintenance package located under updi_root/maintenance that has the most recent time stamp. For example, you might specify the following location if you are installing the iFix for APAR PQ20029.:
/qibm/proddata/WebSphere/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 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.
Product location
Default directive setting
-W product.location="SPECIFY_PRODUCT_INSTALL_LOCATION_HERE"
Valid setting
[AIX HP-UX Linux Solaris Windows] Set this directive to the installation root directory of the product. For example, you might specify the following location on a Linux system:
/opt/IBM/WebSphere/AppServer2
[i5/OS] Set this directive to the installation root directory of the product you want to update. For example, you might specify the following location:
/qibm/proddata/WebSphere/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 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

[AIX HP-UX Linux Solaris Windows] 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.

[i5/OS] The following example is not guaranteed to be an accurate representation of the actual file.

[AIX HP-UX Linux Solaris Windows]
################################################################################
#
# 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
#
# Please enclose all values within a single pair of double quotes.
#
################################################################################


################################################################################
#
# Used to input the maintenance package full filename specification to be installed. 
# Edit as appropriate.
#
# ie. -W maintenance.package="C:\Program Files\IBM\WebSphere\AppServer\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 input the product install location that will be updated.
#
# ie. -W product.location="C:\Program Files\IBM\WebSphere\AppServer"
#
# Note: The product 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="install"
[i5/OS]
################################################################################
#
# 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.
#
################################################################################


################################################################################
#
# Used to input the maintenance package full filename specification to be installed. 
# Edit as appropriate.
#
# ie. -W maintenance.package="/qibm/proddata/WebSphere/AppServer/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 input the product install location that will be updated.
#
# ie. -W product.location="/qibm/proddata/WebSphere/AppServer"
#
# Note: The product 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"



Reference 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/rins_updi_install61.html