Configuration Data 

No entries in Directory Server will be removed (including Access Manager specific data). 

Dependencies 

Directory Server 

Web container 

Products Requiring this Installation 

• Portal Server (must reside on the same host as Access Manager SDK)

• Calendar Server, when configured for single sign-on (SSO)

• Instant Messaging, when configured for Portal Server, SSO

• Messaging Server, when configured for SSO

• Communications Express, when configured for SSO and when Schema 2 is used

Pre-Uninstallation Tasks 

Remove the schema using /etc/opt/SUNWam/config/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. It also does not unconfigure SDK installations on any web container (such as, Web Server, Application Server, BEA WebLogic, IBM WebSphere). 

Additionally, remove the following files located in the directory /var/sadm/install if they exist:

.lockfile.pkg.lock

Configuration Data 

• Proxy information for managing other servers is lost upon uninstallation.

• Configuration data used by Administration Server to manage other servers remains within the Configuration Directory Server. This information can be reused upon a subsequent installation of Administration Server.

Dependencies 

Directory Server 

Products Requiring this Installation 

Directory Proxy Server and Messaging Server require Administration Server. Directory Server can be configured to require Administration Server. 

Note: If you remove Administration Server and not Directory Server, then Directory Server must be managed using other utilities that come with Directory Server. Refer to Directory Server documentation at http://docs.sun.com/coll/DirectoryServer_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 

Configuration Data and User Data 

• The default domain created during installation is removed during uninstallation.

• Configured administrative domains, including all administrative server and Application Server instances, are not removed during uninstallation.

• All Administration Server and Application Server instances are stopped prior to the completion of uninstallation.

Dependencies 

Requires Message Queue on the same system. 

Products Requiring this Installation 

• Access Manager (if configured for Application Server)

• Portal Server (if configured for Application Server)

• Communications Express (if configured for Application Server)

Pre-Uninstallation Tasks 

To preserve configuration data, make a copy of the administration domain directories. 

Post-Uninstallation 

To completely remove Application Server from your system, remove any remaining Application Server log files and directories. Default locations for Application Server directories are: 

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

Configuration Data and User Data 

Configuration data and user data are not removed during uninstallation, and will be overwritten upon subsequent installation. 

Customizations to Calendar Server are removed during uninstallation. 

Dependencies 

• Directory Server

• Access Manager, when configured for single sign-on (SSO) or if you want to use Schema 2

• Messaging Server (or some other mail server, for Calendar Server email notification service)

Products Requiring this Installation 

• Portal Server (when configured to use Calendar Server for the Portal Server’s calendar channel)

• Communications Express

Pre-Uninstallation Tasks 

If you plan to reuse configuration data and user data, follow the migration process as described in the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Post-Uninstallation Tasks 

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

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 

• Application Server (if configured to run under Application Server)

• Web Server (if configured to run under Web Server)

• Access Manager (when configured for SSO)

• Directory Server

• Calendar Server

• Messaging Server

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

Unconfigure Communications Express. Refer to the “Unconfiguring Communications Express” section in the Sun Java System Communications Express 6 2005Q4 Administration Guide.

Post-Uninstallation Tasks 

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

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 

• Directory Server

• Access Manager

• One of these web containers: Web Server or Application Server

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. 

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 

• Administration Server

• Calendar Server

• Directory Proxy Server

• Access Manager

• Instant Messaging

• Messaging Server

• Portal Server

• Communications Express

Pre-Uninstallation Tasks 

• Back up the configuration directory for Directory Server and the Directory Server LDAP database as needed.

• Make sure the Directory Server instance hosting the configuration directory is running, and that you can provide the administrator user ID and password.

Post-Uninstallation Tasks 

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

Configuration Data 

• Configuration data for the instance of Directory Proxy Server you are uninstalling is removed during uninstallation.

• Shared configuration data between several instances of Directory Proxy Server remains after uninstallation.

• Directory Proxy Server has no user data.

Dependencies 

Directory Proxy Server has a logical dependency upon the local or remote Directory Server that acts as Configuration Directory Server. Directory Proxy Server depends upon a local Administration Server. 

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

