[AIX HP-UX Linux Solaris Windows]This topic applies only on the i5/OS operating system.

Installing an interim fix, interim feature, or test fix with silent install

This topic describes how to use the Update Installer for WebSphere Software to install the interim fix, interim feature, or test fix 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.

[AIX HP-UX Linux Solaris Windows] Use the Update Installer program from the same user ID that installed the product that you are updating. Otherwise, the file ownership mismatches might require correction by the root user. See Using root or non-root when installing with the Update Installer for more information.

[iSeries] Use the Update Installer program from a user profile with *ALLOBJ special authority.

About this task

The following steps lead you through the process of applying maintenance to an interim fix, interim feature, or test fix pack using the silent mode.

Procedure

  1. The most recent version of the Update Installer needs to be installed on a target system locally.
  2. Download the required interim fix, interim feature, or test fix pack from the official IBM support Web site into the updi_root/maintenance directory.
  3. Ensure that all running processes have been stopped.
  4. [iSeries] Verify that the host server jobs are started on your iSeries server. The host server jobs allow the installation code to run on iSeries.
    Enter this command on a CL command line:
    STRHOSTSVR SERVER(*ALL)
  5. Edit the response file. An example of a response file is located at the bottom of this article.
    1. The location of the product needs to be added to the response file.
    2. Specify the choice of Install maintenance in the response file.
    3. Add the maintenance location where packages can be found to the response file. The user enters the directory name containing the packages.

      In the response file, point to interim fix, interim feature, or test fix directory containing the package that needs to be installed.

      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.

  6. Run the Update Installer.

    For example:

    [Windows]
    update.bat -silent -options "responsefiles\file_name"
    [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later]
    update.exe -silent -options "responsefiles\file_name"
    [AIX] [HP-UX] [Linux] [Solaris]
    ./update.sh -silent -options "responsefiles/file_name"
    [iSeries]
    update -silent -options "responsefiles/file_name"
  7. Review the log to verify that the maintenance was applied successfully. The log can be found at app_server_root/logs/update/maintenance_package.install.

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 a sample of a response file used by the Update Installer to install an interim fix, interim feature, or test fix 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.1.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.1.0.1-WS-WAS-IFPK21009.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.
#
# 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="D:\Program Files\IBM\WebSphere\AppServer"



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



In this information ...


Related reference

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: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=tins_updi_silifixpk
File name: tins_updi_silifixpk.html