Chapter 12 Uninstalling Components

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

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, the middle column describes the action to take, and the right column contains other useful information and the location of instructions.

Table 12-1 Pre-uninstallation Checklist
Order	Task Description	Instructions or Helpful Information
1	Review the needs and behavior of all the software that has been installed by the Java ES installer on each host in your system. Identify component dependencies that result from configuration and take appropriate measures, such as backing up data, unconfiguring the dependent component from the supporting component, or uninstalling the components in the proper order.	Planning for Uninstallation Component Dependencies Resulting from Configuration
2	Review the needs and behaviors of each component you are going to uninstall.	Reviewing Uninstallation Behavior for Java ES Components
3	Make a copy of the product registry file. The backup copy is helpful in recovering from a failed uninstallation.	On Solaris: /var/sadm/install/productregistry On Linux: /var/opt/sun/install/productregistry
4	Back up or archive configuration or user data for components you are uninstalling if you plan to reuse this data in subsequent installations.	Reviewing Uninstallation Behavior for Java ES Components
5	Make sure the Directory Server instance that hosts the configuration directory is running.	This Directory Server instance must be running so the uninstaller can unconfigure the components you are uninstalling.
6	If necessary, gather administrator access information for Administration Server, Directory Server, and Access Manager.	Granting Administrator Access for the Uninstaller.
7	Before uninstalling Messaging Server that has been installed on its own system, unconfigure Administration Server.	To unconfigure Administration Server: /usr/sbin/mpsadmserver unconfigure

How the Uninstaller Works

Java ES provides an uninstallation program for removing components that were installed on your system using 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:

After all Java ES components are uninstalled, this file is automatically removed.

General Behavior

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


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

The uninstaller checks component dependencies only for the system on which it is running, issuing warnings when it discovers a dependency.

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



Caution	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 components you installed and how they are interrelated.

For example, Portal Server depends on Access Manager. 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 component, you must identify which products are configured for that component (some additional configuration might be required). Otherwise, you could have components on your system that are configured to support products that are no longer present.

Component Dependencies from Remote Hosts

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

Component Dependencies Resulting from Configuration

The uninstaller does not recognize a 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.

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

Surveying Installed Java ES Software

Perform one of the following procedures to review the Java ES 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:

cd /var/sadm/prod/entsys

To survey the local system, run the uninstaller without uninstalling software.

For graphical mode:

./uninstall -no

For text-based mode:

./uninstall -no -noconsole

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

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

After viewing the list of installed 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 Java ES components. This information is useful when checking for component dependencies. The prodreg utility also indicates packages that are incomplete and might need special handling. More information on prodreg can be found in the man pages. On the Solaris 10, and Solaris 9 operating systems and some versions of the Solaris 8 operating system, run the utility as follows:

Reviewing Uninstallation Behavior for Java ES Components

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

Access Manager Uninstallation Behavior

