Chapter 8 Uninstalling

This chapter provides instructions for uninstalling Sun Java^TM Enterprise System (Java ES) product component software or other Java ES-related utilities that have been installed during a Java ES installation.

This chapter includes the following sections:

• How the Uninstaller Works

• Verifying Prerequisites

• Planning for Uninstallation

• Running the Uninstaller

• Uninstalling Java ES Reporter

• Uninstalling Sun Cluster Software

• Completing Post-uninstallation Tasks

How the Uninstaller Works

This section contains the following subsections:

• Limitations of the Uninstaller

• Handling Interdependencies

Java ES provides an uninstallation program for removing product components that were installed on your system using the Java ES installer. Like the Java ES installer, the uninstaller can be run in graphical, text-based, or silent mode.

During installation, the Java ES installer places the Java ES uninstaller at the following location:

• Solaris OS: /var/sadm/prod/SUNWentsys5

• Linux and HP-UX: /var/sadm/prod/sun-entsys5

You can use the optional -no parameter to run the uninstaller without uninstalling any software. This option is useful for familiarizing yourself with the uninstaller and for creating a state file for a subsequent silent uninstallation.

Limitations of the Uninstaller

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

• The uninstaller does not remove Java ES shared components.

• The uninstaller must be run separately on each host that contains Java ES product components. Remote uninstallation is not supported. For each host, you can select one or more product 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 need to remove some additional files and directories. For product-by-product information, refer to Reviewing Uninstallation Behavior for Java ES Product Components.

• The uninstaller presents unconfigure pages for product components if needed for multi-session uninstallation.

• The uninstaller does not unconfigure installations on third-party web containers.

• The uninstaller does not unconfigure Access Manager SDK installations on any web container. You must reconfigure the web container manually (for example, restore the original classpath).

Do not use the uninstaller to remove Sun Cluster software unless Sun Cluster software was installed but never used to configure a cluster node. For more information, see Uninstalling Sun Cluster Software

Handling Interdependencies

The uninstaller might behave differently depending on which product 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 product component that has dependent products installed on the local 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 product component if no other product component depends on it.

  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.

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

Product Component Dependencies from Remote Hosts

Some product component dependencies can be satisfied with product 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.

Product Component Dependencies Resulting from Configuration

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

For example, suppose you install both Portal Server and Calendar Server on the same host, and then configure Portal Server to use Calendar Server for the Portal Server calendar channel. After this configuration, Portal Server depends on Calendar Server. However, if you then uninstall Calendar Server, the uninstaller does not warn you that Portal Server depends on Calendar Server because the uninstaller does not know about the 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.

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 Java ES product components behave when they are uninstalled.

This section contains the following subsections:

• Surveying Installed Java ES Software

• Reviewing Uninstallation Behavior for Java ES Product Components

• Granting Administrator Access for the Uninstaller

Surveying Installed Java ES Software

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

To Use the Uninstaller for Viewing Installed Software

1. As root, navigate to the directory where the uninstaller is located:

   • Solaris OS: /var/sadm/prod/SUNWentsys5

   • Linux and HP-UX: /var/sadm/prod/sun-entsys5

2. To survey the local host, 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.

3. Proceed through the uninstaller pages until you reach the list of installed products.

4. After viewing the list of installed product components, exit the uninstaller.

   No software has been uninstalled.

To Use the Solaris prodreg Utility for Viewing Installed Software

Use the prodreg utility to view information about all packages installed on your system, including Java ES 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 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.

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

• Application Server Uninstallation Behavior

• Directory Proxy Server Uninstallation Behavior

• Directory Server Uninstallation Behavior

• HADB Uninstallation Behavior

• Message Queue Uninstallation Behavior

• Monitoring Console Uninstallation Behavior

• Portal Server Uninstallation Behavior

• Portal Server Secure Remote Access Uninstallation Behavior

• Service Registry Uninstallation Behavior

• Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior

• Web Proxy Server Uninstallation Behavior

• Web Server Uninstallation Behavior

Access Manager Uninstallation Behavior

Application Server Uninstallation Behavior

Directory Proxy Server Uninstallation Behavior

Directory Server Uninstallation Behavior

HADB Uninstallation Behavior

Message Queue Uninstallation Behavior

Monitoring Console Uninstallation Behavior

Portal Server Uninstallation Behavior

Portal Server Secure Remote Access Uninstallation Behavior

Service Registry Uninstallation Behavior

Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior

Web Proxy Server Uninstallation Behavior

Web Server Uninstallation Behavior

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 provides additional information.

Running the Uninstaller

After you have completed the relevant tasks in Verifying Prerequisites and planned for component uninstallation behavior, you are ready to run the uninstaller. This section contains information on the three ways in which the uninstaller can be used.

• Running the Uninstaller in Graphical Mode

