test

Sun Java Communications Suite 5 Installation Guide

Chapter 1 Preparing for Installation

This chapter provides information that will help you install the Sun JavaTM Communications Suite software. Before starting the tasks documented in this guide, you should have already planned your installation according to the Sun Java Communications Suite 5 Deployment Planning Guide. You should also be familiar with the reference material associated with installation in the Sun Java Enterprise System 5 Installation Reference for UNIX.

This chapter contains the following sections:

How the Communications Suite Installer Works

Communications Suite integrates a number of Sun server and client products to support distributed communication and collaboration applications. In this document, these products are referred to as product components. The Communications Suite installer installs the Communications Suite and Java Enterprise System (Java ES) product components and shared components in various combinations, one host at a time. Because of the complex interrelationships of the components, installation requires much more preinstallation and postinstallation effort than is required to install a single product component.

After installation, the installer utilities, logs, and data files are located here:

This section contains the following subsections:

Communications Suite Components Used in This Release

The Communications Suite software consists of a collection of Sun server and client products and their supporting shared components that work together to support distributed applications across a network. The Communications Suite 5 release includes the following selectable components. (The abbreviated names used in this guide follow the name and version.)

In addition, Communications Suite 5 also includes Sun Java System Connector for Microsoft Outlook 7.2. Connector for Microsoft Outlook is not installed with the Communications Suite installer. Instructions for installing Connector for Microsoft Outlook are available in the Sun Java System Connector for Microsoft Outlook 7.2 Installation Guide.

Java ES Components Used in This Release

The Java ES software consists of a collection of Sun server-side products and their supporting shared components that work together to support distributed applications across a network. The Communications Suite 5 release includes the following selectable Java ES components. (The abbreviated names used in this guide follow the name and version.)

To see the full list of services and subcomponents as displayed in the installer, refer to Appendix E, Product Components for This Release. This appendix also lists the shared components that are provided with this release. Some Communications Suite product components work with Java ES products that are not installed with the Communications Suite installer, for example, Sun Java System Monitoring Console 1.0 (Monitoring Console) and Sun Java System Portal Server. Information about installing these Java ES products is available in the Sun Java Enterprise System 5 Installation Guide for UNIX.

Available Installer Modes

The Communications Suite installer is an installation framework that uses the Solaris pkgadd or Linux rpm utility to transfer Communications Suite software to your system. You can install Communications Suite interactively or by means of a reusable script.

Tip –

You can run the installer without installing software. This is useful for surveying Communications Suite software on your existing hosts.

How Language Selection Works

The interactive installer runs in the language specified by the operating system locale setting on the host. The following languages are available:

If your operating system language is not listed, the installer runs in English.

The installer automatically installs English versions of all components. In addition, you can choose to install the localized packages for all languages by selecting the multilingual packages when components are selected for installation.

The installer cannot install additional language packages for previously-installed components. However, you can use the pkgadd, rpm, or swinstall utilities to install language package at any time. Language packages are list in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.

How the Installer Checks for Preexisting Components

During installation, the installer surveys the software that is already installed on the host where you are installing and identifies the following:

How the Installer Checks Component Dependencies

Many product components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of product components to verify that the product components you select during installation will function properly together. For this reason, the installer might prompt you to include certain product components as you make your selections.

In general, the installer uses the following rules for handling dependencies among the product components:

How the Installer Checks for System Readiness

After the components you have selected are found to be acceptable for installation and you have indicated their target installation directories, the installer performs a system check to determine if your host meets the requirements for the components you selected.

The installer checks for disk space, memory, swap space, operating system, patches and operating system resources based on the components and the installation directories provided and informs you about the state of your system using the following messages:

How the Installer Handles Configuration and Parameter Setting

Many product components require some degree of installation-time configuration. The extent of installation-time configuration you are required to perform depends on which product components you select and which installation type you choose.

The following configuration types are available in the installer:

