Installing maintenance packages silently
You can use the IBM® Update
Installer for WebSphere® Software
to install interim fixes and fix packs, collectively known as maintenance
packages. You can run it on all platforms in silent mode with a response
file.
Before you begin
Before starting this installation, perform the following tasks:
- Review the prerequisites and operating system restrictions in
the topic Maintaining the feature pack prerequisites.
- Ensure that you are installing maintenance on an i5/OS, Linux®, UNIX®, or Windows® system, and that you want to install
in silent mode with a response file. For alternative installation
procedures, click the following links:
- Ensure that you have version 7.0.0.4 or higher of the Update Installer
for WebSphere Software
installed on your system.
- Download and extract the most current version of the interim fix
or fix pack into the Update Installer maintenance directory.
Download interim fixes and fix packs from the product Recommended
Fixes Web sites:
The
maintenance directory
is located in one of the following default locations:
- For AIX® operating systems: /usr/IBM/WebSphere/UpdateInstaller/maintenance
- For i5/OS operating systems:/QIBM/ProdData/WebSphere/UpdateInstaller/V7/UPDI/maintenance
- For HP-UX, Linux and Solaris
operating systems:/opt/IBM/WebSphere/UpdateInstaller/maintenance
- For Windows operating
systems:C:\Program Files\IBM\WebSphere\UpdateInstaller\maintenance
About this task
The maintenance packages do not update the profiles. Instructions
that you receive with your interim fix or fix pack override the instructions
in this topic, which are provided for your general reference only.
Always follow the installation instructions you receive with your
specific maintenance package.
- Change directories to the Update Installer directory. The Update Installer directory is located in one of the following
default locations:
Install the maintenance package on the deployment manager
node before installing the maintenance package on each server node
that you intend to update.
- Create a response file by copying the
default install.txt file supplied with the Update
Installer. The file is located by default in the following
directory:
- For AIX operating systems:/usr/IBM/WebSphere/UpdateInstaller/responsefiles
- For i5/OS operating systems:/QIBM/ProdData/WebSphere/UpdateInstaller/V7/UPDI/responsefiles
- For HP-UX, Linux and Solaris
operating systems:/opt/IBM/WebSphere/UpdateInstaller/responsefiles
- For Windows operating
systems:C:\Program Files\IBM\WebSphere\UpdateInstaller\responsefiles
- Edit and save your copy of the response file. You
can edit any portion of the response file, but be sure to specify
the following options:
For more information about the install.txt file,
see install.txt topic in the WebSphere Application Server Network Deployment
documentation.
- Type the update command for your platform,
specifying the following attributes and the location of your response
file:
Important: Do not start multiple copies of the Update
Installer at one time. Running more than one instance of the Update
Installer at a time is not supported and can produce unpredictable
results, which might include a failed or faulty update.
For
more information about the update command, see
the update command topic in the WebSphere Application Server Network Deployment
documentation.
Results
The Update Installer installs the maintenance package.
Verify the success of the update by examining the
updatelog.txt log
file in the following directory:
- For AIX, HP-UX, Linux, and Solaris operating systems: feature_pack_install_root/logs/update/interim_fix_name or fixpack_name.install/updatelog.txt
- For Windows operating
systems:feature_pack_install_root\logs\update\interim_fix_name or fixpack_name.install\updatelog.txt
- For i5/OS operating systems:feature_pack_install_root/logs/update/interim_fix_name or fixpack_name.install/updatelog.txt
If this log file contains the string INSTCONFSUCCESS
on the last line, then the update was successful. Other terms such
as INSTCONFPARTIALSUCCESS or INSTCONFFAILED can occur on other lines
within the file, or even on the last line, but if INSTCONFSUCCESS
is included in the last line, the update was successful.
If
the string INSTCONFPARTIALSUCCESS or INSTCONFFAILED appears in the
last line of the file without INSTCONFSUCCESS, problems were detected
during the update. INSTCONFPARTIALSUCCESS indicates that the update
completed but errors were generated; INSTCONFFAILED means that the
update failed completely. In either case, the log file provides information
to troubleshoot the problems.
You can also verify that the
maintenance is applied by running the command
versionInfo
-maintenancePackages from the following directory:
- For AIX, HP-UX, Linux, and Solaris operating systems: feature_pack_install_root/bin
- For Windows operating
systems: feature_pack_install_root\bin
- For i5/OS operating systems: feature_pack_install_root/bin
What to do next
If a maintenance package affects EAR files, those updated
EAR files are not deployed automatically. Deployment requires an extra
step, which is described in the maintenance package readme file.