Table 12-2 Access Manager Uninstallation Details
Topic	Details
Configuration Data	No entries in Directory Server will be removed (including Access Manager specific data).
Dependencies	Directory Server Web Server or Application Server
Products Requiring this Installation	Portal Server (must reside on the same host as Access Manager) 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	None
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 (i.e. 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

Administration Server Uninstallation Behavior

Table 12-3 Administration Server Uninstallation Details
Topic	Details
Configuration Data	Proxy information for managing other servers is lost upon uninstallation. Configuration data used by Administration Server to manage other servers remains within the Configuration Directory Server. This information can be reused upon a subsequent installation of Administration Server.
Dependencies	Directory Server
Products Requiring this Installation	Directory Proxy Server and Messaging Server require Administration Server. Directory Server can be configured to require Administration Server. Note: If you remove Administration Server and not Directory Server, then Directory Server must be managed using other utilities that come with Directory Server. Refer to Directory Server documentation at http://docs.sun.com/coll/DirectoryServer_05q1 for more information.
Tasks Before Uninstallation	Make sure the Configuration Directory Server is running, and that you can provide the administrator user ID and password.
Post-Uninstallation	None

Application Server Uninstallation Behavior

Table 12-4 Application Server Uninstallation Details
Topic	Details
Configuration Data and User Data	The default domain created during installation is removed during uninstallation. Configured administrative 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	Access Manager (if configured for Application Server) Portal Server (if configured for Application Server) Communications Express (if configured for Application 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. Default locations for Application Server directories are: Solaris: /var/opt/SUNWappserver /opt/SUNWappserver Linux: /var/opt/sun/appserver /opt/sun/apserver Refer to Table 12-11 for information on Message Queue post-uninstallation tasks.

Calendar Server Uninstallation Behavior

Table 12-5 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.
Dependencies	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	Portal Server (when configured to use Calendar Server for the Portal Server’s calendar channel) 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 Administration Guide (http://docs.sun.com/doc/819-0024.).
Post-Uninstallation Tasks	Remove any remaining log files and Calendar Server directories that are not needed.

Communications Express Uninstallation Behavior

Table 12-6 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: /opt/SUNWuwc Linux: /opt/sun/uwc Application Deployment created by default during configuration: Solaris: /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.
Dependencies	Application Server (if configured to run under Application Server) Web Server (if configured to run under Application Server) Identity Server (when configured for SSO) Directory Server Calendar Server Messaging Server
Products Requiring this Installation	None
Pre-Uninstallation Tasks	Unconfigure Communications Express. Refer to the “Unconfiguring Communications Express” section in the Sun Java System Communications Express Administration Guide, http://docs.sun.com/doc/819-0115.
Post-Uninstallation Tasks	Remove any remaining log files and Communications Express directories that are not needed.

Directory Server Uninstallation Behavior

Table 12-7 Directory Server Uninstallation Details
Topic	Details
Configuration Data and User Data	If you are uninstalling the Directory Server instance hosting the configuration directory, the configuration directory information is removed during uninstallation. 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/DirectoryServer_05q1 for more information. Caution: You do not receive a warning before proceeding with uninstallation of your configuration directory (containing configuration information under the o=NetscapeRoot suffix). If you uninstall a centralized configuration directory that other directories rely on for configuration information, you cannot subsequently administer those directories.
Dependencies	None
Products Requiring this Installation	Administration Server Calendar Server Directory Proxy Server Access Manager Instant Messaging Messaging Server Portal Server Communications Express
Pre-Uninstallation Tasks	Back up the configuration directory for Directory Server and the Directory Server LDAP database as needed. Make sure the Directory Server instance hosting the configuration directory is running, and that you can provide the administrator user ID and password.
Post-Uninstallation Tasks	Uninstallation of Directory Server might require manual removal of remaining files and directories.

Directory Proxy Server Uninstallation Behavior

Table 12-8 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.
Dependencies	Directory Proxy Server has a logical dependency upon the local or remote Directory Server that acts as Configuration Directory Server. Directory Proxy Server depends upon a local Administration Server.
Products Requiring this Installation	None
Pre-Uninstallation Tasks	None
Post-Uninstallation Tasks	None

Instant Messaging Uninstallation Behavior

Table 12-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.
Dependencies	Directory Server Access Manager SDK
Products Requiring this Installation	Portal Server, when configured to use Instant Messaging channel
Pre-Uninstallation Tasks	None
Post-Uninstallation Tasks	None

Messaging Server Uninstallation Behavior

Table 12-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.
Dependencies	Directory Server Administration Server (must reside on same host) Web Server (for mailing functionality such as filters) Access Manager (if using Schema 2)
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 12-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.
Dependencies	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 JES registry. More information may be found in the Java Enterprise System Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).
Post-Uninstallation Tasks	If you are not planning to reinstall Message Queue, use the commands in the component documentation to clean up your system. Message Queue documentation is available here: http://docs.sun.com/coll/MessageQueue_35_SP1

Portal Server Uninstallation Behavior

Table 12-12 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.
Dependencies	Directory Server Application Server or Web Server (Can also be configured to be dependent on IBM WebSphere or BEA WebLogic.) Access Manager If configured to use Portal Server Channels: Calendar Server Messaging Server Instant Messaging
Products Requiring this Installation	None
Pre-Uninstallation Tasks	None
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-related Post-uninstallation. 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 12-13 Portal Server Secure Remote Access Details for Uninstallation
Topic	Details
Configuration Data	All configuration data for the Portal Server Secure Remote Access Core 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 components.
Dependencies	Portal Server Secure Remote Access depends on Portal Server. Portal Server, Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy components depend on Access Manager SDK. Portal Server and Portal Server Secure Remote Access Support must reside on the same host and in the same directory. 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 component without removing any dependent 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

Sun Cluster Uninstallation Behavior

Table 12-14 Sun Cluster Software 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.
Dependencies	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.
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 Server Uninstallation Behavior

Table 12-15 Web Server Uninstallation Details
Topic	Details
Configuration Data and User Data	Configuration data and user data are not removed during uninstallation. The Web Server administrative server instance and configured Web Server instance directories are preserved under the installation directory. The initially-configured document root directory is also preserved. Web Server administrative server and Web Server instances are stopped prior to the completion of the uninstallation.
Dependencies	None
Products Requiring this Installation	Access Manager, if configured to run under Web Server Portal Server, if configured to run under Web Server Communications Express Application Server Load Balancing Plugin
Pre-Uninstallation Tasks	None
Post-Uninstallation Tasks	To preserve configuration data, backup 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. Manually remove the installation directory and any custom configuration before reinstalling to the same location.

Granting Administrator Access for the Uninstaller

Depending on the components you choose to uninstall, you might need to grant the uninstaller administrator access to Access Manager, Administration Server, and Directory Server.

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 12-16 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.
Administration Server
Administrator User ID ADMINSERV_CONFIG_ADMIN_USER	User ID of the configuration directory administrator. Administration Server uses this identity when managing configuration directory data.
Administrator User Password ADMINSERV_CONFIG_ADMIN_PASSWORD	Password for the configuration directory administrator.
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.

Running the Uninstaller

After you have completed the relevant tasks in the Prerequisites, you are ready to run the uninstaller. This section contains information on the three ways in which the uninstaller can be accessed.

Running the Uninstaller in Graphical Mode

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

To Start the Graphical Uninstaller

(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 (http://docs.sun.com/doc/816-0279).

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

Start the graphical uninstaller:

./uninstall

The Welcome page is displayed.

Click Next to proceed.

The Select Components page is displayed.

To Select Components to Uninstall

Examine the components and select those you want to uninstall.

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.

After you are satisfied with your selections, click Next.

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

Click Continue to continue with uninstallation.

Click Close to return to the Component Selection page.

To Grant Administrator Access

Depending on the 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.

To Confirm Uninstallation Readiness

Before removing software from your system, the uninstaller displays the Ready to Uninstall page which lists the components you have selected for removal and the total disk space that will be reclaimed.


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

Review the uninstallation selections you have made.

If changes are needed, click Back through successive pages until the Component Selection page is displayed.

Make changes as needed on the Component Selection page.

Click Next to proceed again through the uninstaller pages.

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

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

To Complete the Uninstallation Session

After all component software has been removed, the uninstaller displays the Uninstallation Complete page.

Go to Post-uninstallation if you uninstalled Access Manager or Messaging Server.

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.

To Start the Uninstaller in Text-Based Mode

To Select Components for Uninstallation


Tip	Refer to How to Use the Text-Based Interface to learn about text-based prompts for uninstallation.

The uninstaller selects for removal any Java ES components it finds on your system by listing the numbers corresponding to the installed components. Press Return to uninstall all components. Alternately, choose specific components by typing a comma-separated list of the numbers corresponding to the components you want to uninstall, and press Return.



Note	Components that are not installed on your system are disabled and cannot be chosen.

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

Type Yes and press Return to continue with uninstallation.

Type No and press Return to return to Component Selection.

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

To Grant Administrator Access

If you selected a 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.

To Confirm Uninstallation Readiness

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

To Complete the Uninstallation Session

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


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

Go to Post-uninstallation if you uninstalled Access Manager or Messaging Server.

Running the Uninstaller 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 9, "Installing in Silent Mode".

To Generate a State File

To perform a silent uninstallation, you must first generate a state file by running a false uninstallation in either graphical or text-based mode. Refer to Generating a State File for details.

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

If you are using the graphical interface of the uninstaller, provide access to your local display. See To Start the Graphical Uninstaller.

Run the silent uninstaller. For example:

Graphical mode:

./uninstall -no -saveState statefile_name

Text-based mode:

./uninstall -no -nodisplay -saveState statefile_name

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

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. No software has been uninstalled.

To Edit the State File for the Hosts

To Run the Uninstaller in Silent Mode

To Monitor the Progress of a Silent Uninstallation

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

On Solaris: /var/sadm/install/logs
On Linux: /var/opt/sun/install/logs

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

Java_Enterprise_System_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

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 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. For more information on unconfiguring and uninstalling Sun Cluster software, refer to your Sun Cluster software documentation at http://docs.sun.com/coll/1124.3 for SPARC or http://docs.sun.com/coll/1125.2 for x86.

After uninstalling Sun Cluster software, run /var/sadm/prod/entsys/uninstall to remove Sun Cluster and Sun Cluster Agents from the product registry.

Post-uninstallation

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

Access Manager-related Post-uninstallation

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.

Application Server Post-uninstallation

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

Web Server Post-uninstallation

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

Access Manager Post-uninstallation

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 these two directories and their contents:

Messaging Server Post-uninstallation

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 Messaging Server base directory and its contents. The default base directory is at the following location:

You can also remove the configuration directory for Messaging Server at the following location:

After uninstalling Messaging Server, undo any sendmail configuration for Messaging Server.

Previous Contents Index Next
Sun Java Enterprise System 2005Q1 Installation Guide