It is important to keep track of the configuration information values as you proceed through installation-time configuration or postinstallation configuration. Many of the product components rely on the specifics of other component configuration parameters in order to function correctly. At the end of a Configure Now installation, you can view the configuration parameters that were specified by examining the Installation Summary.

Common server settings are parameters that multiple product components use. For example, most product components require that you specify an administrative ID and password. By setting these common values, you are setting default values for all product component administrative IDs and passwords.

Product component settings are parameters that apply to a particular product component. These settings are requested during installation only if you have selected the Configure Now type. Some of these settings are populated from the common server settings.

How Upgrading Works

Using the graphical installer, you can upgrade shared components and some product components. In a graphical installation session, if upgradable product components are detected on your host, the Choose to Upgrade or Install page is displayed. The components that can be upgraded by the installer are listed in the following table, along with explanation on any Solaris zones issues that might apply.

Table 1–1 Upgrade Support Within the Communications Suite Installer

Product Component 

Situation Where the Installer Can Upgrade 

Solaris Zones Issues 

Application Server 

Application Server 7.0 bundled with Solaris 9 

Application Server 8.0 bundled with Solaris 10 

Application Server 8.1.0 installed with Java ES 2005Q1 (release 3) 

Application Server 8.1.2 installed with Java ES 2005Q4 (release 4) 

Before Application Server can be installed into a non-global sparse-root zone, the bundled version must be removed from the global zone. 

HADB 

HADB installed with Java ES 2005Q1 (release 3) 

HADB installed with Java ES 2005Q4 (release 4) 

 

Message Queue 

Message Queue bundled with Solaris 9 

Message Queue bundled with Solaris 10 

Message Queue installed with Java ES 2005Q1 (release 3) 

Message Queue installed with Java ES 2005Q4 (release 4) 

Message Queue can only be installed in the global zone, or in a whole root non-global zone. 

From the global zone, Message Queue always propagates to non-global zones. 

Communications Express 

 

Cannot install UWC in a local, sparse root non–global zone using the installer. Instead, you need to manually add the UWC and Access Manager packages using pkgadd.

If you are not planning to install any of these product components, you can choose Install New Software. If you are going to install any of these components, select Upgrade Existing Software to initiate an upgrade session. After the upgrade session finishes, you can then start a new installation session. This functionality is not supported for a text-based installation.

During installation, you might encounter additional upgrade situations if the installer identifies incompatible versions of product components that cannot be upgraded by the installer. In this case, you will receive messages that certain products components must be removed or manually upgraded before you can continue with installation. Such upgrading for Communications Suite product components is fully documented in the Sun Java Communications Suite 5 Upgrade Guide and for Java ES product components in the Sun Java Enterprise System 2006Q3 Upgrade Guide.

Shared components are upgraded by the installer along with the selected product components. Shared components can also be upgraded in a dedicated installation session that installs only shared components, enabling them to be synchronized to the current release. If you choose to install the Shared Components item, all required shared components for the Communications Suite release are installed or upgraded.

Note –

If the installer is run in a non-global Solaris zone with a sparse root file system, the Shared Component item is not available for selection .

How Logging Works

During the course of installation or uninstallation, log records are generated for the operations that occur. These records are saved into a single file in a Unified Logging Format (ULF). The installer Log Viewer (viewlog command) provides a user-friendly interface for examining these log records.

After installation is complete, the Log Viewer is located with the installer here:

After uninstallation, the Log Viewer is removed along with the installation and uninstallation utilities. See How Uninstalling Works for information.

For instructions on using the logs and Log Viewer, refer to Examining Installation Log Files.

How Uninstalling Works

Communications Suite provides an uninstallation utility for removing component products that were installed on your local host using the installer. The uninstaller checks product dependencies for the host on which it is running, issuing warnings when it discovers a dependency.

The uninstaller can be run in graphical, text-based, or silent mode. After installation is complete, the uninstaller is located here:

