To Use the Installer for Identifying Upgrade Issues

1. Start the installer using the -no option to indicate that no software is to be installed.

   For the graphical installer:

   ./installer -no

   For the text-based installer:

   ./installer -nodisplay -no

2. Proceed to component selection.

3. Select the product components you are planning to install on this host.

   The Status column indicates products that are required for the product components you have selected and what components are upgradable.

4. If an incompatible version of a selectable product component is detected by the installer, you are prompted to upgrade or remove the incompatible version.

   In the case of Solaris bundled Application Server, Message Queue, and HADB, you can have the installer do the upgrading. For further information, refer to How Upgrading Works.

   After resolving the problem, you can refresh the selection list, make your selection, and then ask the installer to proceed.

5. If an incompatible version of a shared component is detected by the installer, the Shared Component Upgrades Required list is displayed.

   For each shared component listed, review the Installed Version against the Required Version to determine if any upgrading will need to be done. You must determine whether the newer Java ES version of a shared component is compatible with other applications on the host that use that shared component.

6. If necessary, exit the installer and do any upgrading necessary.

   • For product components that the installer cannot upgrade, refer to the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

   • For shared components, most upgrading can be done during installation.

7. Repeat the procedure for each host.

   ---

   Note –

   The installer detects the Directory Server version that is distributed with the Solaris OS and warns you that the Directory Server script belonging to the Solaris distribution will be renamed by the installer. No action is required.

   ---