Chapter 10 Uninstalling Software

This chapter describes how to use the Java Enterprise System uninstaller to remove Java Enterprise System component products from your system. This chapter should be read in its entirety before proceeding with uninstalling Java Enterprise System software.

Overview of Uninstallation

The Java Enterprise System uninstaller offers the following uninstallation modes:

Interactive uninstallation using a graphical interface

Interactive uninstallation in a terminal window

Silent uninstallation using a parameter file you provide

These uninstallation modes correspond to the modes available for installing Java Enterprise System. For information on choosing an uninstallation mode, refer to "Choosing an Installation Mode".

During installation, the Java Enterprise System installation program places the Java Enterprise System uninstaller at the following location:

About the Uninstaller

The Java Enterprise System uninstaller behaves differently, according to your specific installation of Java Enterprise System. Keep the following in mind when running the uninstaller:

The uninstaller must be run separately on each host containing Java Enterprise System components.

The uninstaller does not remove any Java Enterprise System shared components.

The uninstaller only removes component products that were installed by the Java Enterprise System installer.

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

The uninstaller might remove configuration and user data files.

Shared Components

The Java Enterprise System uninstaller does not remove shared components previously installed or upgraded by the Java Enterprise System installer.

Some shared components, for example the J2SE component, may be used by software other than Java Enterprise System components. Other shared components may be used by Sun software products installed outside of the Java Enterprise System.

Typically, you do not remove a shared component. However, if you want to remove Java Enterprise System shared components from a system, use the pkgrm command. Refer to "Packages Installed for Shared Components" of Appendix D for a list of the components that are installed or upgraded by the Java Enterprise System installer.

Product Interdependencies

Before uninstalling any component product you must consider the following interdependencies for that product:


Caution	Removing a shared component might affect the operation of other applications and software on your system that use the shared component.

The component products that depend on the product you are uninstalling

The component products supported by the product you are uninstalling

The following figure provides an example of interdependencies between component products: Product A (Portal Server), Product B (Identity Server), and Product C (Directory Server).

Recognized Dependencies

The Java Enterprise System uninstaller recognizes when one component product depends on another component product only if both products are installed on the same host. If you attempt to uninstall a component that has dependent products on the same host, the uninstaller issues a warning before proceeding with the uninstallation.

For example, assume that all components in Figure 10-1 reside on the same host. If you attempt to uninstall Identity Server from that host, the uninstaller warns you that Portal Server depends on Identity Server.

Continuing with this example, when you attempt to uninstall Identity Server the uninstaller does not recognize that Directory Server supports Identity Server. The uninstaller does not issue a warning that Directory Server supports Identity Server. This and other unrecognized interdependencies are discussed further in the following section.

Unrecognized Interdependencies

The Java Enterprise System uninstaller does not recognize the following interdependencies:

Product Dependencies from Remote Hosts

Products Supporting Other Component Products

Product Dependencies Resulting from Configuration

The following sections provides details on uninstaller behavior for each of these unrecognized interdependencies. "Component Product Details" provides specific interdependency information for each component product.

Product Dependencies from Remote Hosts

A component product dependency that can be optionally satisfied with the products deployed on separate hosts. For example, Figure 10-2 illustrates a dependency of Identity Server on Directory Server with the products deployed on separate hosts.

The uninstaller does not recognize the dependency relationship between these products, even if the products are deployed on the same host.

For example, if you attempt to uninstall Directory Server, the uninstaller does not warn you that Identity Server depends on Directory Server, even if both products are deployed to the same host. This is because after uninstalling Directory Server, you can still configure another Directory Server instance on another host to support Identity Server.

The following component product dependency relationships can be satisfied with the products deployed on separate hosts:

Identity Server depending on Directory Server

Administration Server depending on Directory Server

Calendar Server depending on Directory Server

Products Supporting Other Component Products

The uninstaller does not recognize when one component product supports another component product, as illustrated in the following figure.

For example, Identity Server supports Portal Server. If you attempt to uninstall Portal Server the uninstaller does not warn you that Identity Server supports Portal Server and proceeds with the uninstallation.

Product Dependencies Resulting from Configuration

The uninstaller does not recognize a product dependency when one component product depends on another component product, but the dependency is the result of configuration after the products have been installed.

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’s calendar channel. In this scenario, Portal Server now depends on Calendar Server. If you then attempt to uninstall Calendar Server, the uninstaller will not warn you that Portal Server depends on Calendar Server.

Component Product Details

This section provides component product information you should consider before proceeding with uninstallation.