• Running the Uninstaller in Text-Based Mode

• Running the Uninstaller in Silent Mode

Information on syntax of the uninstall command can be found in Appendix B, Installation Commands.

Running the Uninstaller in Graphical Mode

This section provides instructions for using the interactive graphical interface to uninstall the Java ES product components.

To Start the Graphical Uninstaller

1. (Optional) Provide access to your local display.

   If you are logging in to a remote machine, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.

   • Example for C Shell (machine name myhost):

     setenv DISPLAY myhost:0.0

   • Example for Korn Shell (machine name myhost):

     DISPLAY=myhost:0.0

     You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:

     myhost\> xauth extract - myhost:0.0|rsh -l root serverhost xauth merge -

   ---

   Note –

   For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.

   ---

2. If you are not logged in as root, become superuser.

3. Navigate to the directory where the uninstaller is located:

   • Solaris OS: /var/sadm/prod/SUNWentsys5

   • Linux and HP-UX: /var/sadm/prod/sun-entsys5

4. Start the graphical uninstaller:

   ./uninstall

   The Welcome page is displayed.

5. Click Next to proceed.

   The Select Components page is displayed.

To Select Product Components to Uninstall

1. Examine the product components and select those you want to uninstall.

   • Product components that are installed on your system are enabled and can be selected. Product components that are not installed on your system are disabled.

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

2. After you are satisfied with your selections, click Next.

3. Resolve configuration or dependency issues.

   If the uninstaller detects any recognizable product component dependencies, or potential loss of configuration data among the products selected, warnings are displayed. Your choices are:

   1. Click Continue to continue with uninstallation.

   2. Click Close to return to the Choose Software Components page.

4. If unconfigure pages are displayed, enter the information requested for the product component.

To Grant Administrator Access

Depending on the product components you selected for removal, the uninstaller prompts you for administrator IDs and passwords. For details on the information you must provide the uninstaller, refer to Granting Administrator Access for the Uninstaller.

In addition, the uninstaller might also prompt you for a port number or a host name.

1. Provide the required administrator information.

2. Click Next to proceed to the Ready To Uninstall page.

To Uninstall Software

Before removing software from your system, the uninstaller lists the product components you have selected for removal and the total disk space that will be reclaimed.

1. Review the uninstallation selections you have made and make any changes needed as follows:

   1. Click Back through successive pages until the Select Components page is displayed.

   2. Make changes as needed page.

   3. Click Next to proceed again through the uninstaller pages.

      The uninstaller remembers previously-specified values. You can modify any value you previously specified.

2. Click Next when you are satisfied with your selections.

   The uninstaller begins removing software from your system and displays the following:

   • A progress bar that displays the overall completion percentage

   • The name of the package currently being removed

   • The Uninstallation Complete page displays after all product component software has been removed.

3. Click View Summary or View Log for information about the uninstallation.

   • Uninstallation summary. Shows the product components that were uninstalled and a list of configuration information for the product components.

   • Uninstallation log. Shows all messages that were generated by the uninstaller during uninstallation.

   • You can also review the uninstallation summary and log files:

     Solaris OS: /var/sadm/install/logsLinux and HP-UX: /var/opt/sun/install/logs

4. Click Close to exit the uninstaller.

5. If you uninstalled Access Manager or Service Registry, go to Completing Post-uninstallation Tasks.

Running the Uninstaller in Text-Based Mode

The text-based interface allows you to run the uninstaller directly from a terminal window by responding to prompts displayed in the window. For usage guidelines, refer to How to Use the Text-Based Interface.

If you have problems during uninstallation, refer to Chapter 9, Troubleshooting.

To Start the Uninstaller in Text-Based Mode

1. If you are not logged in as root, become superuser.

2. Navigate to the uninstaller directory:

   • Solaris OS: /var/sadm/prod/SUNWentsys5

   • Linux and HP-UX: /var/sadm/prod/sun-entsys5

3. Run the uninstaller:

   ./uninstall -nodisplay

   The Welcome message is displayed followed by a list of all possible Java ES product components on your system.

To Select Product Components for Uninstallation

The uninstaller selects for removal any Java ES product components it finds on your system by listing the numbers corresponding to the installed product components. Product components that are not installed on your system are disabled and cannot be chosen. You can choose to uninstall all installed components, or select only some of the installed components for uninstallation.

1. Choose product components for uninstallation.

   • To uninstall all installed product components, press Return.

   • To choose specific product components, type a comma-separated list of the numbers corresponding to the product components you want to uninstall, and press Return.

2. Resolve configuration or dependency issues.

   If the uninstaller detects product component dependencies among the products selected for removal, warnings about a potential loss of configuration data are displayed. Your choices are:

   1. Type Yes and press Return to continue with uninstallation.

   2. Type No and press Return to return to Component Selection.

   3. Type the character ! and press Return to exit the uninstallation.