None 

Configuration Data and User Data 

All configuration data remains after uninstallation, and can be reused upon a subsequent installation. 

Dependencies 

• Directory Server

• Access Manager SDK

Products Requiring this Installation 

Portal Server, when configured to use Instant Messaging channel 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

None 

Configuration Data and User Data 

All configuration data and customizations remain after uninstallation, and can be reused upon subsequent installation. 

Dependencies 

• Directory Server

• Administration Server (must reside on same host)

• Web Server (for mailing functionality such as filters)

• Access Manager (if using Schema 2)

Products Requiring this Installation 

• Calendar Server

• Portal Server, when configured with messaging channels

• Communications Express, when messaging is used

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

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

Configuration Data 

Instance-specific configuration data, user repository and access control file remains after uninstallation, and can be reused upon subsequent reinstallation. 

Dependencies 

Directory Server (optional) 

Products Requiring this Installation 

Application Server (must reside on same host as Message Queue) 

Pre-Uninstallation Tasks 

• Stop any running brokers. You will be prompted for user name (admin) and password:imqcmd shutdown bkr [-b hostName:port]

• If you are not planning to reinstall Message Queue and therefore want to delete dynamic data, the flat-file user repository, and the access control file associated with each broker instance, remove this data using the following command. imqbrokerd -name instanceName -remove instance

• If you upgrade Message Queue using the Message Queue upgrade script, make a note of your process. The upgrade script does not write install information to the Java ES registry. More information may be found in the Sun Java Enterprise System 2005Q4 Upgrade Guide.

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

Configuration Data and User Data 

• Configuration data is removed during uninstallation. Unconfiguring includes removing services created in Access Manager by Portal Server.

• Providers for user channels are not removed during installation and can be reused upon subsequent installation.

• Customized configuration data (display profiles, property files, resources strings, and other customizations) is not removed by the uninstaller. It can be reused upon subsequent installation only if Portal Server is reinstalled to the same host with the same configuration.

Dependencies 

• Directory Server

• Application Server or Web Server (Can also be configured to be dependent on IBM WebSphere or BEA WebLogic.)

• Access Manager

If configured to use Portal Server channels: 

• Calendar Server

• Messaging Server

• Instant Messaging

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

• If you are running Portal Server within Web Server and you choose to remove Portal Server only, you must restart Access Manager. For more information, refer to Access Manager Post-uninstallation Issues

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

Configuration Data 

• All configuration data for the Portal Server Secure Remote Access Core component is removed during uninstallation.

• All web applications that have been deployed are undeployed.

• Users do not have configuration data access to Portal Server Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy components.

Dependencies 

• Portal Server Secure Remote Access depends on Portal Server.

• Portal Server, Secure Remote Access Gateway, Netlet Proxy, and Rewriter Proxy components depend on Access Manager SDK.

• Portal Server and Portal Server Secure Remote Access Support must reside on the same host and in the same directory.

• Access Manager SDK must reside on the same host as Gateway, Netlet Proxy, and Rewriter Proxy. Gateway, Netlet Proxy, and Rewriter Proxy cannot be in the same directory.

• You can remove any Portal Server Secure Remote Access component without removing any dependent component.

• You can remove Gateway and leave Access Manager SDK on the host.

Products Requiring this Installation 

None 

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

None 

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.

Configuration Data and User Data 

• User data is not removed during uninstallation but configuration data is removed.

• The Web Server administrative server instance and configured Web Server instance directories are removed. The initially-configured document root directory is preserved.

• Web Server administrative server and Web Server instances are stopped prior to the completion of the uninstallation.

Dependencies 

None 

Products Requiring this Installation 

• Access Manager, if configured to run under Web Server

• Portal Server, if configured to run under Web Server

• Communications Express

• Application Server Load Balancing Plugin (if Application Server uses Web Server as its web container)

Pre-Uninstallation Tasks 

None 

Post-Uninstallation Tasks 

To preserve configuration data, backup the Administrative Server and Web Server instance directories under the installation location. 

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.