Caution	When uninstalling a component product, you must identify which products support that component and take appropriate measures. Otherwise you may have component products remaining on your system configured to support products no longer on your system.


Caution	You must identify any product dependencies that arise during configuration and take appropriate measures, such as back up data for the component product, unconfigure the dependent product from the supporting product, or uninstall the components in the proper order.

Table 10-1 Administration Server Details for Uninstallation
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 of Directory Server. This information can be reused upon subsequent installation of Administration Server.
Dependencies	Directory Server
Required to Support	Directory Proxy Server and Message 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 available with Directory Server. Refer to Directory Server documentation at http://docs.sun.com/coll/S1_DirectoryServer_52 for more information.
Tasks Before Uninstallation	Make sure the Directory Server instance hosting the configuration directory is running, and that you can provide the administrator user ID and password. For more information, refer to "Uninstaller Cannot Connect to Configuration Directory Server".
Tasks After Uninstallation	None.

Table 10-2 Application Server Details for Uninstallation
Topic	Details
Configuration Data and User Data	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.
Required to Support	Identity Server (if configured for Application Server) Portal Server (if configured for Application Server)
Tasks Before Uninstallation	To preserve configuration data, make a copy of the administration domain directories.
Tasks After 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: /etc/opt/SUNWappserver7 /var/opt/SUNWappserver7 /opt/SUNWappserver7 Refer to Table 10-9 for information on Message Queue post-uninstallation tasks.

Table 10-3 Calendar Server Details for Uninstallation
Topic	Details
Configuration Data and User Data	All configuration data and user data remains after uninstallation, and will be overwritten upon subsequent installation. Customizations to Calendar Server are removed during uninstallation.
Dependencies	Directory Server Identity Server, when configured for Single Sign On or if you want to use Schema 2 Messaging Server (or some other mail server, for Calendar Server email notification service)
Required to Support	Portal Server (when configured to use Calendar Server for the Portal Server’s calendar channel)
Tasks Before Uninstallation	If you plan to reuse configuration data and user data, follow the migration process as described in Appendix C, “Calendar Server 5.x to 6.0 Upgrade/Migration Process,” of the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems. This manual is available at http://docs.sun.com/doc/816-6707-10.
Tasks After Uninstallation	Remove any remaining log files and Calendar Server directories that are not needed.

Table 10-4 Directory Server Details for Uninstallation
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/S1_DirectoryServer_52 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
Required to Support	Administration Server Calendar Server Directory Proxy Server Identity Server Instant Messaging Messaging Server Portal Server
Tasks Before Uninstallation	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. For more information, refer to "Uninstaller Cannot Connect to Configuration Directory Server".
Tasks After Uninstallation	Uninstallation of Directory Server might require manual removal of remaining files and directories.

Table 10-5 Directory Proxy Server Details for Uninstallation
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 Server Administration Server
Required to Support	None.
Tasks Before Uninstallation	None.
Tasks After Uninstallation	None.

Table 10-6 Identity Serve Details for Uninstallation
Topic	Details
Configuration Data	Configuration data for Identity Server is removed during uninstallation.
Dependencies	Directory Server Web Server or Application Server (Can also be configured to be dependent on IBM WebSphere or BEA WebLogic.)
Required to Support	Portal Server Calendar Server, when configured for Single Sign On (SSO) Instant Messaging, when configured for SSO Messaging Server, when configured for SSO Identity Server must reside on the same host as Portal Server
Tasks Before Uninstallation	If Identity Server is deployed to IBM WebSphere or BEA WebLogic, then WebSphere or WebLogic must be running before starting the Java Enterprise System uninstaller.
Tasks After Uninstallation	After uninstall has completed, you must unconfigure Identity Server entries from the Web container to which Identity Server is deployed. Additionally, remove the following files located in the directory /var/sadm/install if they exist: .lockfile .pkg.lock

Table 10-7 Instant Messaging Details for Uninstallation
Topic	Details
Configuration Data and User Data	All configuration data remains after uninstallation, and can be reused upon subsequent installation. All user data is removed during uninstallation.
Dependencies	Directory Server Identity Server SDK
Required to Support	Portal Server, when configured to use Instant Messaging channel.
Tasks Before Uninstallation	None.
Tasks After Uninstallation	None.

Table 10-8 Messaging Server Details for Uninstallation
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) Identity Server (if using Schema 2)
Required to Support	Calendar Server Portal Server, when configured with messaging channels.
Tasks Before Uninstallation	None.
Tasks After Uninstallation	Depending on your circumstances, you might have to perform post-uninstallation tasks as explained in "Messaging Server Tasks".

