Chapter 7 Uninstalling Java ES Components

This chapter provides instructions for uninstalling Sun Java Enterprise System (Java ES) components that have been installed using the Java ES installer.

This chapter includes the following sections:

• How the Uninstaller Works

• Verifying Prerequisites

• Reviewing Uninstallation Behavior for Java ES Components

• Running the Uninstall Program in Graphical Mode

• Running the Uninstall Program in Silent Mode

How the Uninstaller Works

Java ES provides an uninstallation program for removing Java ES components that were installed on your system by using the Java ES installer.

Limitations of the Uninstaller

Like the Java ES installer, the uninstaller can be run in graphical or silent mode.

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

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

• 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 Java ES Components.

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

Handling Interdependencies

The uninstaller might behave differently depending on which Java ES 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 Java ES component that has dependent products installed on the host, the uninstaller issues a warning.

  For example, if you attempt to uninstall Access Manager from the host where Portal Server is also installed, the uninstaller warns you that Portal Server cannot function without Access Manager.

• In most cases, you can uninstall a Java ES component if no other Java ES component depends on that component.

  For example, Portal Server depends on Access Manager but Access Manager does not depend on Portal Server. If you attempt to uninstall Portal Server, the uninstaller does not issue a warning because Access Manager can function without Portal Server.

---

Caution –

When uninstalling a Java ES component, you must identify which products are configured for that Java ES component (some additional configuration might be required). Otherwise, you could have Java ES 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

Java ES Component Dependencies From Remote Hosts

Some Java ES component dependencies can be satisfied with Java ES 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 another host could support Access Manager.

Java ES Component Dependencies Resulting From Configuration

The uninstaller does not recognize a Java ES component dependency that is the result of postinstallation configuration.

Verifying Prerequisites

The following table lists the tasks that you should perform before uninstallation. Some of the tasks might not apply to your particular situation.

The left column lists the order in which you should perform the tasks and the right column contains other useful information and the location of instructions.

Table 7–1 Checklist

Task Description	Instructions or Helpful Information
1. Review the needs and behaviors of each Java ES component you plan to uninstall.	Reviewing Uninstallation Behavior for Java ES Components
2. Identify component dependencies that result from configuration and take appropriate measures, such as backing up data, unconfiguring the dependent Java ES component from the supporting Java ES component, or uninstalling the Java ES components in the proper order.	Handling Interdependencies
3. Back up or archive configuration or user data for Java ES components you are uninstalling if you plan to reuse this data in subsequent installations.	Reviewing Uninstallation Behavior for Java ES Components
4. Make sure the Directory Server instance that hosts the configuration directory is running. Note: In most cases, the web container and Directory Server should be running, while the other servers should be shut down before uninstalling.	This Directory Server instance must be running so that the uninstaller can unconfigure the Java ES components that you are uninstalling.

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

• Uninstallation Behavior of Application Server

• Uninstallation Behavior of Directory Server

• Uninstallation Behavior of Message Queue

• Uninstallation Behavior of Monitoring Console

• Uninstallation Behavior of Service Registry

• Uninstallation Behavior of Web Proxy Server

• Uninstallation Behavior of Web Server

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.

Running the Uninstall Program in Graphical Mode

After you have completed the relevant tasks in the Verifying Prerequisites, you are ready to run the uninstall program.

To Start the Windows Wizard/Graphical Uninstall Program

1. Choose Start > Settings > Control Panel.

2. Double-click Add or Remove Programs.

3. Select Sun Java Enterprise Systems.

4. Click Change/Remove.

   The Welcome page to modify or remove the program appears.

To Modify the Current Installation

1. Select Modify from the Install shield wizard to add new program features or to remove the currently installed features.

2. Click Next.

   The Component selection page appears.

3. Examine the components.

   • Components that are installed on your system are enabled and can be selected. Components that are not installed on your system are disabled and cannot be selected.

     • Some components contain subcomponents. Expand the components to view the subcomponents.

     • If you deselect a component that contains subcomponents, expand the component to verify the subcomponent list.

4. Select the components you want to install and deselect the components that you want to uninstall. Click Next.

   The uninstall program modifies the software.

To Remove All the Installed Components

1. Select Remove from the Install shield wizard.

2. Click Next.

   A confirmation dialog box is displayed.

3. Click Yes to confirm Remove.

   The Setup status page is displayed followed by the Unconfigure dialog box.

4. Click Yes to confirm unconfiguration of Java ES components.

   The products are unconfigured and the servers are stopped and removed.

5. The Finish page of the wizard is displayed. You can view the summary of installation or uninstallation details by clicking on View Summary button.

6. Click Finish to exit the uninstallation wizard.

Running the Uninstall Program in Silent Mode

Silent uninstallation is useful for uninstalling Java ES components on multiple hosts that share similar configurations. The procedure for uninstalling in silent mode is similar to the procedure for installing in silent mode as described in Chapter 4, Installing in Silent Mode.

To Perform Uninstallation in Silent Mode

1. Change the directory where the installer is located:

   cd JavaES-install-dir

2. Use the Setup.bat /r command to create the response file.

   Use the /f1 option to specify where the response file is to be created and to provide a name. To avoid unpredictable results, specify an absolute path for the file that has the .iss extension. For example, type:

   Setup.bat /r /f1"C:\Temp\UninstallExample.iss"

   All the data typed and options selected are recorded in the .iss file.

3. The response file is ready for use with the options selected during the record uninstallation. The response file can be edited manually to modify the options recorded.

   You can now use the response file to start silent uninstallation.

4. Change to the directory where the installer is located.

   cd JavaES-install-dir

5. Type the command Setup.bat /s option to initiate a silent mode uninstallation process.

   Use the /f1 option to specify the .iss file location. To avoid unpredictable results, specify an absolute path. For example, type:

   Setup.bat /s /f1"C:\Temp\UninstallExample.iss".

6. (Optional) Use the /f2 option to specify an alternative name and location for the log file. To avoid unpredictable results, specify an absolute path for the file. For example, type:

   Setup.bat /s /f1"C:\Temp\UninstallExample.iss /f2"C:\Setup.log".

   While the uninstaller is running, you can monitor its progress by examining changes to the installation log.