After uninstallation, the Log Viewer is removed along with the installation and uninstallation utilities. The ULF logs themselves are not removed, and are located here:

For instructions on using the uninstaller refer to Chapter 9, Uninstalling Communications Suite Product Components.

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:

Determining If You Can Use an Installation Sequence Example

The order in which you install the product components on the hosts of your system is crucial to installation success. You might be able to use one or more of the sequence examples provided in Chapter 2, Example Installation Sequences to guide you. These sequences include the high-level tasks that are required for some typical installations.

Full instructions for planning your installation are contained in the Sun Java Enterprise System 5 Installation Planning Guide.

Verifying General Installation Prerequisites

The following table lists the tasks that you should perform before beginning any type of installation. The left column lists the order in which you should perform the tasks. The right column contains the location of instructions and other useful information. Not all tasks are required for all installations.

Table 1–3 Preinstallation Checklist

Task 

Instructions and Helpful Information 

1. Plan your installation. 

Refer to the Sun Java Enterprise System 5 Installation Planning Guide.

If installing Sun Cluster software, see Sun Cluster Software Example.

If installing Monitoring Console, see Sun Java Enterprise System 5 Installation Guide for UNIX.

2. Determine if any release noted issues affect your installation. 

Before performing any of the procedures described in the Installation Guide, you should read the Sun Java Communications Suite 5 Release Notes and the Sun Java Enterprise System 5 Release Notes for UNIX. These notes contain installation issues that might pertain to your deployment.

3. Survey your hosts for existing software. 

Refer to Surveying Existing Hosts.

If you need to upgrade Communications Suite product components, refer to the Sun Java Communications Suite 5 Upgrade Guide. If you need to upgrade Java ES product components, refer to the Sun Java Enterprise System 2006Q3 Upgrade Guide.

4. Upgrade any existing components that are incompatible with the Communications Suite 5 release. 

When Incompatible Components Are Installed

Sun Java Communications Suite 5 Upgrade Guide

Sun Java Enterprise System 2006Q3 Upgrade Guide

For information on using the platform package commands, refer to their respective man pages. 

5. Verify that system requirements are met. 

Refer to Determining If Your Hosts Are Ready.

Sun Java Communications Suite 5 Release Notes and Platform Requirements and Issues in Sun Java Enterprise System 5 Release Notes for UNIX

6. Determine if an installation sequence example can be used. 

Refer to Chapter 2, Example Installation Sequences.

7. For a Configure Now installation, gather configuration information for product components. 

Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX provides product component configuration information.

Chapter 4, Configuration Worksheets, in Sun Java Enterprise System 5 Installation Reference for UNIX provides worksheets for gathering your data.

8. Make a copy of the product registry file. A backup copy is helpful in recovering if installation fails.

Solaris OS: /var/sadm/install/productregistry

Linux: /var/opt/sun/install/productregistry

9. To run as a non-root user for Directory Server, create system accounts before configuring. 

Create the necessary system accounts required for non-root. 

10. If installing product components that depend on servers or services that are already installed, ensure that the existing servers and services are accessible. 

 

11. If installing Directory Server, verify that Perl is installed. 

Solaris: Perl packages (SUNWperl5*) can be found on the Solaris media.

Linux: /usr/bin/perl must be present before installation.

If Perl is not present, use pkgadd, rpm -i, or swinstall to add the packages.

12. If you are installing a communications product component, verify that the domain name of the host on which Access Manager will be installed is set. 

To set the domain name, do one of the following: 

  • If the file /etc/resolv.conf exists, enter the fully qualified domain name in the domain configuration entry. Example: domain mycomputer.company.com

  • If the file /etc/resolv.conf does not exist, enter the following command syntax:

    # domainname fully_qualified_domain_name

13. Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:

192.18.99.999 mycomputer.company.com mycomputer loghost

