Communications Suite 6 Update 2 Installation Guide

Skip to end of metadata
Go to start of metadata

Sun Java Communications Suite 6 Update 2 Installation Guide

This document contains the following sections:

See also:

Sun Java Communications Suite 6 Update 2 Installation Overview

This document describes how to install specific Communications 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 6 Update 2 Products and Components
Product & Version
Sun Convergence 1 Update 2
Messaging Server 7 Update 2 (32-bit/64-bit)
Calendar Server 6.3
Instant Messaging 8 Update 1
Delegated Administrator 7
Communications Express 6.3
Comms DSsetup 6.4
Messaging Server Sun Cluster HA Agent 7.0
Calendar Server Sun Cluster HA Agent
Instant Messaging Sun Cluster HA Agent

The Communications Suite installer does not install the Sun Java System Connector for Microsoft Outlook or Sun Java System Communications Sync, although it will be on the distribution.

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:

  • You also can use the Communications Suite 6 Update 2 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

The remainder of this document describes the steps for product installation, as follows:

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 6 Update 2 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.

The Sun Java Communications Suite 6 Update 2 runs on SPARC or x86 hardware running Solaris 9 or 10, or Red Hat Linux 3 or 4. The recommended platform is at least Solaris 10 08/07.

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 6 Update 2.

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 or later is recommended)
  • Web container:
    • Sun Java System Web Server 7.0
    • Sun Java System Application Server 9.1 Update 2

      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 6 Update 2 Products
Communications Suite Product Directory Server Web Container Access Manager
Convergence Yes Application Server 9.1 U2 only Optional. Required only if you want to use Access Manager for authentication and/or SSO.
Messaging Server Yes No Optional
Calendar Server Yes No Optional
Instant Messaging Yes 1 Optional
Delegated Administrator Yes 1 Optional
Communications Express Yes 1 Yes if want use Schema 2. Optional for Schema 1.

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

  • Note: The Communications Suite installer does install Message Queue 4.3, Security NSS, and other shared components.

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, perform the following steps:

  1. Download the software.
    For links to download sites, go to Get the Software.
  2. Install 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.
    Note
    Download the Application Server software zip file from the Communications Suite download site. Do not install the version of Application Server bundled with JES 5 Update 1. That is an older version of Application Server.

    Follow the instructions in the Sun Java System Application Server 9.1 Update 2 Installation Guide. Install Application Server before you install the other Sun Java System products.
    To verify which version of Application Server you have installed, see Verify Application Server Version.

  3. Install Directory Server 6.3 or later.
    Note
    Download Directory Server Enterprise Edition 6.3 (or later) 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. You must apply an upgrade patch as well as other patches to upgrade to DSEE 6.3.

    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.

    The simplest approach is to download and install the zip file version of DSEE 6.3 directly from the Communications Suite download site.

    To install Directory Server, follow the instructions in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

  4. Install the following products by running the JES 5 Update 1 installer:

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 6 Update 2 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

4. Install Communications Suite 6 Update 2 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:

Note
To install the localization version of Communications Express, you must install a localization patch. For details, see Installing the Localization Version of Communications Express.

Sample Sessions: Running commpkg

The following examples document the output of running commpkg:

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:

Note
If you install or upgrade Directory Server before you run the Communications Suite installer, the Directory Server installation process places an outdated version of comm_dssetup.pl on your system. You must use the current version of comm_dssetup.pl provided by the Communications Suite installer. However, the Comms Suite installer cannot install a new version with the commpkg install command. Instead, run the commpkg upgrade command to upgrade to the latest version of comm_dssetup.pl. If you install comm_dssetup.pl with the Comms Suite installer before you install Directory Server, you will have the up-to-date version. The DS installation process does not overwrite the latest version.

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:

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 2:

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 2 Initial Configuration.

Calendar Server 6.3:

Run the initial configuration program:

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

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

For detailed instructions, see Calendar Server 6.3 Initial Configuration.

Instant Messaging 8 Update 1:

Run the initial configuration program:

INSTALLROOT/im/sbin/configure

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

Convergence 1 Update 2:

Run the initial configuration program:

INSTALLROOT/iwc/sbin/init-config

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

Communications Express 6.3:

Run the initial configuration program:

INSTALLROOT/ce/sbin/config-uwc

For detailed instructions, see Communications Express 6.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. Note that 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. Note that 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. Note that 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:

Deployment Examples: Installation

To come.

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:

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

Labels:
guide guide Delete
installing installing Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 25, 2008

    Sun Java Communications Suite 6 Installation Guide
    Mentions IM Server and Cluster 3.2 as a product/component

    Communications Suite 6 Component Products Release Notes
    Lists IM Server with Cluster 3.1 SPARC only (no 3.2). The JCS 5 version of IM Server did not have Cluster 3.2 HA support.

    It is unclear to readers which document is correct. Either IM Server has Cluster 3.2 support (unlike JCS 5) or it does not (like JCS 5).

     

  2. Jan 29, 2008

    IM Server does have Sun Cluster 3.2 support on both the SPARC and x86 platforms. I just updated the Communications Suite 6 Component Products Release Notes to reflect this.

    We did not find any mention of Cluster 3.2 in the Communications Suite 6 Installation Guide. Can you point to where this is mentioned? Thanks.

  3. Feb 29, 2008

    should probably NOTE here : "Access Manager Server. Either run the JES 5 Update 1 Installer or deploy a single WAR file"

    ....that : DA users cannot deploy AM as a single WAR since this install method is not supported for Legacy Mode, which DA requires.

  4. Feb 29, 2008

    Ahead of step 4, customers will need to either upgrade comm_dssetup (SUNWcomds on sparc, sun-comms-dssetup-6.4* on Linux), or remove it and allow the Comms Installer to add it back; 'commpkg upgrade' has worked for me (on all platforms), but it's not fully functional yet so rather than document it, recommend cu's remove dssetup added during jes5u1 installation prior to running 'commpkg install'.

  5. Mar 07, 2008

    Mags,
    I added the note that DA users cannot deploy AM as a WAR file. See the note at bottom of "Where Do You Go to Install the Sun Java System Products?"

    Also added a note about upgrading comm_dssetup if an older DS version is present, in "Prepare Directory Server for Comms Suite (comm_dssetup)"

  6. Mar 13, 2008

    HA Messaging Server and HA DSEE 6.3 tested successfully with Sun Cluster 3.2

    HA DSEE requires a patch that should be forthcoming from Sun. dsldap_svc_start has an issue with Cluster 3.2

    Are there any config notes for IM Server and Cluster 3.2?

    The procedure should be similar to Calendar Server, just looking for an exact procedure. I can open a Cluster ticket on this but is likely they will kick it over to JCS group for this information based on past experience.

    Will see what I can work out via trial and error 

  7. Mar 13, 2008

    At the moment, Calendar Server on SunCluster 3.2 is not supported. However, we ran your steps by engineering and they agree it looks good. They are currently doing a bunch of tests of CS 6.3 on SC 3.2. So far, it is looking good, but it is still work in pgoress. When (if?) it becomes officially supported, we'd like to add your info to our wiki.

    We really appreciate your taking the time to do this.

    Michael

  8. May 09, 2008

    It is worth noting that you have to use the DSEE version that comes with JES 5 update 1 to upgrade to DSEE 6.3 if you are on Solaris 10 x86|SPARC and you are using the native package format.

    A number of patches are required in addition to the actual DSEE upgrade patch:

    http://blogs.sun.com/dsee/entry/dsee_6_3_released 

  9. May 09, 2008

    Nate –
    Thanks for the note. I've just asked the experts how best to advise users to get the recommended version of DSEE.

  10. May 09, 2008

    Nate –
    On advice from engineering, have added yr note to the DSEE install information. Links remain to DS Install Guide rather than to the blog (less permanent).

  11. May 07, 2009

    hi guys

    does anyone know how to add the "Attachment Search" to the menu bar ?...

    you can see this functionality here

    http://commsuite.demo.sun.com:7080/iwc
    (username: field1, password: cosmo)

    thanks

    1. Nov 17, 2010

      KenGra,

      AFAIK, that functionality was just for sample/demo purposes. But could be possible with Indexing and Search Service, which is in beta right now: Indexing and Search Service Documentation.

      Joe

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.