Table 10-9 Message Queue Details for Uninstallation
Topic	Details
Configuration Data	Instance-specific configuration data remains after uninstallation, and can be reused upon subsequent installation. Message Queue user repository and access control file are removed during uninstallation.
Dependencies	Directory Server (optional)
Required to Support	Application Server Application Server and Message Queue must both be installed on the same host.
Tasks Before Uninstallation	If you want to preserve the Message Queue flat file user repository and the Message Queue access control file, make a backup copy of the following files, which can be restored after reinstalling or upgrading Message Queue: /etc/imq/passwd /etc/imq/accesscontrol.properties If you are not planning to reinstall Message Queue, stop any running brokers and their Message Queue clients. Use the commands in the component product documentation to clean up.
Tasks After Uninstallation	If you are not planning to reinstall Message Queue, use the commands in the component product documentation to clean up your system. Message Queue documentation is available at http://docs.sun.com/coll/S1_MessageQueue_301_SP2

Table 10-10 Portal Server Details for Uninstallation
Topic	Details
Configuration Data and User Data	Configuration Data is removed during uninstallation. Unconfiguration includes removing services created in Identity Server by Portal Server. Customized configuration data is not removed by the uninstaller. Customized data includes items such as display profiles, property files, resources strings, and other customizations. Providers for user channels are not removed during installation. Providers can be reused upon subsequent installation. For more information, refer to Portal Server documentation at http://docs.sun.com/coll/S1_PortalServer_62. Customized configuration data can be reused upon subsequent installation only if Portal Server is reinstalled to the same host with the same configuration. For more information, refer to Portal Server documentation at http://docs.sun.com/coll/S1_PortalServer_62.
Dependencies	Directory Server Application Server or Web Server (Can also be configured to be dependent on IBM WebSphere or BEA WebLogic.) Identity Server If configured to use Portal Server Channels: Calendar Server Messaging Server Instant Messaging
Required to Support	None.
Tasks Before Uninstallation	None.
Tasks After Uninstallation	If you are running Portal Server within Web Server and you choose to remove Portal Server only, you must restart Identity Server. For more information, refer to "Portal Server, Restarting Identity Server" .If deployed to the IBM WebSphere web container, there may be additional uninstallation tasks.

Table 10-11 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 installation. All web applications that have been deployed are undeployed. User do not have configuration data access to Portal Server SRA Gateway, Netlet Proxy, and Rewriter Proxy components.
Dependencies	Portal Server SRA depends on Portal Server. Portal Server SRA Gateway, Netlet Proxy, and Rewriter Proxy components depend on Identity Server SDK. Portal Server and Portal Server SRA Support must reside on the same host and in the same directory. Identity Server 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 SRA Component without removing any dependent component. You can remove Gateway and leave Identity Server SDK on the host.
Required to Support	None.
Tasks Before Uninstallation	None.
Tasks After Uninstallation	None.

Table 10-12 Sun Cluster software Details for Uninstallation
Topic	Details
Configuration Data	Do not use the Java Enterprise System uninstaller to remove Sun Cluster software, except in the trivial circumstance to remove software that was installed but never used to configure a cluster node. For more information, refer to "Sun Cluster Software and Agents for Sun Cluster".
Dependencies	Sun Cluster core and agents for Sun Cluster must be removed together.
Required to Support	None.
Tasks Before Uninstallation	Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster installation. Do not use the Java Enterprise System uninstaller to remove Sun Cluster software, except in the trivial circumstance to remove software that was installed but never used to configure a cluster node. For more information, refer to "Sun Cluster Software and Agents for Sun Cluster".
Tasks After Uninstallation	You may need to update the productregistry file after uninstalling Sun Cluster software. For more information, refer to "Sun Cluster Software and Agents for Sun Cluster".

Table 10-13 Web Server Details for Uninstallation
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 uninstall.
Dependencies	None.
Required to Support	Identity Server, if configured to run under Web Server Portal Server, if configured to run under Web Server
Tasks Before Uninstallation	None.
Tasks After Uninstallation	To preserve configuration data, make a backup of 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.

Tasks Before Uninstallation

This sections lists the tasks you should perform before running the Java Enterprise System uninstaller.

Use one of the following methods to review the Java Enterprise System components installed on your system prior to uninstalling.

Run the Java Enterprise System uninstaller simply to list the component products on your system (do not uninstall any software). You can exit the uninstaller after viewing the list of Java Enterprise System components.

