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:
Perform one of the following procedures to review the Java ES product component software that is already installed on each host.
As root, navigate to the directory where the uninstaller is located:
Solaris OS: /var/sadm/prod/SUNWentsys5u1
Linux: /var/sadm/prod/sun-entsys5u1
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.
Proceed through the uninstaller pages until you reach the list of installed products.
After viewing the list of installed product components, exit the uninstaller.
No software has been uninstalled.
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.
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:
Topic |
Details |
---|---|
Configuration Data |
No entries in Directory Server will be removed (including Access Manager specific data). |
Other Installations This Component Requires |
Directory Server Web container |
Products Requiring This Installation |
Portal Server must reside on the same host as Access Manager SDK. |
Pre-Uninstallation Tasks |
Remove the schema using this file: Solaris OS: /etc/opt/SUNWam/config/ldif/ds_remote_schema_uninstall.ldif Linux: /etc/opt/sun/identity/config/ldif/ds_remote_schema_uninstall.ldif |
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. Uninstallation also does not unconfigure SDK on any web container. Additionally, remove the following files located in the directory /var/sadm/install if they exist: .lockfile.pkg.lock. For information on additional post-uninstallation issues, refer to Access Manager Post-uninstallation Issues. |
Topic |
Details |
---|---|
Configuration Data and User Data (Solaris OS and Linux only) |
|
Other Installations This Component Requires |
Requires Message Queue on the same system. |
Products Requiring This Installation |
Components that are configured to use Application Server as web container. |
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 OS: /var/opt/SUNWappserver /opt/SUNWappserver/appserver or ApplicationServer-base Linux : /var/opt/sun/appserver /opt/sun/appserver Refer to Message Queue Uninstallation Behavior for information on Message Queue post-uninstallation tasks. |
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. |
Other Installations This Component Requires |
Directory Proxy Server has a logical dependency upon the local or remote Directory Server. |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
None |
Topic |
Details |
---|---|
Configuration Data and User Data |
If you are uninstalling the Directory Server instance hosting user data, the Directory Server LDAP database is removed during uninstallation. Caution: To avoid loss of data, make sure to back up Directory Server information before uninstalling. Directory Server has several tools and utilities to backup Directory Server and migrate configuration data. Refer to Directory Server documentation at http://docs.sun.com/coll/1224.1 for more information. |
Other Installations This Component Requires |
None |
Products Requiring This Installation |
|
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
If you subsequently install Directory Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location. |
Topic |
Details |
---|---|
Configuration Data and User Data |
Configuration and user data are not removed during uninstallation. By default, this data resides in the following locations:
|
Other Installations This Component Requires |
None |
Products Requiring This Installation |
Application Server when configured to use HADB for high availability session persistence. |
Pre-Uninstallation Tasks |
If you plan to upgrade HADB and reuse configuration data, refer to the chapter on High Availability Session Store in the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX |
Post-Uninstallation Tasks |
Remove configuration and user data that is no longer needed. |
Topic |
Details |
---|---|
Configuration Data |
Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. |
Other Installations This Component Requires |
Directory Server (optional) |
Products Requiring This Installation |
Application Server (must reside on same host as Message Queue). |
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
If you are not planning to reinstall Message Queue, use the commands in the product component documentation to clean up your system. |
Topic |
Details |
---|---|
Configuration Data |
User data remains after uninstallation, however, this data is removed before any reinstallation. |
Other Installations This Component Requires |
None |
Other Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
To preserve data, copy the following to a persistent location, then copy back after reinstallation: For Solaris OS: /etc/opt/SUNWmfwk/config/mfwk.properties /etc/opt/SUNWmfwk/config/masteragent.properties /etc/opt/SUNWmfwk/config/nodelist /var/opt/SUNWmfwk/persistence/ /var/opt/SUNWmfwk/alarms/ For Linux : /etc/opt/sun/mfwk/config/mfwk.properties /etc/opt/sun/mfwk/config/masteragent.properties /etc/opt/sun/mfwk/config/nodelist /var/opt/sun/mfwk/persistence/ /var/opt/sun/mfwk/alarms/ |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Other Installations This Component Requires |
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
Verify that Directory Server and the web container are running. If the web container is Web Server, Web Server admin server must be running. |
Post-Uninstallation Tasks |
|
Topic |
Details |
---|---|
Configuration Data |
The Registry configuration process installs the Registry database domain and server keystore in the following directory:
The directory is not removed when Service Registry is uninstalled. This allows you to preserve the database for use in a future installation or release if you want. |
Other Installations This Component Requires |
Application Server (Domain Administration Server and Command-Line Administration Tool) HADB Message Queue |
Products Requiring This Installation |
None |
Pre-Uninstallation Tasks |
1. Navigate to the ServiceRegistry–base/install directory. 2. Stop the Service Registry domain as follows: .../ant -f build-install.xml appserver.domain.stop 3. Delete the Service Registry domain as follows: .../ant —f build-install.xml appserver.domain.delete If you want to preserve the Registry database for future use, copy the /var/opt/SUNWsrvc-registry/3.0 directory (on Solaris OS) or /var/opt/sun/srvc-registry/3.0 (on Linux) directory to another location before you reinstall the Registry. |
Post-Uninstallation Tasks |
For information on some optional tasks, refer to Service Registry Post-uninstallation Tasks |
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. |
Other Installations This Component Requires |
Sun Cluster Geographic Edition software must be removed on every host that contains Sun Cluster Geographic Edition components. For more information, refer to Chapter 5, Uninstalling the Sun Cluster Geographic Edition Software, in Sun Cluster Geographic Edition Installation Guide 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. Note: Sun Cluster Geographic Edition software must be removed before Sun Cluster software is removed. |
Post-Uninstallation Tasks |
You might need to update the product registry after uninstalling Sun Cluster software. For more information, refer to Uninstalling Sun Cluster Software. |
Topic |
Details |
---|---|
Configuration Data |
Only the certificate database files in the alias directory under the installation location are preserved. All other files are removed. |
Dependencies |
Directory Server (optional) if external LDAP access control has been selected. |
Pre-Uninstallation Tasks |
Stop all instances of Web Proxy Server. |
Post-Uninstallation Tasks |
The certificate database is preserved under the WebProxyServer-base/alias directory. Before reinstalling, move the certificate database and delete the old installation directory. |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Other Installations This Component Requires |
None |
Products Requiring this Installation |
Components that can be configured to use Web Server as web container, such as Access Manager and Portal Server. Also Application Server Load Balancing Plugin (if Application Server uses Web Server as its web container). |
Pre-Uninstallation Tasks |
Make sure you can provide the administrator password for the web container. |
Post-Uninstallation Tasks |
To preserve configuration data, back up the Administrative Server and Web Server instance directories under the installation location. If you reinstall Web Server to the same location, the installation directory must not exist. You might need to manually remove the installation directory and any custom configuration files before reinstalling to the same location. For information on additional post-uninstallation issues, refer to Web Server Post-uninstallation Tasks (Web Server Not Uninstalled). |
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.
Table 8–15 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. |
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. |
Portal Server | |
Administrator Password PS_DEPLOY_ADMIN_PASSWORD |
Password that Portal Server uses to access the web container as administrator. |
Access Manager Administrator Password PS_IS_ADMIN_PASSWORD | |
Directory Server Administrator Password PS_DS_DIRMGR_PASSWORD | |
Directory Server Administrator Domain PS_DS_DIRMGR_DN | |
Web Server |
|
Administrator User ID IS_WS_ADMIN_ID | |
Administrator Password IS_WS_ADMIN_PASSWORD |