Install the latest UpdateInstaller once on a machine, then use that to install any updates (fix packs, refresh packs) to WAS, IHS and Plug-in
1. Download Websphere UpdateInstaller from the official IBM Site
http://www-01.ibm.com/support/docview.wss?uid=swg24020212
2. Extract the installer
[websphe@middleware updatetemp]$ unzip 7.0.0.29-WS-UPDI-LinuxIA32.zip
[websphe@middleware updatetemp]$ cd UpdateInstaller/
[websphe@middleware UpdateInstaller]$ ls -ltr
-rw-r--r-- 1 websphe dba 183 May 26 2013 version.txt
-rwxr-xr-x 1 websphe dba 13123 May 26 2013 install
drwxr-xr-x 2 websphe dba 4096 May 26 2013 framework
-rw-r--r-- 1 websphe dba 18961789 May 26 2013 updi.updi.pak
drwxr-xr-x 3 websphe dba 4096 May 26 2013 updi.primary.pak
-rw-r--r-- 1 websphe dba 14075908 May 26 2013 setup.jar
-rwxr-xr-x 1 websphe dba 1120 May 26 2013 relabel_java.sh
drwxr-xr-x 2 websphe dba 4096 May 26 2013 panels
drwxr-xr-x 2 websphe dba 4096 May 26 2013 lib
drwxr-xr-x 2 websphe dba 4096 May 26 2013 lafiles
-rw-r--r-- 1 websphe dba 6866 Nov 20 23:11 responsefile.updiinstaller.txt
3. Customize that response file parameters according to your environment.
You can find the original response file (responsefile.updiinstaller.txt) inside UpdateInstaller folder in update setup. Take a backup of that file and open and edit the response file parameters according to your environment. The minimum lines required for installing UpdateInstaller are given below.
-OPT silentInstallLicenseAcceptance="true"
-OPT allowNonRootSilentInstall="true"
-OPT installLocation="/u05/local/opt/was/was70/UpdateInstaller"
4. Execute that response file by using a command
syntax :: install -options responsefile.updiinstaller.txt -silent
[websphe@middleware UpdateInstaller]$ ./install -options /home/websphe/Desktop/was70/updates/updatetemp/UpdateInstaller/responsefile.updiinstaller.txt -silent
5. verify the installation
Check for a message INSTCONFSUCCESS in a log file called updateconfig.log if the installation is completed successfully. the updateconfig.log located in /WAS_HOME/ logs/update/install
[websphe@middleware update]$ pwd
/u05/local/opt/was/was70/logs/update
[websphe@middleware update]$ ls -ltr
total 24
-rwxrwxrwx 1 websphe dba 8570 Nov 20 21:10 updateconfig.log
-rwxrwxrwx 1 websphe dba 8598 Nov 20 21:10 updateconfigCIM.log
INSTCONFSUCCESS message in updateconfig.log as below.
<message>Returning with return code: INSTCONFSUCCESS</message>
UpdateInstaller has installed successfully, now you can apply fix packs/refresh packs to WAS , IHS or plug-in.
Apply a fix-pack to WAS
1. Check the current version of WebSphere by using ‘versioninfo.sh’
/WAS_HOME/bin/versionInfo.sh
[websphe@middleware bin]$ ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.26, dated 8/9/08
--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------
Report at date and time November 20, 2015 11:19:53 PM PST
Installation
--------------------------------------------------------------------------------
Product Directory /u05/local/opt/was/was70
Version Directory /u05/local/opt/was/was70/properties/version
DTD Directory /u05/local/opt/was/was70/properties/version/dtd
Log Directory /u05/local/opt/was/was70/logs
Backup Directory /u05/local/opt/was/was70/properties/version/nif/backup
TMP Directory /tmp
Product List
--------------------------------------------------------------------------------
ND installed
Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 7.0.0.0
ID ND
Build Level r0835.03
Build Date 8/31/08
Architecture Intel (32 bit)
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
2. Stop all process that users installations
like dmgr , nodes and applications servers
3. Make sure the .pak file is available under maintenance directory.
[websphe@middleware maintenance]$ pwd
/u05/local/opt/was/was70/UpdateInstaller/maintenance
[websphe@middleware maintenance]$ ls -ltr
-rw-r--r-- 1 websphe dba 718834707 Nov 20 23:21 7.0.0-WS-WAS-LinuxX32-FP0000029.pak
-rw-r--r-- 1 websphe dba 84327167 Nov 20 23:21 7.0.0-WS-WASSDK-LinuxX32-FP0000029.pak
4. Customize the response file parameters
[websphe@middleware maintenance]$ cd /u05/local/opt/was/was70/UpdateInstaller/responsefiles/
[websphe@middleware responsefiles]$ ls -ltr
-rwxr-xr-x 1 websphe dba 3064 Nov 20 23:11 uninstall.txt
-rwxr-xr-x 1 websphe dba 4275 Nov 20 23:11 install.txt
You can find the original response file (install.txt) inside responsefiles folder in UpdateInstaller. Take a backup of that file and open and edit the response file parameters according to your requirement . The minimum lines required for installing UpdateInstaller are given below.
-OPT checkFilePermissions="true"
-W maintenance.package="/u05/local/opt/was/was70/UpdateInstaller/maintenance"
(This parameter specify a full folder name that contains the maintenance packages)
-OPT rootUserHasRunSlibcleanCommandSuccessfully="true"
-W product.location="/u05/local/opt/was/was70"
-W update.type="install"
5. Execute update execute file
[websphe@middleware UpdateInstaller]$ ./update.sh -options=/u05/local/opt/was/was70/UpdateInstaller/responsefiles/install.txt -silent
Executing command: /u05/local/opt/was/was70/UpdateInstaller/java/jre/bin/java -cp /u05/local/opt/was/was70/UpdateInstaller/update.jar -Xms48m -Xmx384m run -options /u05/local/opt/was/was70/UpdateInstaller/responsefiles/install.txt -silent
Check the installation status of fix pack or refresh pack in a log file named by log.txt.
If the installation is success we will get a message “INSTCONFSUCCESS”
[websphe@middleware install]$ pwd
/u05/local/opt/was/was70/UpdateInstaller/logs/install
[websphe@middleware install]$ ls -ltr
total 96
-rw-r--r-- 1 websphe dba 4034 Nov 20 23:11 trace.xml.gz
-rw-r--r-- 1 websphe dba 2457 Nov 20 23:11 trace.txt.gz
-rw-r--r-- 1 websphe dba 26 Nov 20 23:11 relabel.stdout.gz
-rw-r--r-- 1 websphe dba 26 Nov 20 23:11 relabel.stderr.gz
-rw-r--r-- 1 websphe dba 17207 Nov 20 23:11 log.txt
-rw-r--r-- 1 websphe dba 56032 Nov 20 23:11 installconfig.log.gz
[websphe@middleware install]$ view log.txt
------------------------------------
--------------------------------
(Nov 20, 2015 11:11:57 PM), Install, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: 90SCreateEmptyUPDIDirs, percent complete: 100%
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=0
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS
Now check the current version of WAS, and start your process
[websphe@middleware bin]$ ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.5.1, dated 6/15/11
-------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------
Report at date and time November 20, 2015 11:43:28 PM PST
Installation
--------------------------------------------------------------------------------
Product Directory /u05/local/opt/was/was70
Version Directory /u05/local/opt/was/was70/properties/version
DTD Directory /u05/local/opt/was/was70/properties/version/dtd
Log Directory /u05/local/opt/was/was70/logs
Backup Directory /u05/local/opt/was/was70/properties/version/nif/backup
TMP Directory /tmp
Product List
--------------------------------------------------------------------------------
ND installed
Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 7.0.0.29
ID ND
Build Level cf291321.01
Build Date 5/26/13
Architecture Intel (32 bit)
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
[websphe@middleware bin]$
*******************************************************************
SAMPLE INSTALL.TXT FOR FIX PACK UPDATE :
#########################################################
# 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
#
#########################################################
# Used to input the maintenance package full filename
# specification to be installed.
# Edit as appropriate.
#
# ie. -W maintenance.package="C:\Program
# Files\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 time stamp).
#
#-W maintenance.package=
#########################################################
# Used to modify the product install location that will
# be updated.
# This value should be left commented out if the Update
# Installer is
# being run from the recommended location
#
# ie. -W product.location=
# "C:\Program Files\WebSphere\AppServer"
#
# Note: If no location is specified, the parent
# directory to update installer
# will be used as default
#
#-W product.location=""
#########################################################
# Do not edit these values.
#
#
-W update.type="install"
*******************************************************************
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
#
# 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"
1. Download Websphere UpdateInstaller from the official IBM Site
http://www-01.ibm.com/support/docview.wss?uid=swg24020212
2. Extract the installer
[websphe@middleware updatetemp]$ unzip 7.0.0.29-WS-UPDI-LinuxIA32.zip
[websphe@middleware updatetemp]$ cd UpdateInstaller/
[websphe@middleware UpdateInstaller]$ ls -ltr
-rw-r--r-- 1 websphe dba 183 May 26 2013 version.txt
-rwxr-xr-x 1 websphe dba 13123 May 26 2013 install
drwxr-xr-x 2 websphe dba 4096 May 26 2013 framework
-rw-r--r-- 1 websphe dba 18961789 May 26 2013 updi.updi.pak
drwxr-xr-x 3 websphe dba 4096 May 26 2013 updi.primary.pak
-rw-r--r-- 1 websphe dba 14075908 May 26 2013 setup.jar
-rwxr-xr-x 1 websphe dba 1120 May 26 2013 relabel_java.sh
drwxr-xr-x 2 websphe dba 4096 May 26 2013 panels
drwxr-xr-x 2 websphe dba 4096 May 26 2013 lib
drwxr-xr-x 2 websphe dba 4096 May 26 2013 lafiles
-rw-r--r-- 1 websphe dba 6866 Nov 20 23:11 responsefile.updiinstaller.txt
3. Customize that response file parameters according to your environment.
You can find the original response file (responsefile.updiinstaller.txt) inside UpdateInstaller folder in update setup. Take a backup of that file and open and edit the response file parameters according to your environment. The minimum lines required for installing UpdateInstaller are given below.
-OPT silentInstallLicenseAcceptance="true"
-OPT allowNonRootSilentInstall="true"
-OPT installLocation="/u05/local/opt/was/was70/UpdateInstaller"
4. Execute that response file by using a command
syntax :: install -options responsefile.updiinstaller.txt -silent
[websphe@middleware UpdateInstaller]$ ./install -options /home/websphe/Desktop/was70/updates/updatetemp/UpdateInstaller/responsefile.updiinstaller.txt -silent
5. verify the installation
Check for a message INSTCONFSUCCESS in a log file called updateconfig.log if the installation is completed successfully. the updateconfig.log located in /WAS_HOME/ logs/update/install
[websphe@middleware update]$ pwd
/u05/local/opt/was/was70/logs/update
[websphe@middleware update]$ ls -ltr
total 24
-rwxrwxrwx 1 websphe dba 8570 Nov 20 21:10 updateconfig.log
-rwxrwxrwx 1 websphe dba 8598 Nov 20 21:10 updateconfigCIM.log
INSTCONFSUCCESS message in updateconfig.log as below.
<message>Returning with return code: INSTCONFSUCCESS</message>
UpdateInstaller has installed successfully, now you can apply fix packs/refresh packs to WAS , IHS or plug-in.
Apply a fix-pack to WAS
1. Check the current version of WebSphere by using ‘versioninfo.sh’
/WAS_HOME/bin/versionInfo.sh
[websphe@middleware bin]$ ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.26, dated 8/9/08
--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------
Report at date and time November 20, 2015 11:19:53 PM PST
Installation
--------------------------------------------------------------------------------
Product Directory /u05/local/opt/was/was70
Version Directory /u05/local/opt/was/was70/properties/version
DTD Directory /u05/local/opt/was/was70/properties/version/dtd
Log Directory /u05/local/opt/was/was70/logs
Backup Directory /u05/local/opt/was/was70/properties/version/nif/backup
TMP Directory /tmp
Product List
--------------------------------------------------------------------------------
ND installed
Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 7.0.0.0
ID ND
Build Level r0835.03
Build Date 8/31/08
Architecture Intel (32 bit)
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
2. Stop all process that users installations
like dmgr , nodes and applications servers
3. Make sure the .pak file is available under maintenance directory.
[websphe@middleware maintenance]$ pwd
/u05/local/opt/was/was70/UpdateInstaller/maintenance
[websphe@middleware maintenance]$ ls -ltr
-rw-r--r-- 1 websphe dba 718834707 Nov 20 23:21 7.0.0-WS-WAS-LinuxX32-FP0000029.pak
-rw-r--r-- 1 websphe dba 84327167 Nov 20 23:21 7.0.0-WS-WASSDK-LinuxX32-FP0000029.pak
4. Customize the response file parameters
[websphe@middleware maintenance]$ cd /u05/local/opt/was/was70/UpdateInstaller/responsefiles/
[websphe@middleware responsefiles]$ ls -ltr
-rwxr-xr-x 1 websphe dba 3064 Nov 20 23:11 uninstall.txt
-rwxr-xr-x 1 websphe dba 4275 Nov 20 23:11 install.txt
You can find the original response file (install.txt) inside responsefiles folder in UpdateInstaller. Take a backup of that file and open and edit the response file parameters according to your requirement . The minimum lines required for installing UpdateInstaller are given below.
-OPT checkFilePermissions="true"
-W maintenance.package="/u05/local/opt/was/was70/UpdateInstaller/maintenance"
(This parameter specify a full folder name that contains the maintenance packages)
-OPT rootUserHasRunSlibcleanCommandSuccessfully="true"
-W product.location="/u05/local/opt/was/was70"
-W update.type="install"
5. Execute update execute file
[websphe@middleware UpdateInstaller]$ ./update.sh -options=/u05/local/opt/was/was70/UpdateInstaller/responsefiles/install.txt -silent
Executing command: /u05/local/opt/was/was70/UpdateInstaller/java/jre/bin/java -cp /u05/local/opt/was/was70/UpdateInstaller/update.jar -Xms48m -Xmx384m run -options /u05/local/opt/was/was70/UpdateInstaller/responsefiles/install.txt -silent
Check the installation status of fix pack or refresh pack in a log file named by log.txt.
If the installation is success we will get a message “INSTCONFSUCCESS”
[websphe@middleware install]$ pwd
/u05/local/opt/was/was70/UpdateInstaller/logs/install
[websphe@middleware install]$ ls -ltr
total 96
-rw-r--r-- 1 websphe dba 4034 Nov 20 23:11 trace.xml.gz
-rw-r--r-- 1 websphe dba 2457 Nov 20 23:11 trace.txt.gz
-rw-r--r-- 1 websphe dba 26 Nov 20 23:11 relabel.stdout.gz
-rw-r--r-- 1 websphe dba 26 Nov 20 23:11 relabel.stderr.gz
-rw-r--r-- 1 websphe dba 17207 Nov 20 23:11 log.txt
-rw-r--r-- 1 websphe dba 56032 Nov 20 23:11 installconfig.log.gz
[websphe@middleware install]$ view log.txt
------------------------------------
--------------------------------
(Nov 20, 2015 11:11:57 PM), Install, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: 90SCreateEmptyUPDIDirs, percent complete: 100%
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=0
(Nov 20, 2015 11:11:58 PM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS
Now check the current version of WAS, and start your process
[websphe@middleware bin]$ ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.5.1, dated 6/15/11
-------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------
Report at date and time November 20, 2015 11:43:28 PM PST
Installation
--------------------------------------------------------------------------------
Product Directory /u05/local/opt/was/was70
Version Directory /u05/local/opt/was/was70/properties/version
DTD Directory /u05/local/opt/was/was70/properties/version/dtd
Log Directory /u05/local/opt/was/was70/logs
Backup Directory /u05/local/opt/was/was70/properties/version/nif/backup
TMP Directory /tmp
Product List
--------------------------------------------------------------------------------
ND installed
Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 7.0.0.29
ID ND
Build Level cf291321.01
Build Date 5/26/13
Architecture Intel (32 bit)
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
[websphe@middleware bin]$
*******************************************************************
SAMPLE INSTALL.TXT FOR FIX PACK UPDATE :
#########################################################
# 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
#
#########################################################
# Used to input the maintenance package full filename
# specification to be installed.
# Edit as appropriate.
#
# ie. -W maintenance.package="C:\Program
# Files\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 time stamp).
#
#-W maintenance.package=
#########################################################
# Used to modify the product install location that will
# be updated.
# This value should be left commented out if the Update
# Installer is
# being run from the recommended location
#
# ie. -W product.location=
# "C:\Program Files\WebSphere\AppServer"
#
# Note: If no location is specified, the parent
# directory to update installer
# will be used as default
#
#-W product.location=""
#########################################################
# Do not edit these values.
#
#
-W update.type="install"
*******************************************************************
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
#
# 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"
No comments:
Post a Comment