Logic that the Update Installer uses for system recommended installations

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 this occurs.

The package will not be shown or will be grayed out if:
As further maintenance packages are selected, the installer will evaluate prerequisites and dependencies to determine the installation sort order based on the following rules:
  1. Maintenance packages all belong to products already installed in the selected install location directory
  2. Only permit the most recent versions of selected maintenance packages to be installed
  3. 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.
Reference topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:23:46 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=rins_updi_installlogic
File name: rins_updi_installlogic.html