Sun Java Communications Suite 7 Installation Guide

This document contains the following sections:

See also:

• Installing Connector for Microsoft Outlook

Sun Java Communications Suite 7 Installation Overview

This document describes how to install specific Communications Suite products on a specific machine (a machine can mean either a computer or a Solaris Zone). It is designed to be a low-level document describing the product installation tasks required for new deployments and upgrades. The following table shows the products that are available in the installer:

Communications Suite 7 Products and Components

The Communications Suite installer does not install Sun Java System Connector for Microsoft Outlook nor Sun Java System Communications Sync, although both products are included with the distribution.

• For installation instructions for Connector for Microsoft Outlook, see Installing Connector for Microsoft Outlook.

• For installation instructions for Communications Sync, see Sun Java System Communications Sync 3.0 Release Notes.

This document assumes you have already made your architectural and design decisions: for example, which products you want to install, the number of machines in your deployment, and the number of front-end and back-end servers. If you are still in the planning or evaluating process, see the following documents:

Deployment Planning Help

If you do not have an existing architecture or design, refer to Communications Suite Deployment Planning Guide.

Communications Suite Upgrade Guide

To upgrade your current Communications Suite deployment, refer to Communications Suite 7 Upgrade Guide.

Evaluating Communications Suite

If you are looking for a document to help you install and evaluate the product, refer to:

• Deployment Example: Sun Java Communications Suite 7 on a Single Host
• Deployment Example: Sun Java Communications Suite 7 on a Single Host (Linux)
• Deployment Example: Installing Communications Suite 6 on a Solaris Zone

Communications Suite Multi-Host Deployment

If you are planning a multi-host deployment, you can also take advantage of a tool developed by Sun deployment engineering: EMRA, a multi-host install and configuration tool. You can also refer to Deployment Example: Sun Java Communications Suite 6 on Multiple Hosts.

Communications Suite Flowchart and Installation Scenarios

Use the Communications Suite 7 Installation Flowchart to guide you to specific installation scenarios. The flowchart can help in the following ways:

• Provides a decision tree for installing Communications Suite products and the Sun Java System products that support Communications Suite
• Directs you to specific sets of installation instructions based on your decisions

Use the Communications Suite 7 Installation Scenarios to select a product-based or component-based set of high-level instructions.

High-Level Steps for Installing Communications Suite

The remaining information describes the high-level steps to install Communications Suite products. These steps give a general installation flow to install any or all of the Communications Suite products.

1. Check That Your Platform and Operating System Support Communications Suite.
2. Install the Sun Java System Software Required to Run Communications Suite.
3. Define and Set Up Additional Requirements for Individual Communications Suite Products.
4. Install Communications Suite 7 Products.
5. Prepare Directory Server for Communications Suite (run comm_dssetup.pl).
6. Gather Information Needed to Configure Communications Suite Products.
7. Create Initial Configurations for the Individual Communications Suite Products.

1. Check That Your Platform and Operating System Support Communications Suite.

Recommended platforms for Sun Java Communications Suite 7 are:

For details, see this list of operating system and platform requirements.

In addition, certain Communications Suite products have minimum disk and memory requirements. For details, refer to Memory and Disk Space Requirements for Communications Suite 7.

2. Install the Sun Java System Software Required to Run Communications Suite.

The Communications Suite products require other Sun Java System software products to be installed before you install Communications Suite. The dependencies vary among the Communications products, but many have a common set.

Which Products Do You Need?

• Sun Java System Directory Server Enterprise Edition 5.x or 6.x (6.3.1 is recommended for Communications Suite 7)

• Web container:
  • GlassFish Enterprise Server 2.1 (recommended, required for some Communications Suite 7 products)
  • Sun Java System Web Server 7.0 (supported)
  • Sun Java System Application Server 9.1 Update 2 (supported)
    Download the following version: Application Server 9.1 Update 2 with High Availability Database (HADB) - Zip/File Based. This version provides shared components needed by Application Server and Communications Suite. Note: You can configure this version of Application Server without using the HADB.

• Sun Java System Access Manager
  Access Manager (AM) is optional for Convergence to support AM authentication and/or AM SSO.

The following table shows the software required by each product.

Software Requirements for Communications Suite 7 Products

