Sun Java Communications Suite 5 Installation Guide

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:

Solaris OS: /var/sadm/prod/SUNWcomm-entsys5i
Linux: /var/sadm/prod/sun-comm-entsys5i

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

Sun Java System Delegated Administrator 6.4 (Delegated Administrator)
Sun Java System Calendar Server 6.3 (Calendar Server)
Sun Java System Communications Express 6.3 (Communications Express)
Sun Java System Directory Preparation Tool 6.4 (Directory Preparation Tool)
Sun Java System Instant Messaging 7.2 (Instant Messaging)
Sun Java System Messaging Server 6.3 (Messaging Server)

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

Sun Cluster Agents for Sun Java System (Sun Cluster agents)
Sun Java System Access Manager 7.1 (Access Manager)
Sun Java System Application Server Enterprise Edition 8.2 (Application Server)
Sun Java System Directory Server Enterprise Edition 6.0 (Directory Server)
Sun Java System High Availability Session Store 4.4 (HADB)
Sun Java System Message Queue 3.7 UR1 (Message Queue)
Sun Java System Web Server 7.0 (Web Server)

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.

Graphical Mode (Interactive). Provides an interactive graphical wizard that leads you through the tasks of installing the software on a graphical workstation.
Text-based Mode (Interactive). Provides the same functionality as that of graphical mode, but you are prompted for responses on a line-by-line basis in a terminal window.
Silent Mode. Provides the ability to run the installer on multiple hosts, using a generated state file to specify input.

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:

English
French
German
Japanese
Korean
Spanish
Simplified Chinese
Traditional Chinese

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:

Compatible product components are installed.

Compatible product components do not need to be reinstalled and will not be available for selection in the installer.
Incompatible product components are installed.

If the installer identifies incompatibilities between product components you have selected and product components that are already installed locally, you might be prompted to remove or upgrade the incompatible installed product component. The installer cannot continue until these incompatibilities are resolved. If a component shows as upgradable at component selection, you can go back to the first page of the installer and choose to Upgrade instead of Install. For additional information on upgrading incompatible product components, refer to How Upgrading Works.
Incompatible shared components are installed.

It is not uncommon for existing hosts to already contain versions of shared components, such as J2SE or NSS. If the installer finds shared components whose version is incompatible with the version of Communications Suite you are installing, those shared components are listed. If you proceed with installation, the installer automatically upgrades the shared components to compatible versions.

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:

Selecting a Product Component. In most cases, when you select a product component for installation, the installer automatically selects all its subcomponents.

The installer also selects the components and subcomponents upon which the selected product component depends. For example, if you select Application Server, the installer automatically selects Message Queue.
Deselecting a Product Component. In most cases, when you deselect a product component, the installer automatically deselects all its subcomponents.

If you deselect a product component that is required locally or remotely for another selected product component, the installer displays various warnings when you attempt to proceed.
Selecting a Subcomponent. If you select a subcomponent, the installer automatically selects the product component to which it belongs, but not necessarily the other subcomponents.

If the selected subcomponent depends on other components or subcomponents, the others are automatically selected.
Deselecting a Subcomponent. If you deselect a subcomponent, the installer deselects only that subcomponent and not the other subcomponents.

If you deselect a subcomponent that is required locally or remotely for another selected product component, the installer displays various warnings when you attempt to proceed.

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:

System is ready for installation. When this message is displayed, the installer can proceed.
System is ready for installation, however, a resource, such as memory, is not at the recommended level. When this message is displayed, the installer can proceed but you should consider providing additional resources.
System is not ready for installation. When this message is displayed, the installer cannot proceed and you must take some action, such as installing missing patches.

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:

Configure Later. During installation, you enter only the minimum values that are necessary for installing, then perform postinstallation configuration.
Configure Now. During installation, you configure product components that permit installation-time configuration. The information you specify might be just a few common parameters (common server settings), or it might include detailed component-specific parameters (product component settings).

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:

Solaris SPARC: /var/sadm/prod/SUNWcomm-entsys5i/Solaris_sparc
Solaris x86: /var/sadm/prod/SUNWcomm-entsys5i/Solaris_x86
Linux: /var/sadm/prod/sun-comm-entsys5i/Linux_x86

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:

Solaris OS: /var/sadm/prod/SUNWcomm-entsys5
Linux: /var/sadm/prod/sun-comm-entsys5

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:

Solaris OS: /var/sadm/install/logs
Linux: /var/opt/sun/install/logs

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