Sun Java Enterprise System 5 Installation Guide for UNIX

Reviewing Uninstallation Behavior for Java ES Product Components

Review the relevant tables in this section to see what the uninstaller does with each Java ES product component. 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 Files Left Behind During an Uninstallation for guidelines on resolution.


This section contains the following subsections:

Access Manager Uninstallation Behavior

Table 8–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 

Portal Server must reside on the same host as Access Manager SDK. 

Pre-Uninstallation Tasks 

Remove the schema using this file: 

Solaris OS: /etc/opt/SUNWam/config/ldif/ds_remote_schema_uninstall.ldif

Linux and HP-UX: /etc/opt/sun/identity/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. Uninstallation also does not unconfigure SDK on any web container. 

Additionally, remove the following files located in the directory /var/sadm/install if they exist:

.lockfile.pkg.lock.

For information on additional post-uninstallation issues, refer to Access Manager Post-uninstallation Issues.

Application Server Uninstallation Behavior

Table 8–3 Application Server Uninstallation Details

Topic 

Details 

Configuration Data and User Data (Solaris OS and Linux only) 

  • 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. 

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: 

/var/opt/SUNWappserver

/opt/SUNWappserver/appserver or ApplicationServer-base

Linux and HP-UX: 

/var/opt/sun/appserver

/opt/sun/appserver

Refer to Message Queue Uninstallation Behavior for information on Message Queue post-uninstallation tasks.

Directory Proxy Server Uninstallation Behavior

Table 8–4 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 8–5 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 at http://docs.sun.com/coll/1224.1 for more information.

Other Installations This Component Requires 

None 

Products Requiring This Installation 

  • Access Manager

  • Portal Server

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. 

HADB Uninstallation Behavior

Table 8–6 HADB Uninstallation Details

Topic 

Details 

Configuration Data and User Data 

Configuration and user data are not removed during uninstallation. By default, this data resides in the following locations: 

  • Solaris OS and Linux: /etc/opt/SUNWhadb, /var/opt/SUNWhadb

  • HP-UX: /etc/opt/sun-hadb, /var/opt/sun-hadb

Other Installations This Component Requires 

None 

Products Requiring This Installation 

Application Server when configured to use HADB for high availability session persistence. 

Pre-Uninstallation Tasks 

If you plan to upgrade HADB and reuse configuration data, refer to the chapter on High Availability Session Store in the Sun Java Enterprise System 5 Upgrade Guide for UNIX

Post-Uninstallation Tasks 

Remove configuration and user data that is no longer needed. 

Message Queue Uninstallation Behavior

Table 8–7 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). 

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 Java ES registry. For more information, see the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

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

Table 8–8 Monitoring Console Uninstallation Details

Topic 

Details 

Configuration Data 

User data remains after uninstallation, however, this data is removed before any reinstallation. 

Other Installations This Component Requires 

None 

Other Products Requiring This Installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

To preserve data, copy the following to a persistent location, then copy back after reinstallation: 

For Solaris OS: 

/etc/opt/SUNWmfwk/config/mfwk.properties

/etc/opt/SUNWmfwk/config/masteragent.properties

/etc/opt/SUNWmfwk/config/nodelist

/var/opt/SUNWmfwk/persistence/

/var/opt/SUNWmfwk/alarms/

For Linux and HP-UX: 

/etc/opt/sun/mfwk/config/mfwk.properties

/etc/opt/sun/mfwk/config/masteragent.properties

/etc/opt/sun/mfwk/config/nodelist

/var/opt/sun/mfwk/persistence/

/var/opt/sun/mfwk/alarms/

Portal Server Uninstallation Behavior

Table 8–9 Portal Server Uninstallation Details

Topic 

Details 

Configuration Data and User Data 

  • Configuration data is removed during uninstallation. Unconfiguring includes removing services created in Access Manager by Portal Server.

  • Providers for user channels are not removed during installation and can be reused upon subsequent installation.

  • Customized configuration data (display profiles, property files, resources strings, and other customizations) is not removed by the uninstaller. It can be reused upon subsequent installation only if Portal Server is reinstalled to the same host with the same configuration.

