When you select the Recommended update option, the following
logic is used by the Update Installer for WebSphere Software to install an update.
If you are using the Update Installer with the graphical user interface,
after you select the Recommended update option on the maintenance panel
of the wizard, certain packages may be grayed out for certain reasons. The
following describes some of the reasons why this occurs.
The package will not be shown or will be grayed out if:
- The maintenance packages have already been installed
- The maintenance packages are corrupted and not readable
- The maintenance packages are not applicable to products installed in the
selected install location directory
- The maintenance packages are not applicable to target operating system
and architecture
- The maintenance packages are enabling interim fixes
As further maintenance packages are selected, the installer will evaluate
prerequisites and dependencies to determine the installation sort order based
on the following rules:
- Maintenance packages all belong to products already installed in the selected
install location directory
- Only permit the most recent versions of selected maintenance packages
to be installed
- Identify and warn about containment relationship conflicts between refresh
packs, fix packs and interim fixes. For example,
- Ensure APARs already in fix pack are not also selected as interim fixes
- Ensure there are no duplicated maintenance packages selected
- Ensure APARs and maintenance prerequisite and ex-requisite requirements
are met
- Ensure "depends on" dependency requirements are met
- Ensure current selecting maintenance package can be installed with previous
selected maintenance packages
- Ensure the maintenance package is supported by the current Update Installer. updi_root/framework/supportedpakversion.xml is
used to specify which version of maintenance packages is supported by the
Update Installer.