Use the prodreg utility to view information about all packages installed on your system, including Java Enterprise System components. prodreg opens a graphical window on your system that provides extensive information about all installed packages. This information is useful when checking for product dependencies, as outlined in Step 4 below. prodreg also indicates any packages on your system that are incomplete and may need special handling. prodreg is available with Solaris 9 operating system and some versions of Solaris 8 operating system.

pkginfo and related commands provides information on packages installed on your system. You can compare the listings from pkginfo with the packages listed in Appendix D to determine which Java Enterprise System components are installed on your system.

Back up the product registry.

The product registry is available at the following location:

/var/sadm/install/productregistry

If uninstallation fails, you might want to retry uninstallation with a clean product registry.

Back up or archive any configuration or user data for component products you are uninstalling if you plan to reuse this data in subsequent installations.

Refer to component product documentation for information on backing up configuration and user data.

Review the interdependencies for each product and make sure you understand the relationship of the product you are uninstalling with other component products, as described in "Product Interdependencies".



Caution	It is especially important to review and understand dependencies for component products that reside on separate hosts, for products that a component supports, and for product dependencies that result from configuration. The uninstaller does not issue warnings in these situations.

Prepare the information you must provide the uninstaller to grant administrator access to Administration Server, Directory Server, and Identity Server. For more information refer to the section "Granting Administrator Access to the Uninstaller".

Make sure the Directory Server instance hosting the configuration directory is running before starting the uninstaller.

This Directory Server instance must be running to allow the uninstaller to correctly unconfigure component products you are uninstalling.

Granting Administrator Access to the Uninstaller

Depending on the components you elect to uninstall, you might have to grant the uninstaller administrator access to Administration Server, Directory Server, and Identity Server. This section contains tables that describes the information you provide the uninstaller to grant administrator access. The leftmost column of each table lists the label and state file parameters for the information you must provide. The rightmost column describes the information you must provide.

The label identifies an input field displayed on an uninstaller page in the uninstaller’s graphical mode. The state file parameter is the key that identifies the information in a state file for silent uninstallation.

Administration Server

The following table describes the information necessary to provide administrator access for Administration Server. Administrator access is needed to manage configuration directory data during uninstallation.

Table 10-14 Information for Administration Server
Label and State File Parameter	Description
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

The following table describes the information necessary to provide administrator access for Directory Server. Administrator access is needed to manage the configuration directory during uninstallation.

Table 10-15 Administration Information for Directory Server
Label and State File Parameter	Description
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, but access control restrictions apply.
Administrator Password CONFIG_DIR_ADM_PASSWD	Password for the Administrator.

Identity Server

The following table describes the information necessary to provide administrator access for Identity Server. Administrator access is needed to undeploy the Identity Server web applications from the Sun ONE Application Server and to remove the Identity Server schema.

Table 10-16 Administration Information for Identity Server
Label and State File Parameter	Description
Administrator User ID IS_IAS7_ADMIN	User ID of the Sun ONE Application Server administrator.
Administrator Password IS_IAS7_ADMINPASSWD	Password of the Sun ONE Application Server administrator.
Directory Manager DN IS_DIRMGRDN	Distinguished Name (DN) of the user who has unrestricted access to Directory Server. The default value is cn=Directory Manager.
Directory Manager Password IS_DIRMGRPASSWD	Password of the directory manager.

Running the Uninstaller

When you install Java Enterprise System, the installer creates the Java Enterprise System uninstaller and places it at the following location:

Uninstalling Using the Graphical Interface

This section describes how to uninstall Java Enterprise System software using the uninstaller’s interactive graphical interface.

Starting the Uninstaller

To Start the Uninstaller

Perform the pre-uninstallation tasks, as explained in "Tasks Before Uninstallation".

Careful preparation can prevent accidental loss of data.

Make sure you provide access to your local display.

If you are logging in to a remote machine, or using the su command to become superuser on a local machine, use the xhost command on the local machine to allow access to your local display. For example, use the following command to grant access to all users:

xhost +

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 uninstaller runs in text-based mode. For example, if your machine name is myhost:

(C Shell) % setenv DISPLAY myhost:0.0
(Korn Shell) $ DISPLAY=myhost:0.0

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

Run the uninstaller:

./uninstall [-no]

The optional -no parameter runs the uninstaller but does not uninstall any software. This is useful to familiarize yourself with the uninstaller and for creating state files for a subsequent silent uninstall.

