If you want to install maintenance without the graphical user interface, you can use the Update Installer for WebSphere® Software to install a fix pack in silent mode.
Ensure that 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 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.
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 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="/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 the product install location that will be updated. # # ie. -W product.location="/QIBM/ProdData/WebSphere/AppServer/V61/Express" # # Note: The product install location should always been specified, and it should # always be the full path. # -W product.location="" ################################################################################ ################################################################################ # # File Permission Checking # # The installer does not check that it has sufficient file permissions to # perform the installation by default. # # Uncomment the following option to notify the installer that it should # check that it has sufficient file permissions to perform the required # install operation on each file to be installed. # # This option is not applicable for Windows. # # -OPT checkFilePermissions="true" # ############################################################################### ################################################################################ # # AIX Non-root User Limitation # # The AIX user account running the Update Installer program also must be able to # run the slibclean command; otherwise, a root user must run the slibclean command # before the Update Installer program runs. # # Uncomment the following option to notify the installer that a root user has run # the slibclean command before the Update Installer program runs. # #-OPT rootUserHasRunSlibcleanCommandSuccessfully="true" ################################################################################## # Do not edit these values. # -W update.type="install"
In this information ...Related reference
| IBM Redbooks, demos, education, and more(Index) |