Before using the uninstaller, you should survey your installation and plan the steps you might have to take to prevent loss of data or loss of interdependency connections. It is important to understand how the various product components behave when they are uninstalled.
This section contains the following subsections:
Perform one of the following procedures to review the product component software that is already installed on each host.
As root, navigate to the directory where the uninstaller is located:
Solaris OS: /var/sadm/prod/SUNWcomm-entsys5
Linux: /var/sadm/prod/sun-comm-entsys5
To survey the local system, run the uninstaller without uninstalling software.
For graphical mode:
./uninstall -no |
For text-based mode:
./uninstall -no -nodisplay |
To see the full syntax for the uninstall command, refer to uninstall Command.
Proceed through the uninstaller pages until you reach the list of installed products.
After viewing the list of installed product components, exit the uninstaller.
No software has been uninstalled.
You can use the prodreg utility to view information about all packages installed on your system, including Communications Suite product components.
This information is useful when checking for product component dependencies. The prodreg utility also indicates packages that are incomplete and might need special handling. On the Solaris 10 and Solaris 9 operating systems, run the utility as follows:
prodreg
For more information, see the prodreg man page.
Review the relevant tables in this section to see what the uninstaller does with Communications Suite product components. Plan the steps you might have to take to prevent loss of data or loss of interdependency connections.
In some cases, component files are left behind after uninstallation, which could cause a subsequent installation to fail. If this occurs, refer to Installation Fails Due to Leftover Files During Uninstallation for guidelines on resolution.
This section contains the following subsections:
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Other Installations This Component Requires |
Requires Message Queue on the same system. |
Products Requiring this Installation |
Components that are configured to use Application Server as web container: Access Manager, Communications Express, Delegated Administrator, Instant Messaging. |
Pre-Uninstallation Tasks |
To preserve configuration data, make a copy of the administration domain directories. |
Post-Uninstallation |
To completely remove Application Server from your system, remove any remaining Application Server log files and directories. Default locations for Application Server directories are: Solaris OS: /opt/SUNWappserver /opt/SUNWappserver/appserver or ApplicationServer-base Linux: /var/opt/sun/appserver /opt/sun/appserver Refer to Message Queue Uninstallation Behavior for information on Message Queue post-uninstallation tasks. |
Topic |
Details |
---|---|
Configuration Data and User Data |
Configuration data and user data are not removed during uninstallation, and will be overwritten upon subsequent installation. Customizations to Calendar Server are removed during uninstallation. |
Other Installations This Component Requires |
|
Products Requiring this Installation |
|
Pre-Uninstallation Tasks |
If you plan to reuse configuration data and user data, follow the migration process as described in the Sun Java System Calendar Server 6.3 Administration Guide. |
Post-Uninstallation Tasks |
Remove any remaining log files and Calendar Server directories that are not needed. |
Topic |
Details |
---|---|
Configuration Data and User Data |
All configuration data, user data and UI customizations remain after uninstallation. Communications Express files are maintained in two locations: Package Installation by default: Solaris OS: /opt/SUNWuwc Linux: /opt/sun/uwc Application Deployment created by default during configuration: Solaris OS: /var/opt/SUNWuwc Linux: /var/opt/sun/uwc When you uninstall Communications Express, the uninstaller removes the data from only the package installation location. The data at application deployment location is still present. You can access the application from application deployment location. However, all configuration data and UI customizations will be overwritten during re-configuration. User data remains after re-configuration. |
Other Installations This Component Requires |
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
Undeploy Communications Express referring to the “Undeploying Communications Express” section in the Sun Java System Communications Express 6.3 Administration Guide. |
Post-Uninstallation Tasks |
Remove any remaining log files and Communications Express directories that are not needed. |
Topic |
Details |
---|---|
Configuration Data |
Configuration data and user data are not removed during uninstallation. This data will be overwritten upon a subsequent installation. Customizations to Delegated Administrator are removed during uninstallation. |
Other Installations This Component Requires |
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
If you plan to reuse configuration data and user data, read Preserve an Existing Configuration in Sun Java System Delegated Administrator 6.4 Administration Guide. Undeploy the Delegated Administrator web applications using the undeploy command for the web container. |
Post-Uninstallation Tasks |
Remove any remaining log files and Delegated Administrator directories that are not needed. |
Topic |
Details |
---|---|
Configuration data |
Configuration data for the instance of Directory Proxy Server you are uninstalling is removed during uninstallation. Shared configuration data between several instances of Directory Proxy Server remains after uninstallation. Directory Proxy Server has no user data. |
Other Installations This Component Requires |
Directory Proxy Server has a logical dependency upon the local or remote Directory Server . |
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
None |
Topic |
Details |
---|---|
Configuration Data and User Data |
All configuration data and customizations remain after uninstallation, and can be reused upon subsequent installation. By default, this includes configuration files, logs, MTA queues, message store, and other read/write working files. |
Other Installations This Component Requires |
|
Products Requiring this Installation |
|
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
Depending on your circumstances, you might have to perform post-uninstallation tasks as explained in Messaging Server Post-uninstallation |
Topic |
Details |
---|---|
Configuration Data |
Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. |
Other Installations This Component Requires |
Directory Server (optional) |
Products Requiring This Installation |
Application Server (must reside on same host as Message Queue) Messaging Server |
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
If you are not planning to reinstall Message Queue, use the commands in the product component documentation to clean up your system. |
For information on Monitoring Console uninstallation behavior, refer to the Sun Java Enterprise System 5 Installation Guide for UNIX.
Topic |
Details |
---|---|
Configuration Data |
Do not use the uninstaller to remove Sun Cluster software, except to remove software that was installed but never used to configure a cluster node. For more information, refer to Uninstalling Sun Cluster Software. |
Other Installations This Component Requires |
Sun Cluster core and agents for Sun Cluster must be removed together. Sun Cluster Geographic Edition software must be removed on every host that contains Sun Cluster Geographic Edition components. For more information, refer to Chapter 5, Uninstalling the Sun Cluster Geographic Edition Software, in Sun Cluster Geographic Edition Installation Guide. |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster installation. Sun Cluster Geographic Edition must be removed before Sun Cluster software is removed. |
Post-Uninstallation Tasks |
You might need to update the productregistry file after uninstalling Sun Cluster software. For more information, refer to Uninstalling Sun Cluster Software. |
Topic |
Details |
---|---|
Configuration Data |
Only the certificate database files in the alias directory under the installation location are preserved. All other files are removed. |
Dependencies |
Directory Server (optional) if external LDAP access control has been selected. |
Pre-Uninstallation Tasks |
Stop all instances of Web Proxy Server. |
Post-Uninstallation Tasks |
The certificate database is preserved under the WebProxyServer-base/alias directory. You need to move the certificate database and delete the old installation directory before reinstalling. |
Depending on the product components you choose to uninstall, you might need to grant the uninstaller administrator access to Access Manager and Directory Server.
Access Manager administrator access is required to undeploy the Access Manager web applications from the Application Server and to remove the Access Manager schema.
Directory Server administrator access is required to manage the configuration directory during uninstallation.
The following table describes the information that the uninstaller needs for granting administrator access. The left column of each table lists the graphical mode labels and state file parameters for the information you must provide. The right column describes the information.
Table 9–15 Required Administration Information
Label and State File Parameter |
Description |
---|---|
Access Manager | |
Administrator User ID IS_IAS81_ADMIN |
User ID of the Application Server administrator. |
Administrator Password IS_IAS81_ADMINPASSWD |
Password of the Application Server administrator. |
Directory Manager DN IS_DIRMGRDN |
Distinguished Name (DN) of the user who has unrestricted access to Directory Server. Default value is cn=Directory Manager. |
Directory Manager Password IS_DIRMGRPASSWD |
Password of the Directory Manager. |
Directory Server | |
Administrator User ID CONFIG_DIR_ADM_USER |
User with administrator privileges for the configuration directory. This user can modify Directory Server configuration, including creating and removing suffixes. Access control restrictions apply. |
Administrator Password CONFIG_DIR_ADM_PASSWD |
Password for the Administrator. |