+

Search Tips   |   Advanced Search

Install fix packs silently


To install maintenance without the GUI, we can use the Update Installer for WebSphere Software to install a fix pack in silent mode.

Verify the most recent version of the Update Installer is installed on a target system locally.

Use the Update Installer program from the same user ID that installed WAS that we are updating. Otherwise, the file ownership mismatches might require correction by the root user. See Use root or non-root when installing with the Update Installer for more information.

 

  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 this page can be used as an example. There are also sample response files found in the updi_root/responsefiles directory.

    1. Specify the location of WAS 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.

  4. Run the Update Installer.

    For example:

    (Windows) 

    update.bat -silent -options "responsefiles\file_name"


    update.exe -silent -options "responsefiles\file_name"

    [AIX] [HP-UX] [Linux] [Solaris] 

    ./update.sh -silent -options "responsefiles/file_name"

  5. Review the log file to verify that maintenance is installed successfully. We can find the log at APP_ROOT/logs/update/maintenance_package.install. If the maintenance package is not applicable to the installation, a log file found in updi_root/logs/tempX lists the reason for the failure. The most recent log file, tmpX, where X refers to the first available empty directory, is created to reflect the status for this attempted install. You might not receive an error message for a failed installation in some cases. If we 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 under <Installed_UPDI_root>/responsefiles

 

Results

One of the following results appears 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. In some cases, we might not receive an error message for a failed installation. If we 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 under <Installed_UPDI_root>/responsefiles

 

Example

The following example is a sample response file used in a silent installation: 

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


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

 

Related


install.txt