3. If unconfigure pages are displayed, enter the information requested for the product component.

To Grant Administrator Access

If you selected a product component for which the uninstaller needs an administrative ID or password, the uninstaller prompts you for administrator IDs and passwords.

For details on the information you must provide the uninstaller, refer to Granting Administrator Access for the Uninstaller.

---

Note –

Depending on the product components you selected for removal, the uninstaller might also prompt you for a port number or a host name.

---

To Uninstall the Software

Before removing software from your system, the uninstaller displays a summary page, showing the product components selected for removal.

1. Review your selections.

   1. If changes are needed, type the < character and press Return to go back through successive pages until the Component Selection list appears.

   2. Make changes as needed on the Component Selection list.

   3. Proceed again through the uninstaller screens.

2. When you are satisfied with your selections, type the number 1 and press Return.

   The uninstaller begins removing software from your system. During uninstallation, the uninstaller displays a progress bar that displays the overall completion percentage.

   After all product component software has been removed, you can view the uninstallation summary and log.

3. Type 1 or 2 and press Return to see information about the uninstallation.

   • Uninstallation summary. Type 1 to see the product components that were uninstalled and a list of configuration information for the product components.

   • Uninstallation log. Type 2 to list all messages that were generated by the uninstaller during uninstallation.

     You can also view the uninstallation summary and log files:

     Solaris OS: /var/sadm/install/logsLinux and HP-UX: /var/opt/sun/install/logs

4. Type the ! character to exit the uninstaller.

   If you uninstalled Access Manager or Service Registry, go to Completing Post-uninstallation Tasks.

Running the Uninstaller in Silent Mode

Silent uninstallation is useful for uninstalling Java ES product 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 5, Installing in Silent Mode.

To Create a State File

To perform a silent uninstallation, you must first generate a state file by running an interactive uninstallation session in either graphical or text-based mode. For more information, refer to Generating the Initial State File.

1. If you are not logged in as root, become superuser.

2. Navigate to the uninstaller directory:

   • Solaris OS: /var/sadm/prod/SUNWentsys5

   • Linux and HP-UX: /var/sadm/prod/sun-entsys5

3. If you are using the graphical interface of the uninstaller, you might need to provide access to your local display. See Running the Uninstaller in Graphical Mode.

4. Run the silent uninstaller. For example:

   ---

   Tip –

   Include the –no option if you do not want to uninstall software in this session.

   ---

   Graphical mode:

   ./uninstall -saveState statefile_path

   Text-based mode, software not uninstalled:

   ./uninstall -no -nodisplay -saveState statefile_path

   To see the full syntax for the uninstall command, refer to uninstall Command.

5. Proceed through the uninstaller to completion.

   As you respond to the prompts, the uninstaller records your answers in the specified state file. When you complete the uninstallation, the state file is available in the location that you specified. If you used the –no option, no software was uninstalled.

6. Make a copy of the state file for each host on which you are going to perform a silent uninstallation.

7. Edit each file providing information specific to the host where you will run that silent uninstallation.

   For guidelines on editing state files, refer to Editing the State File. Editing the state file might also include generating a state file ID, as explained in Creating a Platform-Appropriate State File ID.

To Run the Uninstaller in Silent Mode

1. Verify that you have properly prepared and edited the state file for the host where you want to uninstall Java ES product components.

2. If you are not logged in as root, become superuser.

3. Navigate to the uninstaller directory:

   • Solaris OS: /var/sadm/prod/SUNWentsys5

   • Linux and HP-UX: /var/sadm/prod/sun-entsys5

4. Start the uninstaller. For example:

   ./uninstall -noconsole -state statefile_path

   To see the full syntax for the uninstall command, refer to uninstall Command.

To Monitor the Progress of a Silent Uninstallation

1. In a terminal window, navigate to the log file directory:

   Solaris OS: /var/sadm/install/logsLinux and HP-UX: /var/opt/sun/install/logs

2. Locate the log files for the current uninstallation. The log file of interest for monitoring purposes is:

   Java_Enterprise_System_5_uninstall.Btimestamp

   The timestamp variable represents the time the log was created. The variable has the following format MMddhhmm, where:

   MM

   Specifies the month

   dd

   Specifies the date

   hh

   Specifies the hour

   mm

   Specifies the minute

3. Use the tail command to watch messages as they are written to the logs. For example:

   tail -f logfile_name

   To exit the tail program, press Ctrl+C.

Uninstalling Java ES Reporter

Java ES Reporter is not a component managed by the Java ES installer, therefore, you cannot use the uninstaller to remove Reporter.

To Uninstall Java ES Reporter

1. Disable Java ES Reporter

   Follow instructions contained in Java ES Reporter Postinstallation Configuration.

