Before you begin
Use the correct authorizations to successfully install
product updates.
Use
the Update Installer program from a user profile with *ALLOBJ special
authority.
Important:
- Make sure that no processes from any users are locking any files
in the target location where a maintenance package is to be installed.
Attention: Fix packs that include updates to the Software Development
Kit (SDK) might overwrite unrestricted policy files. Back up unrestricted
policy files before you apply a fix pack and reapply these files after
the fix pack is applied.
The Update Installer wizard is an InstallShield for Multiplatforms
wizard that runs with in silent mode with a response file.
The following
descriptions contain reference information about installing interim
fixes, fix packs, and refresh packs on WebSphere
® Application Server products and
components:
- Overview of the installation procedure
- Ensure that the Update Installer for WebSphere Software is installed on your system.
The Update installer can be installed from the WebSphere Application Server for i5/OS® supplements disk, which
is included with the installation media. Additionally, when you apply
the latest WebSphere Application
Server for i5/OS group program
temporary fix (PTF), the current level of the Update Installer is
installed if it is not already installed on the system. The default
install location for the Update Installer is QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI.
- Download the most current version of the interim
fix, fix pack, or refresh pack file from the Support site into the updi_root /maintenance directory.
Note: The WebSphere Application Server
for i5/OS group PTF always
includes the most recent fix pack or refresh pack for the product.
If you have applied the group PTF, there is no need to download the
current fix or refresh pack level.
- Use the Update Installer to install the interim
fix, fix pack, or refresh pack.
The Update Installer creates a backup file in the
app_server_root/properties/version/nif/backup directory.
Note: The group PTFs do not contain any feature
pack related items. These items can be downloaded from the support
site.
- Updating existing profiles in WebSphere Application
Server products
- The Update Installer updates the core product files in a WebSphere Application Server
product. Service in a maintenance package might update the following
files in the installation root directory:
- Viewing the fix level of the product
- Use the versionInfo command and
the historyInfo command in the app_server_root/bin directory
of the installation root directory to display the exact fix and version
level of the product. However, do not use either command while installing
or uninstalling a maintenance package.
Important: See the release notes for your product for the latest
information about the Update Installer.
- Log on as a user profile with *ALLOBJ
special authority.
- Install the product that you intend to update.
You
have very likely already installed the software that you are now updating.
But if not, install the software now.
- Optional: Install
a new version of the Update Installer.
If you have installed
the current level of the WebSphere Application
Server group PTF, the update installer was updated to the most recent
level for you and you do not need to perform this step.
Back
up and uninstall any older copy of the Update Installer before downloading
and installing the current Update Installer. To use a newer version
of the Update Installer, you must first remove the older version.
- Back up any files and subdirectories in the updi_root/maintenance directory
if necessary.
- Uninstall the older version of the Update Installer
using the program under updi_root/uninstall.
- Download, unpack, and install the Update Installer for WebSphere Software; or install the
Update Installer that is on the WebSphere Application
Server supplements disc.
- Download the maintenance
package *.pak file from the Support Web site
into the updi_root/maintenance directory.
Note: If you are installing the most current fix pack and you
have installed the current level of the WebSphere Application Server group PTF,
the maintenance package containing the fix pack was placed in the
updi_root/maintenance
directory for you and you do not need to perform this step.
Tip: Do not attempt to unzip or unpack the *.pak file.
- Stop all processes that use the WebSphere Application Server
product.
Before installing or uninstalling interim fixes,
fix packs, and refresh packs on a machine, stop all Java processes on the machine that use the WebSphere Application Server
product.
WebSphere Application Server processes
include application server processes, such as the process created
when server1 is running.
See Shutting down the WebSphere Application Server subsystem to stop all processes.
- Verify that the following prerequisite
conditions are met:
- Follow the instructions for installing
the maintenance package. If you obtained the fix or refresh
pack by installing the Websphere Application Server group PTF, the
instructions for installing the fix or refresh pack can be found in
file: updi_root/ReadmeV61.html or updi_root/ReadmeV61.txt.
If
you downloaded the maintenance package from the Support site, the
instructions are contained in the readme file link found on the download
page.
- Change directories to the updi_root directory
and use the update command to install the
maintenance package.
Use the following command syntax to install the last maintenance
package that you downloaded. The Update Installer wizard runs in two
modes: the silent mode, as a background process, and the regular mode,
using the graphical user interface. The Update Installer wizard does
not display the graphical user interface when running in silent mode.
For i5/OS,
only the silent mode is supported.
update -options responsefile
update.exe -silent -options responsefile
update.exe
The following tables show options that are
available when using the update command.
Recommendation: Use the Submit
Job (SBMJOB) CL command to run the update script as a batch job. This
allows the job to run in a single storage pool and can improve the
performance of the update. The following example submits the update
as a batch job running in the QBATCH subsystem:
SBMJOB CMD(STRQSH CMD('was_install_root/updi_root/update'))
JOB(UPDATE) ALWMLTTHD(*YES)
Specify an appropriate
JOBQ parameter value to have the job run in a different subsystem.
Verify that the storage pool that the job runs in has as much memory
as possible.
The command in the following table
starts the Update Installer wizard in silent mode without the graphical
user interface:
Table 1. Update Installer command for
installing in silent mode
Command example |
Description |
update.bat -silent -options "responsefiles/file_name" |
Overrides all default values with values that
you specified in the options response file. Always use a response
file that is based on the response file under updi_root/responsefiles.
|
- For i5/OS,
only the silent mode is supported.
update -options responsefile