Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Reviewing Uninstallation Behavior for Java ES Components

Review the relevant tables in this section to see what the uninstaller does with Java ES components. Plan the steps that you might have to take to prevent loss of data or loss of interdependency connections.

This section contains the following subsections:

Uninstallation Behavior of Access Manager

Table 7–2 Uninstallation Details for Access Manager

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 

None 

Post-uninstallation tasks 

Uninstallation unconfigures Access Manager from the web container for full installations on Web Server or Application Server only. 

Uninstallation Behavior of Application Server

Table 7–3 Uninstallation Details for Application Server

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.

Dependencies 

Requires Message Queue on the same system. 

Products requiring this installation 

Components that are configured to use Application Server as web container: Access Manager, Portal Server. 

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. The default locations for Application Server directories is \JavaES-Install-Dir\appserver.

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

Uninstallation Behavior of Directory Server

Table 7–4 Uninstallation Details for Directory Server

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 back up Directory Server and migrate configuration data.

Dependencies 

None 

Products requiring this installation 

  • Access Manager

  • Portal Server

Pre-uninstallation Tasks 

Back up the Directory Server LDAP database as needed. 

Post-uninstallation Tasks 

If you subsequently install Directory Server at 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 at the same location. 

Uninstallation Behavior of Message Queue

Table 7–5 Uninstallation Details for Message Queue

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 by using the following command. imqbrokerd -name instanceName -remove instance

  • If you upgrade Message Queue by using the Message Queue upgrade script, make a note of your process. The upgrade script does not write installation information to the Java ES registry.

Post-uninstallation tasks 

If you are not planning to reinstall Message Queue, use the commands in the Java ES component documentation to clean up your system.  

Uninstallation Behavior of Monitoring Console

Table 7–6 Uninstallation Details for Monitoring Console

Topic 

Details 

Configuration data 

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

Dependencies 

None 

Other products requiring this installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

 

Uninstallation Behavior of Portal Server

Please refer the ReadMe file provided with the installer that has information on how to install and uninstall Portal Server. For more details please accesshttp://(http://www.sun.com/download/products.xml?id=465e130d).

Uninstallation Behavior of Service Registry

Table 7–7 Uninstallation Details for Service Registry

Topic 

Details 

Configuration data 

The Registry configuration process installs the Registry database domain and server keystore in the JavaES-install-dir directory.

The directory is not removed when Service Registry is uninstalled. This safety mechanism enables 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. Stop the Service Registry Domain as follows: 

JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.stop

2. Delete the Service Registry Domain as follows: 

JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.delete

If you want to preserve the Registry database for future use, copy the ServiceRegistry-base directory to another location before you reinstall the Registry.

Post-uninstallation tasks 

If you made a copy of the Registry database, copy the database again after you reinstall. 

After restoring the database and keystore files (stored in the 3.0 directories), run the following command using platform-specific variants: 

JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.stop export.registryOperatorCert install.cacerts appserver.domain.start

This command enables existing users to have continued use of the Service Registry Web Console. 

Uninstallation Behavior of Web Proxy Server

Table 7–8 Uninstallation Details for Web Proxy Server

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.

Uninstallation Behavior of Web Server

Table 7–9 Uninstallation Details for Web Server

Topic 

Details 

Configuration data and user data 

  • Web Server administrative server and Web Server instances are stopped prior to the completion of the uninstallation.

  • Web Server installation or instance directories can not be removed without running the uninstaller.

Other installations this component requires 

None 

Products requiring this installation 

Components that are configured to use Web Server as web container: Access Manager and Portal Server. Also Application Server Load Balancing Plug-in (if Application Server uses Web Server as its web container). 

Pre-uninstallation tasks 

None 

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 at 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 at the same location.