Installing a fix pack with silent install

This topic describes how to use the Update Installer for WebSphere Software to install the fix pack using the silent install option.

Before you begin

The most recent version of the Update Installer needs to be installed on a target system locally.

About this task

The most recent version of the Update Installer needs to be installed on a target system locally.

Procedure

  1. Download the required fix pack from the official IBM support Web site into the updi_root/maintenance directory.
  2. Ensure that all running processes have been stopped.
  3. Edit a response file. The one located at the bottom of the pane can be used as an example. There are also sample response files found in the updi_root/responsefiles directory.
    1. Specify the location of the product to the response file.
    2. Specify the choice of install maintenance in the response file. For example: -W update.type="install"
    3. Add the maintenance location where packages can be found to the response file.

      When you install the fix pack, certain logic is used to determine which packages to install. To find out more, refer to "Logic that the Update Installer uses for system recommended installations," found at the bottom of this topic.

  4. Run the Update Installer.

    For example:

    [Windows]
    update.bat -silent -options "responsefiles\file_name"
    [AIX] [HP-UX] [Linux] [Solaris]
    ./update.sh -silent -options "responsefiles/file_name"
  5. Review the log file to verify maintenance has been installed successfully. The log can be found at app_server_root/logs/update/maintenance_package.install. If for some reason the maintenance package is not applicable to install, a log file found in updi_root/logs/tempX will list the reason for the failure. The most recent log file, tmpX, where X refers to the first available empty directory, will be created to reflect the status for this attempted install. You might not receive an error message for a failed installation in some cases. If you silently install a maintenance package and you do not receive a response after a short period of time, view the logs. If logs are not generated, then an invalid or missing argument might be causing the installation to fail. Verify the Update Installer syntax for the command line with the response files install.txt and uninstall.txt, located in updi_root/responsefiles

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 is an sample response file used by the Update Installer to install a fix pack using the silent installer.

################################################################################
#
# 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.
#
################################################################################


################################################################################
#
# This section describes how to apply a maintenance package using the full 
# filename specifications to be installed. 
# There are three ways you 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="C:\Program Files\IBM\WebSphere\AppServer\UpdateInstaller\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="C:\maintenance\PQ20029.pak;C:\maintenance\PK31008.pak;D:\6.0.0-WS-WAS-WinX32-FP0000001.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="D:\UpdateInstaller\maintenance"
#
# Notes: If no package is specified, maintenance packages from the default folder 
# (such as, UpdateInstaller_HOME/maintenance )
#        will be installed.
#
-W maintenance.package="D:\UpdateInstaller\maintenance\6.0.0-WS-WAS-WinX32-FP0000001.pak"


################################################################################
# 
# 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 the product install location that will be updated.
#
# such as, -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="D:\Program Files\IBM\WebSphere\AppServer"



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



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tins_updi_silfixpk
File name: tins_updi_silfixpk.html