Sun Java Communications Suite 5 Installation Guide

Handling Interdependencies

The uninstaller might behave differently depending on which product components you installed and how they are interrelated.

Caution – Caution –

When uninstalling a product component, you must identify which products are configured for that product component (some additional configuration might be required). Otherwise, you could have product components on your system that are configured to support products that are no longer present.

The uninstaller does not recognize the following interdependencies:

Product Component Dependencies from Remote Hosts

Some product component dependencies can be satisfied with product components deployed on remote hosts. The uninstaller does not recognize these dependency relationships.

For example, if you uninstall Directory Server, the uninstaller does not warn you that Access Manager depends on Directory Server, even if both products are deployed on the same host. This is because another Directory Server instance on yet another host could support Access Manager.

Product Component Dependencies Resulting from Configuration

The uninstaller does not recognize a product component dependency that is the result of postinstallation configuration.

For example, suppose you install both Portal Server with the JES installer and Calendar Server with the Communications Suite installer on the same host, and then configure Portal Server to use Calendar Server for the Portal Server calendar channel. After this configuration, Portal Server depends on Calendar Server. However, if you then uninstall Calendar Server, the uninstaller does not warn you that Portal Server depends on Calendar Server because the uninstaller does not know about the postinstallation configuration.