Sun Java Communications Suite 5 Installation Guide

Planning for Uninstallation

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:

Surveying Installed Communications Suite Software

Perform one of the following procedures to review the product component software that is already installed on each host.

To Use the Uninstaller for Viewing Installed Software

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.

To Use the Solaris prodreg Utility to View Installed Software

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.

Reviewing Uninstallation Behavior for Communications Suite Product Components

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.

Note –

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:

Access Manager Uninstallation Behavior

Table 9–2 Access Manager Uninstallation Details


Topic	Details
Configuration Data	No entries in Directory Server will be removed (including Access Manager specific data).
Other Installations This Component Requires	Directory Server Web container
Products Requiring this Installation	Calendar Server, when configured for single sign-on (SSO) Instant Messaging, when configured for Portal Server, SSO Messaging Server, when configured for SSO Communications Express, when configured for SSO and when Schema 2 is used
Pre-Uninstallation Tasks	Remove the schema using `/etc/opt/SUNWam/config/ldif/ds_remote_schema_uninstall.ldif`.
Post-Uninstallation Tasks	Uninstallation unconfigures Access Manager from the web container for full installations on Web Server or Application Server only. It does not unconfigure Access Manager from third-party web containers. It also does not unconfigure SDK installations on any web container (such as, Web Server, Application Server, BEA WebLogic, IBM WebSphere). Additionally, remove the following files located in the directory `/var/sadm/install` if they exist: `.lockfile.pkg.lock`

Application Server Uninstallation Behavior

Table 9–3 Application Server Uninstallation Details


Topic	Details
Configuration Data and User Data	The default domain created during installation is removed during uninstallation. User-created domains, including all administrative server and Application Server instances, are not removed during uninstallation. All Administration Server and Application Server instances are stopped prior to the completion of uninstallation.
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.

Calendar Server Uninstallation Behavior

Table 9–4 Calendar Server Uninstallation Details


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	Directory Server Access Manager, when configured for single sign-on (SSO) or if you want to use Schema 2 Messaging Server (or some other mail server, for Calendar Server email notification service)
Products Requiring this Installation	Communications Express
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.

Communications Express Uninstallation Behavior

Table 9–5 Communications Express Uninstallation Details


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	Application Server (if configured to run under Application Server) Web Server (if configured to run under Web Server) Access Manager (when configured for SSO) Directory Server Calendar Server Messaging Server
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.

Delegated Administrator Uninstallation Behavior

Table 9–6 Delegated Administrator Uninstallation Details


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	Directory Server Access Manager One of these web containers: Web Server or Application Server
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.

Directory Proxy Server Uninstallation Behavior

Table 9–7 Directory Proxy Server Uninstallation Details


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

Directory Server Uninstallation Behavior

Table 9–8 Directory Server Uninstallation Details


Topic	Details
Configuration Data and User Data	If you are uninstalling the Directory Server instance hosting user data, the Directory Server LDAP database is removed during uninstallation. Caution: To avoid loss of data, make sure to back up Directory Server information before uninstalling. Directory Server has several tools and utilities to backup Directory Server and migrate configuration data. Refer to Directory Server documentation for more information.
Other Installations This Component Requires	None
Products Requiring this Installation	Calendar Server Access Manager Instant Messaging Messaging Server Communications Express
Pre-Uninstallation Tasks	Back up the Directory Server LDAP database as needed. Make sure you can provide the Directory Server instance path.
Post-Uninstallation Tasks	If you subsequently install Directory Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location.

Instant Messaging Uninstallation Behavior

Table 9–9 Instant Messaging Uninstallation Details


Topic	Details
Configuration Data and User Data	All configuration data remains after uninstallation, and can be reused upon a subsequent installation.
Other Installations This Component Requires	Directory Server Access Manager SDK Web container
Products Requiring this Installation	Portal Server, when configured to use Instant Messaging channel
Pre-Uninstallation Tasks	Undeploy Instant Messaging modules from the web container.
Post-Uninstallation Tasks	None

Messaging Server Uninstallation Behavior

Table 9–10 Messaging Server Uninstallation Details


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	Directory Server Web Server (for mailing functionality such as filters) Access Manager (if using Schema 2) Message Queue
Products Requiring this Installation	Calendar Server Portal Server, when configured with messaging channels Communications Express, when messaging is used
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

Message Queue Uninstallation Behavior

Table 9–11 Message Queue Uninstallation Details


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	Stop any running brokers. You will be prompted for user name (admin) and password:`imqcmd shutdown bkr` [`-b` `hostName:port`] If you are not planning to reinstall Message Queue and therefore want to delete dynamic data, the flat-file user repository, and the access control file associated with each broker instance, remove this data using the following command. `imqbrokerd -name` `instanceName` `-remove` `instance` If you upgrade Message Queue using the Message Queue upgrade script, make a note of your process. The upgrade script does not write install information to the Communications Suite registry. More information may be found in the Sun Java Enterprise System 2006Q3 Upgrade Guide.
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.

Monitoring Console Uninstallation Behavior

For information on Monitoring Console uninstallation behavior, refer to the Sun Java Enterprise System 5 Installation Guide for UNIX.

Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior

Table 9–12 Sun Cluster and Sun Cluster Geographic Edition Uninstallation Details


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.

Web Proxy Server Uninstallation Behavior

Table 9–13 Web Proxy Server Uninstallation Details


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.

Web Server Uninstallation Behavior

Table 9–14 Web Server Uninstallation Details


Topic	Details
Configuration Data and User Data	User data is not removed during uninstallation but configuration data is removed. The Web Server administrative server instance and configured Web Server instance directories are removed. The initially-configured document root directory is preserved. Web Server administrative server and Web Server instances are stopped prior to the completion of the uninstallation.
Other Installations This Component Requires	None
Products Requiring this Installation	Components that can be configured to use Web Server as web container: Access Manager, Communications Express, Delegated Administrator, and Instant Messaging.. Also Application Server Load Balancing Plugin (if Application Server uses Web Server as its web container).
Pre-Uninstallation Tasks	Make sure you can provide the administrator password for the web container.
Post-Uninstallation Tasks	To preserve configuration data, back up the Administrative Server and Web Server instance directories under the installation location. If you subsequently install Web Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location.

Granting Administrator Access for the Uninstaller

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.