4.1 Upgrading Shared Components

Perform the following procedure to identify any shared components in the operating system that need to be upgraded before installing Java ES. Perform this procedure on all front-end (FE) and back-end (BE) servers.

To Identify Upgrade Needs of Shared Components

Steps

1. Launch the Java ES installer in command-line report-only mode:

   # cd /var/bits/ # ./installer -nodisplay -no

2. Proceed to the language selection page and select a language, by default en_US. After a language is selected, the installer begins inspection for previously installed components.

3. If components are detected, a report will be shown. Review the report. If there are outdated versions, exit the installer now by typing “!” and upgrade those shared components.

4. When all shared components are up-to-date, continue to the Component Selection menu and select the following components:

   • On FE systems designated as MTA

     • Sun Java System Messaging Server

   • On FE systems designated as MMP, MEM, or CE

     • Sun Java System Messaging Server

     • Sun Java System Communications Express

     • Sun Java System Calendar Server

     • Sun Java System Instant Messaging (Multiplexor and Client Resources)

     • Sun Java System Web Server

   • On FE systems designated as Portal Gateway

     • Sun Java System Portal Server

   • On BE systems designated as Messaging Store

     • Sun Java System Messaging Server

     • Sun Cluster

     • Sun Java System Directory Server

     • Sun Java System Access Manager

   • On BE systems designated as Calendar Store

     • Sun Java System Calendar Server

     • Sun Java System Instant Messaging (on one Calendar Server BE instance only)

     • Sun Java System Web Server (on the same BE instance as Instant Messaging only)

     • Sun Cluster

   The installer now checks for shared component dependencies. If there is a broken dependency, it will display an explanation.

5. Exit the installer. If there are shared components to be installed/removed, do that before continuing.

6. Make a copy of the /var/sadm/install/productregistry file on each server.

7. Verify that the file /etc/resolv.conf exists and that the information it contains is correct.

8. Verify that the 2nd column in the /etc/hosts file contains only fully-qualified domain names (FQDN) in all lower case (avoids known issue 6330974).