Q24: Does the installer check dependencies on remote components?

Answer: In general, the installer checks dependencies and versions on the local host only. However, one situation exists where the installer interacts with a remote host: if you select the Configure Now configuration type and are using a remote component (such as Directory Server or Access Manager) to satisfy a dependency. In this case, the installer tries to connect with the remote component during the installation session. If the remote component is not available, installation stops, and you receive an error message. To avoid this situation, install, configure, and start any remote components before starting an installation session.

In a Configure Later installation, the installer runs as though the remote component is available and does no checking. Installation succeeds, and you can proceed to postinstallation configuration. However, if the remote component is not available, you receive errors when you try to run any component that depends on that remote component.

To indicate to the installer that you will be using a remote component, select all the components that you will install locally and then deselect any dependency that will be fulfilled by a remote component. When you attempt to proceed, the installer prompts you to fulfill any requirements for the component that you deselected. At this point, you indicate to the installer that you are using a remote component to fulfill a dependency.