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.
This section contains the following subsections:
Perform one of the following procedures to review the Java ES 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/SUNWentsys4
Linux: /var/sadm/prod/sun-entsys4
To survey the local system, 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 components, exit the uninstaller.
No software has been uninstalled.
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. On the Solaris 10, and Solaris 9 operating systems and some versions of the Solaris 8 operating system, 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 Java ES components. Plan the steps you might have to take to prevent loss of data or loss of interdependency connections.
This section contains the following subsections:
Topic |
Details |
---|---|
Configuration Data |
|
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_05Q4 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 |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Dependencies |
Requires Message Queue on the same system. |
Products Requiring this Installation |
|
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 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 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 |
|
Products Requiring this Installation |
|
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 6 2005Q4 Administration Guide. |
Post-Uninstallation Tasks |
Remove any remaining log files and Calendar Server directories that are not needed. |
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 OS: /opt/SUNWuwc Linux: /opt/sun/uwc Application Deployment created by default during configuration: Solaris OS: /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 |
|
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 6 2005Q4 Administration Guide. |
Post-Uninstallation Tasks |
Remove any remaining log files and Communications Express directories that are not needed. |
Topic |
Details |
---|---|
Configuration Data |
Configuration data and user data are not removed during uninstallation. This data will be overwritten upon a subsequent installation. Customizations to Delegated Administrator are removed during uninstallation. |
Dependencies |
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
If you plan to reuse configuration data and user data, read Preserve an Existing Configuration in Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide. |
Post-Uninstallation Tasks |
Remove any remaining log files and Delegated Administrator directories that are not needed. |
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_05Q4 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 |
|
Pre-Uninstallation Tasks |
|
Post-Uninstallation Tasks |
Uninstallation of Directory Server might require manual removal of remaining files and directories. |
Topic |
Details |
---|---|
Configuration Data and User Data |
All configuration data and customizations remain after uninstallation, and can be reused upon subsequent installation. |
Dependencies |
|
Products Requiring this Installation |
|
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 |
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 |
|
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 |
Topic |
Details |
---|---|
Configuration Data and User Data |
|
Dependencies |
If configured to use Portal Server channels:
|
Products Requiring this Installation |
None |
Pre-Uninstallation Tasks |
None |
Post-Uninstallation Tasks |
|
The Registry configuration process installs the Registry database and server keystore in the following directory:
Solaris OS: /var/opt/SUNWsoar
Linux: /var/opt/sun/SUNWsoar
The directory is not removed when the Service Registry is uninstalled. This allows you to preserve the database for use in a future installation or release if you want To do so, copy the /var/opt/SUNWsoar/3.0 directory (on Solaris OS) or /var/opt/sun/SUNWsoar/3.0 (on Linux) to another location before you reinstall the Registry, then copy it back after you reinstall.
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. |
Topic |
Details |
---|---|
Configuration Data |
Only the certificate database files in the alias directory under the installation location are preserved. All other files are removed. |
Dependencies |
Directory Server (optional) if external LDAP access control has been selected. |
Pre-Uninstallation Tasks |
Stop all instances of Web Proxy Server. |
Post-Uninstallation Tasks |
The certificate database is preserved under the WebProxyServer-base/alias directory. You need to move the certificate database and delete the old installation directory before reinstalling. |
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.
Access Manager administrator access is required to undeploy the Access Manager web applications from the Application Server and to remove the Access Manager schema.
Administration Server and 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 describes the information.
Table 8–18 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. |
Portal Server | |
Administrator Password PS_DEPLOY_ADMIN_PASSWORD | |
Access Manager Administrator Password PS_IS_ADMIN_PASSWORD | |
Directory Server Administrator Password PS_DS_DIRMGR_PASSWORD | |
Directory Server Administrator Domain PS_DS_DIRMGR_DN |