How the Installer Checks Component Dependencies

Many product components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of product components to verify that the components you select during installation will function properly together. For this reason, the installer might prompt you to include certain product components as you make your selections.

In general, the installer uses the following rules for handling dependencies among the Java ES product components:

• Selecting a Product Component. In most cases, when you select a product component for installation, the installer automatically selects all its subcomponents.

  The installer also selects the components and subcomponents upon which the selected product component depends. For example, if you select Application Server, the installer automatically selects HADB, Java DB, and Message Queue.

• Deselecting a Product Component. In most cases, when you deselect a product component, the installer automatically deselects all its subcomponents.

  If you deselect a product component that is required locally or remotely for another selected product component, the installer displays various warnings when you attempt to proceed.

• Selecting a Subcomponent. If you select a subcomponent, the installer automatically selects the product component to which it belongs, but not necessarily the other subcomponents.

  If the selected subcomponent depends on other components or subcomponents, the others are automatically selected.

• Deselecting a Subcomponent. If you deselect a subcomponent, the installer deselects only that subcomponent and not the other subcomponents.

  If you deselect a subcomponent that is required locally or remotely for another selected product component, the installer displays various warnings when you attempt to proceed.