14. Verify that the second column returned by getent hosts for your target system contains the FQDN rather than the simple hostname.

For example: 

getent hosts ip-address

15. When installing the Load Balancing Plugin with Apache Web Server, Apache Web Server must be installed and configured before beginning installation.  

On Linux only, you must first install Application Server, then install Apache Web Server, and finally install the Load Balancing Plugin. 

If not already done, install and configure Apache Web Server. For more information, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

16. If installing Access Manager for deployment on a third-party web container, you must choose the Configure Later type and run a postinstallation configuration script. 

For more information, see the Sun Java System Access Manager 7.1 Postinstallation Guide.

17. If this is a reinstallation, verify that the Web Server installation directory does not exist. If it does, remove or rename the directory.

Default installation directory for Web Server: 

Solaris OS: /opt/SUNWwbsvr7

Linux: /opt/sun/webserver7

18. If you are upgrading J2SE software, verify that you have stopped other products that depend on the J2SE component you are upgrading. 

Refer to the Sun Java Enterprise System 2006Q3 Upgrade Guide.

19. If you are implementing Messaging Server, verify that sendmail is disabled.

If needed, disable sendmail on Solaris 9 and Linux as follows:

/etc/init.d/sendmail stop

If needed, disable sendmail on Solaris 10 as follows: 

svcadm disable sendmail

20. If your host does not have direct connectivity to the Internet, an HTTP proxy needs to be specified. 

An Application Server example can be found in the Sun Java System Application Server Enterprise Edition 8.2 Administration Guide

21. On Linux, remove the /usr/share/bdb/db.jar link if it exists.

 

22. On Linux, verify that Ant 1.5.2 is not on the host: rpm –qa | grep ant

To remove it: rpm –e ant-1.5.2-23 ant—libs-1.5.2-23

23. On Linux, verify that Korn shell is installed. 

To install Korn shell, go to the RPM directory and run the rpm –i pdksh command.

Getting the Communications Suite Software

You can get the Communications Suite software in the following ways:

For a listing of the distribution bundles for this release, refer to Chapter 1, Java ES Distribution Bundles, in Sun Java Enterprise System 5 Installation Reference for UNIX.

Making an Installation Image

The Communications Suite distribution is designed so that you can put the installation files in a shared location. The benefit of this is that the installation files can then be run from this shared location as often as needed.

ProcedureTo Create an Image on Your Network

This section provides instructions for making a Solaris SPARC installation image available on your site network.

  1. Log in as root or become superuser.

  2. Create a shared directory on your network. For example:


    mkdir shared-location/comms5

  3. Access your installation files from the web site, the CD, or the DVD, then prepare the installation files to be shared.

    Note –

    Installation cannot be done directly from a mounted ISO image. Instead, the image must be copied onto your network.

    1. Create an installation image from the mounted ISO image. For example:


      unzip compressed-file.zip
lofiadm -a pathname/image.iso /dev/lofi/1

      If /dev/lofi/1 is already in use, refer to the lofiadm (1M) man page.


      mkdir mountpoint
mount -F hsfs /dev/lofi/1 mountpoint
cd mountpoint
find . -print | cpio -pdum shared-location/comms5

      After copying is done, unmount the ISO image:


      cd
umount mountpoint
lofiadm -d /dev/lofi/l

      Repeat this step for the remaining ISO images.

    2. Create an installation image from the CD or DVD. For example:


      cd /cdrom/cdrom0
find . -print | cpio -pdum shared-location/comms5

      Repeat this step for the remaining CDs.

    3. Create an installation image from the compressed archive.

      For example:


      cd shared-location/comms5
unzip pathname/archive.zip

      Repeat this step for the remaining compressed archive files.

    Note –

    If you copy files for multiple platforms to the shared location, you will receive a query similar to the following in relation to the README file and the COPYRIGHT file:

    File already exists. OK to overwrite?

    Type Yes. These files are identical for all platforms.