Other Installations This Component Requires 

  • Directory Server

  • Application Server or Web Server (Can also be configured to be dependent on IBM WebSphere or BEA WebLogic on Solaris OS.)

  • Access Manager

  • Service Registry

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

Verify that Directory Server and the web container are running. If the web container is Web Server, Web Server admin server must be running. 

Post-Uninstallation Tasks 

  • If you are running Portal Server within Web Server and you choose to remove Portal Server only, you must restart Access Manager. For more information, refer to Access Manager Post-uninstallation Issues

  • If Portal Server is deployed to the IBM WebSphere web container, there might be additional uninstallation tasks.

Portal Server Secure Remote Access Uninstallation Behavior

Table 8–10 Portal Server Secure Remote Access Details for Uninstallation

Topic 

Details 

Configuration Data 

  • All configuration data for the Portal Server Secure Remote Access Core product component is removed during uninstallation.

  • All web applications that have been deployed are undeployed.

  • Users do not have configuration data access to Portal Server Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy subcomponents.

Other Installations This Component Requires 

  • Portal Server Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy depend on Portal Server. You cannot remove Portal Server and retain Gateway, Netlet Proxy, and Rewriter Proxy.

  • Portal Server, Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy subcomponents depend on Access Manager SDK.

  • Access Manager SDK must reside on the same host as Gateway, Netlet Proxy, and Rewriter Proxy. Gateway, Netlet Proxy, and Rewriter Proxy cannot be in the same directory.

  • You can remove any Portal Server Secure Remote Access product component without removing any dependent product component.

  • You can remove Gateway and leave Access Manager SDK on the host.

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

None 

Service Registry Uninstallation Behavior

Table 8–11 Service Registry Details for Uninstallation

Topic 

Details 

Configuration Data 

The Registry configuration process installs the Registry database domain and server keystore in the following directory: 

  • Solaris OS: /var/opt/SUNWsrvc-registry

  • Linux and HP-UX: /var/opt/sun/srvc-registry

The directory is not removed when Service Registry is uninstalled. This allows you to preserve the database for use in a future installation or release if you want.  

Other Installations This Component Requires 

Application Server (Domain Administration Server and Command-Line Administration Tool) 

HADB 

Message Queue 

Products Requiring This Installation 

None 

Pre-Uninstallation Tasks 

1. Navigate to the ServiceRegistry–base/install directory.

2. Stop the Service Registry domain as follows: 

.../ant -f build-install.xml appserver.domain.stop

3. Delete the Service Registry domain as follows: 

.../ant —f build-install.xml appserver.domain.delete

If you want to preserve the Registry database for future use, copy the /var/opt/SUNWsrvc-registry/3.0 directory (on Solaris OS) or /var/opt/sun/srvc-registry/3.0 (on Linux and HP-UX) directory to another location before you reinstall the Registry.

Post-Uninstallation Tasks 

For information on some optional tasks, refer to Service Registry Post-uninstallation Tasks

Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior

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

Topic 

Details 

Configuration Data 

Do not use the Java Enterprise System 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 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

Sun Cluster core and agents for Sun Cluster must be removed together. 

Products Requiring This Installation 

None 

Pre-Uninstallation Tasks 

Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster installation.  

Note: Sun Cluster Geographic Edition software must be removed before Sun Cluster software is removed. 

Post-Uninstallation Tasks 

You might need to update the product registry after uninstalling Sun Cluster software. For more information, refer to Uninstalling Sun Cluster Software.

Web Proxy Server Uninstallation Behavior

Table 8–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. Before reinstalling, move the certificate database and delete the old installation directory.

Web Server Uninstallation Behavior

Table 8–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 not removed.

  • Web Server administrative server and Web Server instances are stopped before completion of uninstallation.

Other Installations This Component Requires 

None 

Products Requiring this Installation 

Components that can be configured to use Web Server as web container, such as Access Manager and Portal Server. 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 reinstall 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. 

For information on additional post-uninstallation issues, refer to Web Server Post-uninstallation Tasks (Web Server Not Uninstalled).