1 - Web Server 7.0 update 1, Application Server 8.2P2, or Application Server 9.1 Update 2 (recommended)

For more information about software product dependencies, see Product Version Compatibility.

For products needed to deploy Convergence, see the Product Version Compatibility Requirements for Convergence 1 Update 3.

Where Do You Go to Install the Sun Java System Products?

The Communications Suite installer does not install these software products. To install these products for Communications Suite 7, perform the following steps:

1. Download the software.
   For links to download sites, go to Get the Software.
2. Install GlassFish Enterprise Server 2.1.
   Download the GlassFish Enterprise Server 2.1 software zip file from the Communications Suite download site.

   Note If you are installing Application Server 9.1 Update 2, do not install the version of Application Server bundled with JES 5 Update 1. That is an older version of Application Server.

3. Follow the instructions in Communications Suite 7 Installation Scenario - GlassFish Enterprise Server.
4. Install Directory Server 6.3.1.

   Note Download Directory Server Enterprise Edition 6.3.1 from the Communications Suite download site before you run the JES 5 Update 1 installer. Do not install the Directory Server software bundled with JES 5 Update 1. That is an older version of Directory Server. If you already started with an older DSEE version, you can still upgrade to the recommended DSEE 6.3.1. You must apply an upgrade patch as well as other patches to upgrade to DSEE 6.3.1. For example, if you obtained the native package format of DSEE on the Solaris 10 x86 or SPARC platform, you must start by installing the DSEE 6.2 version bundled with JES 5 Update 1, then upgrade to DSEE 6.3.1. The simplest approach is to download and install the zip file version of DSEE 6.3.1 directly from the Communications Suite download site.

   To install Directory Server, follow the instructions in Communications Suite 7 Installation Scenario - Directory Server.

5. Install the following products by running the JES 5 Update 1 installer:
   • Access Manager 7.1 (Delegated Administrator 7 no longer requires Access Manager. So, only install Access Manager if you are using it for single sign-on capabilities.)
   • Web Server 7.0
     To install Access Manager and Web Server, follow the instructions in the Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.
     Here are some other information sources and methods for installing these products:
     • Sun Java System Web Server 7.0 Update 1 Installation and Migration Guide
     • Access Manager Server. Either run the JES 5 Update 1 Installer or deploy a single WAR file. For details, see the Access Manager Configuration Guide. You can also find installation instructions in this Access Manager Deployment Example.

       Note If you are installing Access Manager 7.1 on a Linux system, you should verify that a compatible version of Java Development Kit (JDK) is installed. For details, see Verifying the Correct JDK Version to Support Access Manager.

3. Define and Set Up Additional Requirements for Individual Communications Suite Products.

In addition to the generic suite requirements, some products might have specific requirements. For details about individual product requirements, see the Communications Suite 7 Release Notes.

Messaging Server

• You must ensure DNS is running and configured properly. For details, see DNS configuration.
• Recommended file systems for the message store are listed in Message Store File Systems.
• Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see Default Port Numbers.

Calendar Server 7

Install the Calendar Server 7 back-end database first. Then install the Calendar Server 7 front end.

Calendar Server 6.3

• Set up Calendar Server 6.3 administrator accounts and plan for Calendar Server hosted domains. For details, see Calendar Server Pre-Installation Considerations.

4. Install Communications Suite 7 Products.

After the platform and software requirements have been met (as described previously), take these steps:

1. Download the software.
   To download Communications Suite, including the installer, go to Get the Software.
2. Run the installer.
   The installer is a single unified utility called commpkg. It installs (but does not configure) the Communications Suite products. commpkg does all the necessary preparation work before installing the product software on the system. Run the following command:
   ./commpkg install

For step-by-step instructions, see To Run the Communications Suite Installer.

For details about other features of the commpkg installer, see the following information:

• commpkg install Usage
• Install in Silent Mode
• Perform Multiple Installations with Alt Root
• Install on Solaris Zones
• Communications Suite Installer: General Syntax and Verbs

Sample Sessions: Running commpkg

The following examples document the output of running commpkg:

• Sample Session - Communications Suite 7 Simple Install and Uninstall.
• Sample Session - Communications Suite 7 Install Using altroot.
• commpkg upgrade sample session.