2. As root, delete the following files:

   Solaris OS	/opt/SUNWmfwk/lib/commons-codec-1.3.jar /opt/SUNWmfwk/lib/commons-httpcclient-3.0.jar /opt/SUNWmfwk/lib/mfwk_reporter.jar /etc/opt/SUNWmfwk/config/reporter/config.properties /var/opt/SUNWmfwk/jobtool/reporter/job_measurement_reporter.xml /etc/cacao/instances/default/modules/com.sun.mjwk.reporter.xml /etc/opt/SUNWmfwk/config/reporter/config_state.properties
   Linux and HP-UX	/opt/sun/mfwk/share/lib/commons-codec-1.3.jar /opt/sun/mfwk/share/lib/commons-httpcclient-3.0.jar /opt/sun/mfwk/share/lib/mfwk_reporter.jar /etc/opt/sun/mfwk/config/reporter/config.properties /var/opt/sun/mfwk/jobtool/reporter/job_measurement_reporter.xml /etc/opt/sun/cacao/instances/default/modules/com.sun.mjwk.reporter.xml /etc/opt/sun/mfwk/config/reporter/config_state.properties

Uninstalling Sun Cluster Software

Do not use the Java ES uninstaller to remove Sun Cluster software unless Sun Cluster software was installed but never used to configure a cluster node. Sun Cluster software should be uninstalled using the utilities provided with the Sun Cluster software. Sun Cluster Core and Sun Cluster Agents for Sun Java System must be removed together. Sun Cluster Geographic Edition software must be removed before removing Sun Cluster software. For more information on unconfiguring and uninstalling Sun Cluster software, refer to the Sun Cluster Software Installation Guide for Solaris OS.

After uninstalling Sun Cluster software manually, run the Java ES uninstaller to remove Sun Cluster components from the product registry.

Completing Post-uninstallation Tasks

This section provides instructions for tasks that you might need to perform after uninstalling Java ES product components from your system. The actual tasks required depend on which product components you chose to uninstall.

• Access Manager Post-uninstallation Issues

• Access Manager Post-uninstallation Task (Application Server Not Uninstalled)

• Service Registry Post-uninstallation Tasks

• Web Server Post-uninstallation Tasks (Web Server Not Uninstalled)

Access Manager Post-uninstallation Issues

If you uninstall Access Manager but not its web container (Application Server or Web Server), you need to apply configuration changes to the instance where Access Manager was deployed.

In some cases the uninstaller might not be able to remove some or all of the Access Manager files. In this case, do a final cleanup by removing the following default directories and their contents:

• For Solaris OS: /opt/SUNWam

• For Linux and HP-UX: /opt/sun/identity

or, if Access Manager was not installed in the default location:

AccessManager_base/identity

Access Manager Post-uninstallation Task (Application Server Not Uninstalled)

If you uninstall Access Manager but not the Application Server in which it is deployed, you must complete the following procedure.

To Restart Application Server After Access Manager Uninstallation

1. If necessary, start the Application Server admin instance. For example, on a Solaris host:

   cd /opt/SUNWappserver/appserver/bin ./asadmin start-domain --user admin_user --passwordfile path_to_admin-password_file domainname

2. In a browser window, go to the Application Server administration console. The default URL is https://hostname:4849 .

3. In the left pane, click the key to the left of Application Server Instances.

4. Select the server or the name of the Application Server instance on which Access Manager was deployed.

5. Click Apply Changes.

Service Registry Post-uninstallation Tasks

In some cases, the uninstaller might not be able to remove some or all of your installation files. To do a final cleanup, remove the ServiceRegistry-base directory and its contents at the following location:

• Solaris OS: /opt/SUNWsrvc-registry

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

The directory that contains the Service Registry database, domain, and keystores is not removed when you uninstall the Registry:

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

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

You can remove it manually if you want. However, to preserve the database for use in a future installation or release, copy the following directory to another location before you reinstall the Registry, then copy it back after you reinstall:

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

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

For reinstallation, if you made a copy of the Registry database before you installed Service Registry, copy it back after you reinstall. After restoring the database and keystore files (stored in the 3.0 directories), run the following command using platform-specific variants:

.../ant —f build-install.xml appserver.domain.stop export.registryOperatorCert install.cacerts \
appserver.domain.start

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

Web Server Post-uninstallation Tasks (Web Server Not Uninstalled)

If you uninstall Access Manager but not the Web Server in which it is deployed, you must complete the following procedure.

To Restart Web Server After Access Manager Uninstallation

1. If necessary, start the Web Server admin instance. Refer to To Start Web Server .

2. Access the Web Server administration console. For example:

   /var/opt/SUNWwbsvr7 instance-config-root /admin-server/bin/startserv

3. Click Apply Changes to restart the web container.