How the Uninstaller Works

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

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

• Solaris OS: /var/sadm/prod/SUNWcomm-entsys5

• Linux: /var/sadm/prod/sun-comm-entsys5

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

Like the installer, you can run the uninstaller in graphical, text-based, or silent mode.

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

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

• The uninstaller does not remove shared components.

• 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 Communications Suite Product Components.

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

• The uninstaller presents unconfigure pages for product components if needed for multi-session uninstallation.

• The uninstaller does not unconfigure installations on third-party web containers.

• The uninstaller does not unconfigure Access Manager SDK installations on any web container. You must reconfigure the web container manually (for example, restore the original classpath).

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.

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

• In most cases, you can uninstall a product component if no other product component depends on it.

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:

• Dependencies from remote hosts

• Dependencies resulting from configuration

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.