5. Prepare Directory Server for Communications Suite (run comm_dssetup.pl).

All Communications Suite components require that you run the comm_dssetup.pl script against Directory Server. For example:

cd INSTALLROOT/dssetup/sbin
./comm_dssetup.pl

For detailed instructions, see the following:

• Communications Suite Directory Server Setup Script: comm_dssetup.pl

6. Gather Information Needed to Configure Communications Suite Products.

Before you run a configuration program, you need to gather specific configuration information for each product. Use the following worksheets:

• Convergence 1 Update 3 - Configuration Worksheet
• Messaging Server 7 Update 3 - Configuration Worksheet
• Calendar Server 7 - Configuration Worksheet
• Calendar Server 6.3 - Configuration Worksheet
• Instant Messaging 8 Update 2 - Configuration Worksheet
• Delegated Administrator 7 - Configuration Worksheet
• Indexing and Search Service 1 - Configuration Worksheet

7. Create Initial Configurations for the Individual Communications Suite Products.

For each Communications Suite product, you must run a separate configuration program. Each configuration program creates an initial runtime configuration to make the product operational. The program provides a generic, functional server configuration, which you can refine by making specific configurations and customizations.

You will typically want to configure the back-end servers before configuring clients. Client configurations require certain server attributes to be defined.

Delegated Administrator 7:

Run the initial configuration program:

INSTALLROOT/da/sbin/config-commda

For detailed instructions, see Delegated Administrator 7 Initial Configuration.

Messaging Server 7 Update 3:

Run the initial configuration program:

For 32-bit: INSTALLROOT/messaging/sbin/configure

For 64-bit: INSTALLROOT/messaging64/sbin/configure

For detailed instructions, see Messaging Server 7 Update 3 Initial Configuration.

Calendar Server 7:

Run the initial configuration program:

INSTALLROOT/sbin/init-config

For detailed instructions, see Calendar Server 7 Initial Configuration.

Calendar Server 6.3:

Run the initial configuration program:

For Solaris OS: INSTALLROOT/calendar/SUNWics5/cal/sbin/csconfigurator.sh

For Red hat Linux: INSTALLROOT/calendar/calendar/sbin/csconfigurator.sh

For detailed instructions, see Calendar Server 6.3 Initial Configuration.

Indexing and Search Service 1:

Run the initial configuration program:

INSTALLROOT/bin/setup.sh

For detailed instructions, see Indexing and Search Service 1 Initial Configuration.

Instant Messaging 8 Update 2:

Run the initial configuration program:

INSTALLROOT/im/sbin/configure

For detailed instructions, see Instant Messaging 8 Update 2 Initial Configuration.

Convergence 1 Update 3:

Run the initial configuration program:

INSTALLROOT/iwc/sbin/init-config

For detailed instructions, see Convergence 1 Update 3 Initial Configuration.

Messaging Server Sun Cluster HA Agent 7.0:

Run the initial configuration program:

msg-scha-base/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. You must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Messaging Server Sun Cluster HA agent, see Configuring Messaging Server for High Availability.

Calendar Server Sun Cluster HA Agent:

Run the initial configuration program:

cs-scha-base/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. You must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Calendar Server Sun Cluster HA agent, see Configuring Calendar Server Software for High Availability (Failover Service).

Instant Messaging Sun Cluster HA Agent:

Run the initial configuration program:

im-scha-base/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. You must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Instant Messaging Sun Cluster HA agent, see Configuring Instant Messaging for High Availability.

Uninstalling Communications Suite

To uninstall the Communications Suite products installed on the local machine, run the following command:

cd INSTALLROOT/CommsInstaller/bin
./commpkg uninstall

For detailed instructions, see the following:

• commpkg uninstall Usage
• Uninstall in Silent Mode
• Communications Suite Installer: General Syntax and Verbs

Getting Information About Which Products Are Installed

To determine the Communications Suite software components installed on the machine, run the following command:

./commpkg info --verbose

This command prints product information installed in the INSTALLROOTS. To print information about one product, run this command:

./commpkg info --verbose installroot|product name

For details about the commpkg info command, see the following:

• commpkg info Usage
• Communications Suite Installer: General Syntax and Verbs

To determine which version of Application Server you have installed, see Verify Application Server Version.