The uninstaller starts, displaying the Welcome screen. Click Next to proceed with selecting components to uninstall.

Selecting Components to Uninstall

The Component Selection page lists all possible Java Enterprise System components on your system.

Component products that are installed on your system are automatically selected for removal. Component products that are not installed on your system are disabled and cannot be selected.

Some component products contain subcomponents. You can expand these components to view the subcomponents.

If all the subcomponents for a component are selected, you can deselect them all by deselecting the parent component.

If you want select a component and all of its subcomponents you must expand the component and select the subcomponents individually. You cannot simply select the parent component.

To Select Component Products for Uninstallation

Make sure you understand product dependencies, as explained in "Product Interdependencies", before proceeding.

Examine the default selections and deselect any component product you do not want to uninstall.

If you deselect a component that contains subcomponents, be sure to expand the component to make sure of your selection.

After making your selections, click Next.

If the uninstaller detects any product dependencies among the products selected for removal, it issues a warning about a potential loss of configuration data.

Click Continue to continue with uninstallation.

Click Close to return to the Component Product Selection page.

Granting Administrator Access

Depending on the component products you selected for removal, the uninstaller prompts you for administrator IDs and passwords so it can do the following:

Manage configuration directories

Manage configuration directory data

Undeploy Identity Server web applications

Remove the Identity Server schema

In each case, provide the required information and click Next to continue with the uninstallation.

Getting Ready to Uninstall

Before removing software from your system, the uninstaller displays a summary page, showing the components selected for removal and the total disk space that will be reclaimed. The following figure provides an example summary page.

At this point you can review your selections and make any needed changes. If you are satisfied with your selections click Next. The uninstaller begins removing software from your system.

To Change Component Selections

Click Back through successive pages until the Component Selection page appears.

Make changes as needed on the Component Selection page.

Click Next and proceed again through the uninstaller pages.

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

At the Ready to Uninstall page click Next.

The uninstaller begins removing software from your system.

Uninstalling Components

A progress bar that displays the overall completion percentage

The name of package currently being removed

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

Click the View Summary or View Log button for information about the uninstallation:

The uninstallation summary lists each component uninstalled and its uninstallation and unconfiguration status.

The uninstallation log lists the uninstaller’s log messages.

You can also review the uninstallation summary and log files at the following location:

Exiting the Uninstaller

Uninstalling Using the Text-Based Interface

This section describes how to uninstall Java Enterprise System software using the uninstaller’s interactive text-based interface. The text-based interface allows you to run the uninstaller directly from a terminal window by responding to prompts displayed in the window.

The following table describes the responses you make to the Java Enterprise System uninstaller prompts.

Table 10-17 Responding to Uninstaller Prompts
Action	Input
Accept default values Default values are indicated in square brackets ([ ])	Press Return
Select an item from a list	Type the number associated with the item. Press Return
Accept list selections For example, you are finished selecting from a list and want to continue.	Type the numeral 0 Press Return
Provide a value to a text field For example, when prompted to supply a user name or port number.	Type the value Press Return
Provide a password	Type the password Press Return The password is not echoed to the terminal window
Return to the previous page in the uininstaller	Type the character < Press Return
Exit the uninstaller	Type the character ! Press Return

Starting the Uninstaller

To Start the Uninstaller


Note	Navigation techniques in text-based mode for the uninstaller differs slightly from the navigation techniques for the installer.

Perform the pre-install tasks, as explained in "Tasks Before Uninstallation".

Careful preparation can prevent accidental loss of data.

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

Run the uninstaller:

./uninstall -nodisplay [-no]

Selecting Components To Uninstall

The uninstaller displays a Welcome message and then lists all possible Java Enterprise System components on your system.

Component products that are installed on your system are automatically selected for removal. Some component products contain subcomponents. If all the subcomponents for a component are selected, you can deselect them all by deselecting the parent component.

If you want to select a component and all of its subcomponents you must select the subcomponents individually. You cannot simply select the parent component.

To Select Component Products for Uninstallation

Make sure you understand product interdependencies, as explained in "Product Interdependencies", before proceeding.

Examine the default selections and deselect any component product you do not want to uninstall.

If you deselect a component that contains subcomponents, be sure to examine the list to make sure of your selection.

After making your selections type the number 0 and press Return.

If the uninstaller detects any product dependencies among the products selected for removal, it issues a warning about a potential loss of configuration data.

Type Yes and press Return to continue with uninstallation.

Type No and press Return to return to the Component Product Selection page.

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

Granting Administrator Access

