Sun Java Communications Suite 5 Installation Guide

How to Use This Chapter

The example installation sequences in this chapter are intended to provide high-level guidelines for some common Communications Suite installations. These are not literal procedures, but instead provide the sequential steps required to implement particular deployment scenarios.

The single-session examples describe typical steps for installing one or a number of product components on a single host in a single installation session. The remaining examples describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions. For the most part, the sequences in this chapter are based on the relationships among the product components as shown in Sun Java Enterprise System 5 Installation Planning Guide.

At component selection, the installer identifies incompatible versions of components as well as unmet requirements. You receive warning messages that identify the problem and tell you what you need to do. Many of these messages tell you about requirements that are not yet met. Other messages tell you that incompatible versions of some or all of the components you are trying to install are already on the local host. You can use the installer to identify components that are already on your local host. For instructions, refer to When Incompatible Components Are Installed.

Tip –

Installation goes most smoothly if any incompatible versions of Communications Suite components are identified and removed or upgraded before starting the installer.

Table 2–1 Installation Sequence Guidelines


Installation Guideline Topic	Description
Sun Cluster software	If you are using this product component with Sun Cluster software, you must perform a precise series of tasks before installing any product components. Communications Suite components that can be configured for Sun Cluster are Calendar Server, Instant Messaging, and Messaging Server. Several Java ES components can also be configured for Sun Cluster. See the Sun Java Enterprise System 5 Installation Guide for UNIX for instructions. Also, refer to Sun Cluster Software Example to see Sun Cluster guidelines.
Monitoring	Monitoring Console cannot be run on the same host as Communications Suite or Java ES product components that it monitors. Therefore, it should be installed on another host in a separate installation session. See the Sun Java Enterprise System 5 Installation Guide for UNIX for information on installing Monitoring Console.
Installation-time configuration	The following components can be installed in a Configure Now installation, but configuration cannot be done during installation: Sun Cluster components and Communications Suite components.
Upgrading	You might receive messages asking you to remove or upgrade product components that are already on the host. For some components (Application Server, Message Queue, and HADB), you can return to the beginning of installation and choose to Upgrade Existing Software. After you have upgraded, you can then start the installation. For full instructions on upgrading Communications Suite components without using the installer, see the Sun Java Communications Suite 5 Upgrade Guide, for Java ES components, refer to Sun Java Enterprise System 2006Q3 Upgrade Guide
Solaris 10 zones	In a Solaris 10 zones environment, shared components must be installed separately in the global zone before installing into a local zone. Message Queue can only be installed in the global zone, after which it is propagated to all non-global zones.
Remote component	If you are using a remote product component to fulfill dependencies, the remote product component must be installed and running before installing any product components that depend on it.
Third-party component	If you are using a third-party product, such as a WebLogic web container, the third-party product component must be installed and running before installing any Communications Suite product components that depend on it.
Access Manager modes	You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Communications Suite product components. Access Manager Realm (7.x) installation type cannot be used with Communications Suite.
LDAP Schema 1	The Calendar-Messaging Schema 1 Example is the only example based on LDAP Schema 1. All other examples in this chapter are based on Schema 2. See: Understanding Schema Choices in Sun Java Communications Suite 5 Deployment Planning Guide for more information.