How the Uninstaller Works

Java ES provides an uninstallation program for removing Java ES components that were installed on your system by using the Java ES installer.

Limitations of the Uninstaller

Like the Java ES installer, the uninstaller can be run in graphical or silent mode.

• The uninstaller removes only Java ES components that were installed by the Java ES installer. To remove Java ES components that were not installed by the Java ES installer, follow instructions in the Java ES component documentation.

• The uninstaller must be run separately on each host that contains Java ES components. Remote uninstallation is not supported. For each host, you can select one or more Java ES components for removal.

• The uninstaller might remove configuration and user data files. The files vary for each component.

  After the uninstallation process is completed, you might have to remove some additional files and directories. For product-by-product information, refer to Reviewing Uninstallation Behavior for Java ES Components.

• The uninstaller checks Java ES component dependencies only for the system on which the uninstaller is running, issuing warnings when a dependency is discovered.

Handling Interdependencies

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

• The uninstaller recognizes dependencies among products that are installed on the same host. If you attempt to uninstall a Java ES component that has dependent products installed on the host, the uninstaller issues a warning.

  For example, if you attempt to uninstall Access Manager from the host where Portal Server is also installed, the uninstaller warns you that Portal Server cannot function without Access Manager.

• In most cases, you can uninstall a Java ES component if no other Java ES component depends on that component.

  For example, Portal Server depends on Access Manager but Access Manager does not depend on Portal Server. If you attempt to uninstall Portal Server, the uninstaller does not issue a warning because Access Manager can function without Portal Server.

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

The uninstaller does not recognize the following interdependencies:

• Dependencies from remote hosts

• Dependencies resulting from configuration

Java ES Component Dependencies From Remote Hosts

Some Java ES component dependencies can be satisfied with Java ES 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 another host could support Access Manager.

Java ES Component Dependencies Resulting From Configuration

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