You can use the IBM® Update
Installer for WebSphere® Software
to install interim fixes, fix packs, and refresh packs collectively
known as maintenance packages. The Update Installer for WebSphere Software is also known as the
update installer program, the UpdateInstaller program, and the Update
Installation Wizard.
Before you begin
Use the correct authorizations to successfully install
product updates.
When administrative security is enabled on WebSphere Application Server
Network Deployment or WebSphere ESB, you
must supply the administrative user ID and password before you can
update the files.
Use the Update Installer program from the
same installer ID that installed the product that you are updating.
Otherwise, the file ownership mismatches might require correction
by the root user.
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.
On i5/OS® platforms: Use the Update Installer
program from a user profile with *ALLOBJ special authority.
Important: - The user account that originally installed the product you want
to update should be used to install the Update Installer, and the
same user account should be used to start the Update Installer program
to update the product.
- When a different user account uses the location where the Update
Installer files are located, that user account must have reading and
running access to that location. It must also have writing access
to the logs directory and its subdirectory. For
information about the location of the Update Installer files, see Installing the Update Installer for WebSphere Software.
- When a different user account is used to update the target WebSphere Application Server
product location, that user account must have full access (reading,
writing, and running) to the target location where a maintenance package
is to be applied.
On AIX® platforms: If
a non-root user starts the Update Installer program, that user account
must be able to run the slibclean command; otherwise, a root user
must run the slibclean command whenever the Update Installer program
is used.
- Make sure that no processes from any users are locking any files
in the target location where a maintenance package is to be installed.
The Update Installer is an InstallShield MultiPlatform
wizard that runs with either a graphical user interface or in silent
mode with or without a response file. When you omit the response file
in silent mode, the wizard installs the last maintenance package that
you downloaded to the default maintenance directory. For more information
about the example response file that is installed with the Update
Installer, see the
install.txt topic in the WebSphere Application Server Network Deployment
documentation.
Restriction: On i5/OS platforms: The Update
Installer on i5/OS runs only
with the install.txt response file.
Important: The
maintenance package updates the profiles. Before updating an existing
installation, back up your configuration files. Use the
backupConfig command
to back up the configuration of each profile that the maintenance
package can update. See
Backing up and restoring administrative configurations for
more information about running this command.
For refresh packs you
might also need to update the various WebSphere ESB database
schemas. If you want to uninstall your refresh pack, then you need
to restore your database to the previous level, so you need to backup
your database as well. For detailed installing or uninstalling instructions,
please refer to the instructions provided with your fix pack or refresh
pack.
About this task
Updating is modifying a file or data set
with current information. When WebSphere ESB is
updated with a refresh pack, interim fix, or a fix pack, its out-of-date
files are replaced with newer versions. Updating is different from migrating,
which is installing a completely new version of the product to replace
an earlier version of the product. For more information
about migrating, see Migrating.
Important: Instructions you receive with your interim fix,
fix pack or refresh pack override the instructions in this topic,
which are provided for your general reference only. Always follow
the specific installation instructions you receive with your interim
fix, fix pack or refresh pack.
Check the list of
WebSphere ESB recommended
fixes to confirm that your software is at the latest maintenance
level. From the Recommended Fixes web page, make sure to read the
readme file, also called the installation instructions, for the fix
pack or refresh pack that you are installing.
Important: Do
not start multiple copies of the update installer at one time. Concurrent
instances of the update installer program are not supported. Performing
more than one update at the same time can produce unpredictable results,
which might include a failed or faulty installation.
Note: Throughout
this topic, certain directory paths are shown only in Linux® and UNIX® format
for simplicity. The equivalent Windows® paths
are identical except for the direction of the slashes.
The
following procedure describes how to install a maintenance package.
For a description of how to roll back a maintenance package, see Uninstalling maintenance
packages.
To install an interim fix, a fix pack, or a
refresh pack, perform the following steps.
What to do next
After installing an maintenance package, continue to use
your WebSphere software.