Depending on the component products you selected for removal, the uninstaller prompts you for administrator IDs and passwords so it can do the following:

Manage configuration directories

Manage configuration directory data

Undeploy Identity Server web applications

Remove the Identity Server schema

In each case, provide the required information and continue with the uninstallation.

Getting Ready to Uninstall

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

If you are satisfied with your selections type the number 1 and press Return. The uninstaller begins removing software from your system.

To Change Component Selections

Type the < character and press Return to go back through successive pages until the Component Selection screen appears.

Make changes as needed on the Component Selection screen.

Proceed again through the uninstaller screens.

At the Ready to Uninstall screen type the number 1 and press Return.

The uninstaller begins removing software from your system.

Uninstalling Components

During uninstallation, the uninstaller displays a progress bar that displays the overall completion percentage.

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

To View the Uninstallation Summary and Logs

Type 1 and press Return to view the uninstallation summary.

The uninstaller lists the component products that were uninstalled and then lists configuration information for the components.

Type 2 and press Return to view the uninstallation log.

The uninstaller lists all messages generated by the uninstaller during uninstallation.

You can also review the uninstallation summary and log files at the following location:

Exiting the Uninstaller

Uninstalling Software in Silent Mode

Silent uninstallation is useful for automated uninstallation of Java Enterprise System components on multiple hosts that share similar configurations. Silent uninstallation requires that you run the uninstaller once to allow the uninstaller to capture provided values in a state file. The state file matches your responses to state file variables, forming name-value pairs. During silent uninstall, the uninstaller uses the name-value pairs in the state file to uninstall and unconfigure Java Enterprise System components.

Typically, you edit the generated state file to provide values specific to each host on which you are uninstalling. You can then run the uninstaller on many hosts, using the host-specific state file as input for each host.

The procedure for uninstalling in silent mode is similar to the procedure for installing in silent mode. For information on using silent mode, refer to Chapter 7, "Installing Software in Silent Mode".

Generating a State File

Before you can run the uninstaller in silent mode, you must first generate a state file, as described in the following procedure. This procedure requires you to run the uninstaller in either graphical or console-based mode. You should be familiar with these procedures, as explained in "Uninstalling Using the Graphical Interface" and "Uninstalling Using the Text-Based Interface".

To Generate a State File

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

If you are planning to use the graphical interface of the uninstaller, provide access to your display.

xhost +

(C Shell) % setenv DISPLAY myhost:0.0
(Korn Shell) $ DISPLAY=myhost:0.0

Run the uninstaller with the following command:

./uninstall [-no] [-nodisplay] -saveState statefile

where:


-no	Prevents the uninstaller from removing software.
-nodisplay	Starts the uninstaller in interactive text-based mode. If you do not specify this option, the uninstaller starts in graphical mode.
-saveState	Instructs the uninstaller to generate a state file at the location specified by statefile. Specify an absolute or relative path to the state file you want to create.
statefile	Specifies an absolute or relative path to the generated state file.

Proceed through the uninstaller to completion.

As you respond to the uninstaller, 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.

Edit a copy of the state file for each host on which you are going to perform a silent uninstall, providing information specific to each host.

For information 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 ID".

Running the Uninstaller in Silent Mode

After generating and editing state files, you are ready to uninstall software using the silent mode of the uninstaller.

To Run the Uninstaller in Silent Mode

Make sure you have properly prepared and edited the state file, as explained in the previous section, "Generating a State File"

Open a terminal window on the host where you want to uninstall Java Enterprise System components.

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

Navigate to the following directory:

cd /var/sadm/prod/entsys/

Start the uninstaller, using the following format:

./uninstall -noconsole -state statefile

where:


-nodisplay	Suppresses the graphical display.
-noconsole	Starts the uninstaller in silent mode, suppressing the user interface.
-state	Uses the specified statefile as input to a silent uninstallation.
statefile	Specifies an absolute or relative pathname to a statefile.

While the uninstaller is running, you can monitor its progress by examining the uninstallation log.

To Monitor the Progress of a Silent Uninstallation

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

cd /var/sadm/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. It has the 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 log-file-name

Tasks to Perform After Uninstallation

This section lists tasks that you might have to perform after uninstalling Java Enterprise System component products from your system. The actual tasks you perform depend on the components you elected to uninstall.

Messaging Server Tasks

In some cases, uninstall 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. The default configuration directory for Messaging Server is at the following location:

sendmail Configuration

After uninstallation of Messaging Server, undo any sendmail configuration for Messaging Server.

