test

Sun Java Communications Suite 5 Installation Guide

Surveying Existing Hosts

Before installation, it is important to know what resides on the hosts where you plan to install the software. If your existing hosts have versions of Communications Suite components already installed, you might need to upgrade or remove some software before running the installer for the new release.

This section contains the following subsections:

When Incompatible Components Are Installed

During installation, the installer verifies that any Communications Suite components that are already installed on the host are compatible with the release of Communications Suite you are installing. If some components are not compatible, your installation is likely to be interrupted by incompatibility error messages. Therefore, it is best to survey installed software and do any upgrading before actually installing the Communications Suite software.

When you run the installer, you can see which incompatible components are on your host. If you want to install Application Server, Message Queue, or HADB, you can choose to Upgrade Software and let the installer upgrade these components in a separate upgrade session. For other product components, you cannot use the installer to upgrade, but instead must remove or upgrade the incompatible components by following instructions in the Sun Java Enterprise System 2006Q3 Upgrade Guide (for Java ES components) and the Sun Java Communications Suite 5 Upgrade Guide for Communications Suite components.

The installer upgrades or installs any shared components that are required for the product components you are installing.

Using the Installer to Survey Installed Software

You can use Solaris commands such as prodreg and pkginfo or the Linux rpm command to examine installed software. You can also use the installer itself to examine package-based software installations as described in the procedures in this section.

Note –

Do not rely only on the installer for information about installed software. You must also perform an independent survey of the host to determine what software is currently installed.

The following table lists the basic package command equivalencies for the UNIX platforms.

Table 1–2 UNIX Package Command Equivalencies

Task 

Solaris 

Linux 

Show installed package 

pkginfo

rpm –qa

Install package 

pkgadd

rpm -i

Remove package 

pkgrm

rpm –e

ProcedureTo Provide Access to Your Local Display for the Graphical Installer

  1. Set your DISPLAY environment variable.

    If you are logging in to a remote host, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.

    • Example for C Shell (host name myhost):


      setenv DISPLAY myhost:0.0

    • Example for Korn Shell (host name myhost):


      DISPLAY=myhost:0.0

  2. Grant display authorization.

    You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:


    myhost\> xauth extract - myhost:0.0|rsh -l root serverhost xauth merge -
    Note –

    For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.

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

  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 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 versions of shared components are compatible with other installed applications on the host.

  6. Exit the installer and do any upgrading necessary.

  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.

Determining If Your Hosts Are Ready

Before you start the installer, review the issues that determine system readiness:

Access Privileges

To install Communications Suite software, you must be logged in as root, or become superuser.

System Requirements

Before you install, ensure that the hosts in your deployment meet the minimum hardware and operating system requirements. For the latest information on the supported platforms and software and hardware requirements, refer to the following:

If the operating system found on the host does not satisfy Communications Suite recommendations, the installer cannot proceed. You must resolve this problem before installation.

Memory, Disk Space, and Swap Space Requirements

The installer runs a check to determine if your host has sufficient memory and disk space for the components you selected.

Note –

On Solaris 10, memory check is not performed if you are installing into a non-global zone.

Patch Requirements

During installation, the installer will discover any missing software patches. You cannot proceed with installation until these patches are installed.

ProcedureTo Install a Patch

the following example provides an example for installing a Solaris OS patch.

  1. Go to the Sunsolve site: http://sunsolve.sun.com

    (Location for Linux patches: http://www.redhat.com)

  2. Click Patches and Updates.

  3. Enter the patch number in the PatchFinder text box, and click Find Patch.

  4. Download the zip file for the patch.

  5. Expand the zip file.

    For example: unzip 112785-44.zip

    A directory is created for the patch files.

  6. Apply the patch.

    For example: patchadd 117885-44

    A directory is created for the patch files.

  7. In the installer, click Check Again.

    All system requirements are rechecked. Additional material on patches can be found in the following release notes: