Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2004Q2 Installation Guide 

Appendix G
Component Product Uninstallation Details

This appendix lists and gives pertinent details about the component products you may uninstall. Review the appropriate tables in this appendix to see what the uninstaller does with that component and what steps you might have to take to prevent loss of data or loss of interdependency connections.

This appendix contains the following sections:


Administration Server

Before uninstalling Administration Server, review the information found in Table G-1.

Table G-1  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 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 available with Directory Server. Refer to Directory Server documentation at http://docs.sun.com/coll/DirectoryServer_04q2 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. For more information, refer to Uninstaller Cannot Connect to Configuration Directory Server.

Post-Uninstallation

None


Application Server

Before uninstalling Application Server, review the information found in Table G-2.

Table G-2  Application Server Uninstallation Details

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.

Products Requiring this Installation

  • Identity Server (if configured for Application Server)
  • Portal Server (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:

/etc/opt/SUNWappserver7
/var/opt/SUNWappserver7
/opt/SUNWappserver7

Refer to Table G-10 for information on Message Queue post-uninstallation tasks.


Calendar Server

Before uninstalling Calendar Server, review the information found in Table G-3.

Table G-3  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
  • Identity Server, 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)

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 2004Q2 Administration Guide (http://docs.sun.com/doc/817-5697.).

Post-Uninstallation Tasks

Remove any remaining log files and Calendar Server directories that are not needed.


Communications Express

Before uninstalling Communications Express, review the information found in Table G-4.

Table G-4  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 /opt/SUNWuwc)
  • Application Deployment (by default /var/opt/SUNWuwc) created during the configuration time.

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 remain after re-configuration.

Dependencies

None

Products Requiring this Installation

None

Pre-Uninstallation Tasks

Unconfigure Communications Express.

To unconfigure Communications Express, refer to the “Unconfiguring Communications Express” section in the Sun Java System Communications Express 6 2004Q2 Administration Guide, http://docs.sun.com/doc/817-5416.

Post-Uninstallation Tasks

Remove any remaining log files and Communications Express directories that are not needed.


Directory Server

Before uninstalling Directory Server, review the information found in Table G-5.

Table G-5  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_04q2 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
  • Identity Server
  • Instant Messaging
  • Messaging Server
  • Portal Server

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. For more information, refer to Uninstaller Cannot Connect to Configuration Directory Server.

Post-Uninstallation Tasks

Uninstallation of Directory Server might require manual removal of remaining files and directories.


Directory Proxy Server

Before uninstalling Directory Proxy Server, review the information found in Table G-6.

Table G-6  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 has a physical dependency upon Administration Server.

Products Requiring this Installation

None

Pre-Uninstallation Tasks

None

Post-Uninstallation Tasks

None


Identity Server

Before uninstalling Identity Server, review the information found in Table G-7.

Table G-7  Identity Server Uninstallation Details  

Topic

Details

Configuration Data

Configuration data for Identity Server is removed during uninstallation.

Dependencies

Directory Server
Web Server or Application Server

Products Requiring this Installation

  • Portal Server (must reside on the same host as Identity Server)
  • Calendar Server, when configured for single sign-on (SSO)
  • Instant Messaging, when configured for SSO
  • Messaging Server, when configured for SSO

Pre-Uninstallation Tasks

None

Post-Uninstallation Tasks

After uninstallation 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


Instant Messaging

Before uninstalling Instant Messaging, review the information found in Table G-8.

Table G-8  Instant Messaging Uninstallation Details

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

Products Requiring this Installation

Portal Server, when configured to use Instant Messaging channel

Pre-Uninstallation Tasks

None

Post-Uninstallation Tasks

None


Messaging Server

Before uninstalling Messaging Server, review the information found in Table G-9.

Table G-9  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)
  • Identity Server (if using Schema 2)

Products Requiring this Installation

  • Calendar Server
  • Portal Server, when configured with messaging channels

Pre-Uninstallation Tasks

None

Post-Uninstallation Tasks

Depending on your circumstances, you might have to perform post-uninstallation tasks as explained in Messaging Server Tasks.


Message Queue

Before uninstalling Message Queue, review the information found in Table G-10.

Table G-10  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 user) and password:

imqcmd shutdown bkr [-b hostName:port]

If you are not planning to reinstall Message Queue and so 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

Post-Uninstallation Tasks

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 here: http://docs.sun.com/coll/MessageQueue_35_SP1


Portal Server

Before uninstalling Portal Server, review the information found in Table G-11.

Table G-11  Portal Server Uninstallation Details 

Topic

Details

Configuration Data and User Data

Configuration Data is removed during uninstallation. Unconfiguring 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/PortalServer_04q2.

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/PortalServer_04q2.

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

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 Identity Server. For more information, refer to Identity Server Tasks.

If Portal Server is deployed to the IBM WebSphere web container, there may be additional uninstallation tasks.


Portal Server, Secure Remote Access

Before uninstalling Portal Server, Secure Remote Access, review the information found in Table G-12.

Table G-12  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 Identity Server SDK.

Portal Server and Portal Server, Secure Remote Access 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, Secure Remote Access Component without removing any dependent component.

You can remove Gateway and leave Identity Server SDK on the host.

Products Requiring this Installation

None

Pre-Uninstallation Tasks

None

Post-Uninstallation Tasks

None


Sun Cluster

Before uninstalling Sun Cluster Software, review the information found in Table G-13.

Table G-13  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 Sun Cluster Software and Sun Cluster Agents for Sun Java System.

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 may need to update the productregistry file after uninstalling Sun Cluster software. For more information, refer to Sun Cluster Software and Sun Cluster Agents for Sun Java System.


Web Server

Before uninstalling Web Server, review the information found in Table G-14.

Table G-14  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

  • Identity Server, if configured to run under Web Server
  • Portal Server, if configured to run under Web Server

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.



Previous      Contents      Index      Next     


Copyright 2004 Sun Microsystems, Inc. All rights reserved.