Portal Server, Restarting Identity Server

If you are running Portal Server on Web Server and you uninstall Portal Server only, you must restart the Identity Server. Follow the procedures below before accessing Identity Server after Portal Server software has been uninstalled.

The following procedure shows how to restart Identity Server for a single instance installation.

To Restart Identity Server for a Single Instance Installation

Stop Identity Server using the following command:

/etc/init.d/amserver stop

Start Identity Server using the following command:

/etc/init.d/amserver start

The following procedure shows how to restart Identity Server for multiple instance installation. Follow this procedure for each created instance on which Portal Server was deployed (excluding the original instance for which the ClassCache is removed by the pssetup script).

To Restart Identity Server for a Multiple Instance Installation

Navigate to the ClassCache directory and remove the instances, as follows:

cd ${BASEDIR}/SUNWam/servers/https-Instance_Name/ClassCache
rm -rf https-Instance_Name/* https-Deploy_Instance/*

Repeat Step 1 for each created server instance.

After the ClassCache for all additional instances is removed, stop all instances using:

/etc/init.d/amserver stopall

Restart all the instances using:

/etc/init.d/amserver startall

Sun Cluster Software and Agents for Sun Cluster

Sun Cluster software should only be uninstalled using the utilities provided with your Sun Cluster software installation. Sun Cluster core and agents for Sun Cluster must be removed together.

Do not use the Java Enterprise System uninstaller to remove Sun Cluster software, except in the trivial circumstance to remove software that was installed but never used to configure a cluster node.


Note	If you attempt to use the Java Enterprise System uninstaller to remove Sun Cluster software from a machine after a cluster has been configured, the uninstaller does not perform the uninstallation. Instead it informs you that it cannot uninstall Sun Cluster software and asks you to deselect Sun Cluster software from your list of components to uninstall.

For more information on unconfiguring and uninstalling Sun Cluster software, refer to your Sun Cluster software documentation at http://docs.sun.com/coll/572.12.

After uninstalling Sun Cluster software, you should remove references to Sun Cluster software from the Java Enterprise System productregistry file, which is located at:


Caution	Before editing the productregistry file, it is a good idea to first back up the file. This file contains information essential to the proper operation of your Java Enterprise System.

Troubleshooting Uninstallation

This section provides suggestions on how to resolve problems encountered when uninstalling Java Enterprise System software. The information in this section supplements the general troubleshooting information available in Chapter 9, "Troubleshooting Installation Problems".

"Verify Uninstallation Procedures and Dependencies"

"Examine Log Files"

"Verify Passwords"

"Uninstallation Cleanup"

"Product Registry"

"Uninstaller Cannot Connect to Configuration Directory Server"

"Cannot Find the Uninstaller"

Verify Uninstallation Procedures and Dependencies

Before running the Java Enterprise System uninstaller, you should carefully prepare for the uninstallation as described in earlier sections of this chapter. If you are troubleshooting a failed uninstallation, review the following sections to make sure you have not overlooked a step prior to running the uninstaller:

"About the Uninstaller"

"Product Interdependencies"

"Component Product Details"

"Tasks Before Uninstallation"

Examine Log Files

If you are troubleshooting a failed uninstallation, you can check the uninstaller log files and other related log files. The uninstallation log files are available at the following location:

Examining the uninstaller and installer log files, along with the Java Enterprise System configuration log and component product logs, can help locate the source of a failed uninstallation.

For example, you can compare the packages listed in the installation log to the packages listed in the uninstallation log.

Verify Passwords

During uninstallation, you must grant administrator access to the uninstaller, as described in "Granting Administrator Access to the Uninstaller". Make sure you provide the correct user IDs and passwords during uninstallation.

Cannot Find the Uninstaller

The Java Enterprise System installation program places the Java Enterprise System uninstaller on your system at the following location:

If the uninstaller is not at this location, this could be the result of the following situations:

Java Enterprise System was never installed on this host.

The Java Enterprise System uninstaller previously removed all component products from this host, including the uninstaller.

During a failed installation, the uninstaller was never installed on the host.

In this case, you need to manually clean up your system, as described in"Uninstallation Cleanup".

During a failed uninstallation, the uninstaller was removed, but some Java Enterprise System components remain on the host.

In this case, you need to manually clean up your system, as described in"Uninstallation Cleanup".

Uninstallation Cleanup

If uninstallation fails you can check the packages installed using the pkginfo command or the prodreg tool. Compare the results with the Java Enterprise System packages listed in Appendix D, "List of Installable Packages".


Note	Step 1 of the tasks listed in "Tasks Before Uninstallation" provides additional information on how to verify packages installed on system.

You can then use the pkgrm command to manually remove packages. You might also have to remove directories and files, depending on which Java Enterprise System component product you are uninstalling. Refer to your component product documentation for more information.

If you determine that manual cleanup is necessary, use the following procedure to remove Java Enterprise System packages from your system.

To Manually Clean Up Packages

Determine which packages you want to remove.

Compare the packages on your system with the Java Enterprise System packages listed in Appendix D, "List of Installable Packages". You can use either the pkginfo or prodreg utilities to determine which packages are installed on your system.

Stop all running processes for Java Enterprise System component products.

Refer to the component product documentation for information on determining which processes to stop for each component. "Component Product Facts for Troubleshooting" provides some information on each component product, with links to component product documentation.

Back up all custom configuration and user data you plan to use in a subsequent installation.

"Component Product Details" provides some information on configuration and user data that should be backed up. For more information, refer to the component product documentation for each component.

Use the pkgrm command to remove Java Enterprise System component packages.

Remove any remaining component product directories and their content that you do not plan to use in subsequent installations.

Update the product registry file, which is located at:

/var/sadm/install/productregistry

The Java Enterprise System installer and uninstaller programs use this registry to determine which components are installed on a host. Both the installer and uninstaller update the product registry upon completion of an installation or uninstallation.

If you manually remove packages, then you must manually update the product registry so it correctly reflects the software installed on your system.

Clean up the log files for your system, which are located at:

/var/sadm/logs

The log files may not correctly reflect the state of your system after manual removal of packages.

Product Registry

During uninstallation, the Java Enterprise System uninstaller looks at the product registry to determine what needs to be uninstalled. If the uninstaller fails, you might need to retry later with a clean product registry.

Manual Removal of Packages

When you manually remove packages, the product registry is not updated. When you subsequently run the uninstaller, you might encounter problems because the product registry does not correctly reflect your system. In this case, you can try to reinstall using the Java Enterprise System installer and then run the Java Enterprise System uninstaller again.

Uninstaller Cannot Connect to Configuration Directory Server

When uninstalling either the Administration Server or Directory Server, the uninstaller attempts to connect to the configuration directory server using the administrator user ID and password supplied earlier when running the uninstaller.

If the uninstaller cannot connect to the configuration directory server, or if the administrator user ID and password are not valid, the uninstaller indicates it cannot proceed with the uninstallation by displaying the following Error Notification:

If you encounter this Error Notification, use the following procedure to troubleshoot the problem and complete the uninstallation. You do not have to exit the Java Enterprise System uninstaller to complete this procedure.

To Troubleshoot and Complete Administration Server or Directory Server Uninstallation


Note	The following procedure assumes you have configured a Directory Server instance at the following location: /var/opt/mps/serverroot/slapd-Dir_Svr_Instance_Name If you specified a different location, modify the instructions in the procedure accordingly.

Make sure the Directory Server instance hosting the configuration directory is running. For example, search for the slapd process as follows:

/usr/bin/ps -ef | grep slapd

If the configuration directory server is not running, do the following:

Log in as root on the configuration directory host and start the configuration directory server with the following commands:

cd /var/opt/mps/serverroot/slapd-Dir_Svr_Instance_Name
./start-slapd

Once you have verified that the configuration directory server is running, make sure you have a valid administrator user ID and password.

If the configuration directory server is running and you have a valid administrator user ID and password, you can proceed with the uninstallation.

If you do not have a valid administrator user ID and password, the Java Enterprise System uninstaller stalls with the Error Notification described previously.

If you do not have a valid administrator user ID and password, and you want to continue with the uninstallation, do the following to manually unconfigure the Directory Server and/or Administration Server:

Stop the Directory Server instance that is hosting the configuration directory. For example, with root privileges do the following:

cd /var/opt/mps/serverroot/slapd-Dir_Svr_Instance_Name

./stop-slapd

Run the following unconfiguration programs for Administration Server and Directory Server respectively:

/usr/sbin/mpsadmserver unconfigure

/usr/sbin/directoryserver unconfigure

During unconfiguration, a notice appears informing you that the configuration directory server cannot be contacted.

Click Continue to continue with unconfiguration.

After running the unconfiguration programs, in the Java Enterprise System uninstaller continue with the uninstallation process.

When prompted for the administrator user ID and password, supply any arbitrary value. These values will be ignored during uninstallation.