Apply maintenance updates and program
fixes to product components.
To install the updates that you have
downloaded:
Log in to the system. On AIX, you
must log in as root. On Linux® and
on other UNIX® computers, your
user ID must have root authority to complete installation. Follow
your local security guidelines to acquire root authority; either log
in as root, or log in as another user and become root.
- Stop all components that are running on this computer by
using the mqsistop command.
If you are applying service on a computer that is
running Linux on x86, close all instances
of the workbench.
Ensure that you
do not have any WebSphere Message
Broker files open.

Change to the directory where you downloaded
the fix pack file. The file name is in the form V.R.M-prod-platform-fixpack.tar.z,
where V.R.M-prod represents the version, release,
and modification level of the product, -platform identifies
the platform, and -fixpack identifies the fix pack. For example, the file name 6.0.0-WS-MB-AIXPPC64-FP0006.tar.z identifies
the file for Fix Pack 6 on Version 6.0.0 of WebSphere Message
Broker on AIX®.
- Replace the .z file with a .tar file,
by entering the following command:
uncompress -fv V.R.M-prod-platform-fixpack.tar.z
- Untar the image and extract all the directories, subdirectories,
and files required to apply the update, by entering the following
command:
tar -xvf V.R.M-prod-platform-fixpack.tar
- Decide which
interface you want to use for the installation; -graphical (the
default option if none is specified), -console, or -silent.
For further details of how you can run and installation, and other
options that you can specify, see Modes of installation and uninstallation.
- Depending on the choice you have selected, run one of the
commands described below, where installer is the
appropriate installation program for your platform, listed in the
table.
- To
start the installation wizard in graphical mode, type the installer name
with no options at a command prompt, and press Enter. Include
the absolute or relative path names if you invoke installation from
a directory other than the one in which the wizard exists. When you
invoke the installation wizard, it guides you through a series of
panels where you can make choices about where to install the components,
and which components you want to install.
- To start the installation wizard in console mode,
enter installer -console. Include
the absolute or relative path names if you invoke installation from
a directory other than the one in which the wizard exists. When you
invoke the installation wizard, it prompts you to enter input for
all options, including where to install the components, and which
components you want to install.
- To use the installation wizard silent interface, enter installer -silent.To start the installation wizard in silent mode,
enter installer -silent. Include
the absolute or relative path names if you invoke installation from
a directory other than the one in which the wizard exists. If you
want to specify non-default settings, include a response file on the
invocation. For more details of how to do this, and how to create
and edit a response file to define your requirements, see Using response files.
Platform |
Installation program |
AIX |
setupaix |
HP-UX on Itanium |
setuphpia64 |
HP-UX on PA-RISC |
setuphp |
Linux on POWER™ |
setuplinuxppc |
Linux on x86 |
setuplinuxia32 |
Linux on System z® |
setuplinux390 |
Solaris on SPARC |
setupsolaris |
Solaris
on x86-64 |
setupsolarisx64 |
The installer extracts the update files and runs according
to the arguments supplied.
- Follow the instructions presented by the installation program
and provide any input that is required to complete the installation.
When installation has successfully completed, review
the release notes that are supplied in the directory readmes,
and complete any manual post-installation tasks that are required.
If you have defined ODBC connections
for brokers on this computer, check the sample odbc.ini files
and make any required changes before you restart your brokers. For example, a change to database libraries might have been
made. Apply these changes to your ini files, or copy the sample and
recreate your ini files, making sure that you use the appropriate
32-bit or 64-bit sample files.
When you have completed any required ODBC changes,
restart the components by using the mqsistart command.