Sun Java Enterprise System 5 Installation Guide for UNIX

How the Uninstaller Works

This section contains the following subsections:

Java ES provides an uninstallation program for removing product components that were installed on your system using the Java ES installer. Like the Java ES installer, the uninstaller can be run in graphical, text-based, or silent mode.

During installation, the Java ES installer places the Java ES uninstaller at the following location:

Tip –

You can use the optional -no parameter to run the uninstaller without uninstalling any software. This option is useful for familiarizing yourself with the uninstaller and for creating a state file for a subsequent silent uninstallation.

Limitations of the Uninstaller

Caution – Caution –

Do not use the uninstaller to remove Sun Cluster software unless Sun Cluster software was installed but never used to configure a cluster node. For more information, see Uninstalling Sun Cluster Software

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 might 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 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 and Calendar Server 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.