h1. Sun Java Communications Suite 6 Update 2 Installation Guide
This document contains the following sections:
{toc:minLevel=2|maxLevel=2|location=top|type=list}
See also:
* [Installing Connector for Microsoft Outlook|Connector for Microsoft Outlook 7.3 Update 1 Installation Guide]
h2. 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:
h5. 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.
* For installation instructions for Connector for Microsoft Outlook, see the [Installing Connector for Microsoft Outlook|Connector for Microsoft Outlook 7.3 Update 1 Installation Guide].
* For installation instructions for Communications Sync, see the [Sun Java System Communications Sync 3.0 Release Notes|http://docs.sun.com/app/docs/doc/819-4706].
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:
* If you do not have an existing architecture or design, refer to the [CommSuite:Communications Suite Deployment Planning Guide].
* If you are looking for help with upgrading your current Communications Suite Deployment, refer to [Upgrading to Communications Suite 6 Update 2|Communications Suite 6 Update 2 Upgrade Guide].
* If you are looking for a document to help you install and evaluate the product, refer to
[Deployment Example: Sun Java Communications Suite 6 Update 1 on a Single Host|CommSuite6U1:Sun Java Communications Suite 6 Update 1 on a Single Host] or
[Deployment Example: Installing Communications Suite 6 on a Solaris Zone|Sample Session - Installing Communications Suite 6 on a Solaris Zone]
* If you are planning a multi-host deployment, you can also take advantage of a tool developed by Sun deployment engineering: [EMRA|CommSuite:Enterprise Messaging Reference Architecture Toolkit], a multi-host install and configuration tool. You can also refer to
[Deployment Example: Sun Java Communications Suite 6 on Multiple Hosts|CommSuite6:Sun Java Communications Suite 6 on Multiple Hosts].
* 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.]
h2. {anchor:systemreqs} 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|http://docs.sun.com/app/docs/coll/1236.3], or Red Hat Linux 3 or [4|http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/x8664-multi-install-guide/]. The recommended platform is at least Solaris 10 08/07.
For details, see this list of [operating system and platform requirements|Communications Suite 6 Update 2 Component Products Release Notes#OSPlatform].
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|Communications Suite 6 Update 2 Component Products Release Notes#Memory].
h2. {anchor:installrequiredproducts} 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.
h3. 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.
h5. 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|Communications Suite 6 Update 2 Component Products Release Notes#ProdVerCompatibilityforC6].
For products needed to deploy Convergence, see the [Product Version Compatibility Requirements for Convergence 1 Update 2|Communications Suite 6 Update 2 Component Products Release Notes#convergenceproductreqs].
* Note: The Communications Suite installer _does_ install Message Queue 4.3, Security NSS, and other shared components.
h3. 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:
# *Download the software.*
For links to download sites, go to [Get the Software|Get the Software].
# *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.
{info:title=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.
{info}
Follow the instructions in the [Sun Java System Application Server 9.1 Update 2 Installation Guide|http://docs.sun.com/app/docs/doc/820-3797]. 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|Verify Application Server Version].
# *Install Directory Server 6.3 or later.*
{info:title=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.
{info}
To install Directory Server, follow the instructions in the [Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide|http://docs.sun.com/app/docs/doc/820-2761].
# *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|http://docs.sun.com/app/docs/doc/820-2827].
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|http://docs.sun.com/app/docs/doc/820-1060]
#** Access Manager Server. Either run the JES 5 Update 1 Installer or deploy a single [WAR file|http://docs.sun.com/app/docs/doc/819-5899/gcdta?a=view]. For details, see the [Access Manager Configuration Guide|http://docs.sun.com/app/docs/doc/819-5899]. You can also find installation instructions in this [Access Manager Deployment Example|http://docs.sun.com/app/docs/doc/820-2278/gdssn?a=view].
{info:title=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].{info}
h2. {anchor:productreqs} 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|Communications Suite 6 Update 2 Release Notes].
h4. Messaging Server
* You must ensure DNS is running and configured properly. For details, see [DNS configuration|Communications Suite 6 Update 2 Component Products Release Notes#MessagingRequirements].
* Recommended file systems for the message store are listed in [Message Store File Systems|Communications Suite 6 Update 2 Component Products Release Notes#MessageStoreFileSystems].
* 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|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Calendar Server
* Set up Calendar Server administrator accounts and plan for Calendar Server hosted domains. For details, see [Calendar Server Pre-Installation Considerations|Calendar Server Pre-Installation Planning].
h2. {anchor:installcommssuite} 4. Install Communications Suite 6 Update 2 Products.
After the platform and software requirements have been met (as described previously), take these steps:
# *Download the software.*
To download Communications Suite, including the installer, go to [Get the Software|Get the Software].
# *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|commpkg install Usage]
* [Install in Silent Mode|Installing Communications Suite in Silent Mode]
* [Perform Multiple Installations with Alt Root|Performing Multiple Installations with an Alternate Root]
* [Install on Solaris Zones|Installing Communications Suite on Solaris Zones]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
{info:title=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|Communications Suite 6 Update 2 Installation Scenario - Communications Express#localizedCE].
{info}
h4. {anchor:CIsamplesessions} Sample Sessions: Running commpkg
The following examples document the output of running {{commpkg}}:
* [Sample Session - Communications Suite 6 Update 2 Simple Install and Uninstall].
* [Sample Session - Communications Suite 6 Update 2 Install Using altroot].
* [commpkg upgrade sample session].
h2. {anchor:runcommdssetup}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}}|Communications Suite Directory Server Setup Script (comm_dssetup.pl)]
{info:title=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.
{info}
h2. {anchor:gatherconfiginformation} 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 2 - Configuration Worksheet| Configuration Worksheets - Convergence]
* [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server]
* [Calendar Server 6.3 - Configuration Worksheet|Configuration Worksheets - Calendar Server]
* [Instant Messaging 8 Update 1 - Configuration Worksheet|Configuration Worksheets - Instant Messaging]
* [Delegated Administrator 7 - Configuration Worksheet|Configuration Worksheets - Delegated Administrator]
* [Communications Express 6.3 - Configuration Worksheet|Configuration Worksheets - Communications Express]
h2. {anchor:createinitconfigs} 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.
h6. *Delegated Administrator 7:*
Run the initial configuration program:
{{_INSTALLROOT_/da/sbin/config-commda}}
For detailed instructions, see [Delegated Administrator 7 Initial Configuration].
h6. *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].
h6. *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].
h6. *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].
h6. *Convergence 1 Update 2:*
Run the initial configuration program:
{{_INSTALLROOT_/iwc/sbin/init-config}}
For detailed instructions, see [Convergence 1 Update 2 Initial Configuration].
h6. *Communications Express 6.3:*
Run the initial configuration program:
{{_INSTALLROOT_/ce/sbin/config-uwc}}
For detailed instructions, see [Communications Express 6.3 Initial Configuration].
h6. *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|CommSuite:Configuring Messaging Server for High Availability].
h6. *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)|CommSuite:Configuring Calendar Server Software for High Availability (Failover Service)].
h6. *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|CommSuite:Configuring Instant Messaging for High Availability].
h2. 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|commpkg uninstall Usage]
* [Uninstall in Silent Mode|Uninstalling Communications Suite in Silent Mode]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
h2. Deployment Examples: Installation
To come.
{excerpt:hidden=true}
The following deployment examples show how to install Communications Suite 6 Update 2 in different scenarios. The examples provide step-by-step records of running the installers and configuration programs.
* [Deployment Example: Sun Java Communications Suite 6 Update 2 on a Single Host|Sun Java Communications Suite 6 Update 2 on a Single Host]
* [Deployment Example: Installing Communications Suite 6 on a Solaris Zone|Sample Session - Installing Communications Suite 6 on a Solaris Zone]
* [Deployment Example: Sun Java Communications Suite 6 Update 2 on Multiple Hosts|Sun Java Communications Suite 6 Update 2 on Multiple Hosts]
{excerpt}
h2. 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|commpkg info Usage]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
To determine which version of Application Server you have installed, see [Verify Application Server Version|Verify Application Server Version].
This document contains the following sections:
{toc:minLevel=2|maxLevel=2|location=top|type=list}
See also:
* [Installing Connector for Microsoft Outlook|Connector for Microsoft Outlook 7.3 Update 1 Installation Guide]
h2. 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:
h5. 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.
* For installation instructions for Connector for Microsoft Outlook, see the [Installing Connector for Microsoft Outlook|Connector for Microsoft Outlook 7.3 Update 1 Installation Guide].
* For installation instructions for Communications Sync, see the [Sun Java System Communications Sync 3.0 Release Notes|http://docs.sun.com/app/docs/doc/819-4706].
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:
* If you do not have an existing architecture or design, refer to the [CommSuite:Communications Suite Deployment Planning Guide].
* If you are looking for help with upgrading your current Communications Suite Deployment, refer to [Upgrading to Communications Suite 6 Update 2|Communications Suite 6 Update 2 Upgrade Guide].
* If you are looking for a document to help you install and evaluate the product, refer to
[Deployment Example: Sun Java Communications Suite 6 Update 1 on a Single Host|CommSuite6U1:Sun Java Communications Suite 6 Update 1 on a Single Host] or
[Deployment Example: Installing Communications Suite 6 on a Solaris Zone|Sample Session - Installing Communications Suite 6 on a Solaris Zone]
* If you are planning a multi-host deployment, you can also take advantage of a tool developed by Sun deployment engineering: [EMRA|CommSuite:Enterprise Messaging Reference Architecture Toolkit], a multi-host install and configuration tool. You can also refer to
[Deployment Example: Sun Java Communications Suite 6 on Multiple Hosts|CommSuite6:Sun Java Communications Suite 6 on Multiple Hosts].
* 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.]
h2. {anchor:systemreqs} 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|http://docs.sun.com/app/docs/coll/1236.3], or Red Hat Linux 3 or [4|http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/x8664-multi-install-guide/]. The recommended platform is at least Solaris 10 08/07.
For details, see this list of [operating system and platform requirements|Communications Suite 6 Update 2 Component Products Release Notes#OSPlatform].
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|Communications Suite 6 Update 2 Component Products Release Notes#Memory].
h2. {anchor:installrequiredproducts} 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.
h3. 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.
h5. 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|Communications Suite 6 Update 2 Component Products Release Notes#ProdVerCompatibilityforC6].
For products needed to deploy Convergence, see the [Product Version Compatibility Requirements for Convergence 1 Update 2|Communications Suite 6 Update 2 Component Products Release Notes#convergenceproductreqs].
* Note: The Communications Suite installer _does_ install Message Queue 4.3, Security NSS, and other shared components.
h3. 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:
# *Download the software.*
For links to download sites, go to [Get the Software|Get the Software].
# *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.
{info:title=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.
{info}
Follow the instructions in the [Sun Java System Application Server 9.1 Update 2 Installation Guide|http://docs.sun.com/app/docs/doc/820-3797]. 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|Verify Application Server Version].
# *Install Directory Server 6.3 or later.*
{info:title=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.
{info}
To install Directory Server, follow the instructions in the [Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide|http://docs.sun.com/app/docs/doc/820-2761].
# *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|http://docs.sun.com/app/docs/doc/820-2827].
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|http://docs.sun.com/app/docs/doc/820-1060]
#** Access Manager Server. Either run the JES 5 Update 1 Installer or deploy a single [WAR file|http://docs.sun.com/app/docs/doc/819-5899/gcdta?a=view]. For details, see the [Access Manager Configuration Guide|http://docs.sun.com/app/docs/doc/819-5899]. You can also find installation instructions in this [Access Manager Deployment Example|http://docs.sun.com/app/docs/doc/820-2278/gdssn?a=view].
{info:title=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].{info}
h2. {anchor:productreqs} 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|Communications Suite 6 Update 2 Release Notes].
h4. Messaging Server
* You must ensure DNS is running and configured properly. For details, see [DNS configuration|Communications Suite 6 Update 2 Component Products Release Notes#MessagingRequirements].
* Recommended file systems for the message store are listed in [Message Store File Systems|Communications Suite 6 Update 2 Component Products Release Notes#MessageStoreFileSystems].
* 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|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Calendar Server
* Set up Calendar Server administrator accounts and plan for Calendar Server hosted domains. For details, see [Calendar Server Pre-Installation Considerations|Calendar Server Pre-Installation Planning].
h2. {anchor:installcommssuite} 4. Install Communications Suite 6 Update 2 Products.
After the platform and software requirements have been met (as described previously), take these steps:
# *Download the software.*
To download Communications Suite, including the installer, go to [Get the Software|Get the Software].
# *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|commpkg install Usage]
* [Install in Silent Mode|Installing Communications Suite in Silent Mode]
* [Perform Multiple Installations with Alt Root|Performing Multiple Installations with an Alternate Root]
* [Install on Solaris Zones|Installing Communications Suite on Solaris Zones]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
{info:title=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|Communications Suite 6 Update 2 Installation Scenario - Communications Express#localizedCE].
{info}
h4. {anchor:CIsamplesessions} Sample Sessions: Running commpkg
The following examples document the output of running {{commpkg}}:
* [Sample Session - Communications Suite 6 Update 2 Simple Install and Uninstall].
* [Sample Session - Communications Suite 6 Update 2 Install Using altroot].
* [commpkg upgrade sample session].
h2. {anchor:runcommdssetup}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}}|Communications Suite Directory Server Setup Script (comm_dssetup.pl)]
{info:title=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.
{info}
h2. {anchor:gatherconfiginformation} 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 2 - Configuration Worksheet| Configuration Worksheets - Convergence]
* [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server]
* [Calendar Server 6.3 - Configuration Worksheet|Configuration Worksheets - Calendar Server]
* [Instant Messaging 8 Update 1 - Configuration Worksheet|Configuration Worksheets - Instant Messaging]
* [Delegated Administrator 7 - Configuration Worksheet|Configuration Worksheets - Delegated Administrator]
* [Communications Express 6.3 - Configuration Worksheet|Configuration Worksheets - Communications Express]
h2. {anchor:createinitconfigs} 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.
h6. *Delegated Administrator 7:*
Run the initial configuration program:
{{_INSTALLROOT_/da/sbin/config-commda}}
For detailed instructions, see [Delegated Administrator 7 Initial Configuration].
h6. *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].
h6. *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].
h6. *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].
h6. *Convergence 1 Update 2:*
Run the initial configuration program:
{{_INSTALLROOT_/iwc/sbin/init-config}}
For detailed instructions, see [Convergence 1 Update 2 Initial Configuration].
h6. *Communications Express 6.3:*
Run the initial configuration program:
{{_INSTALLROOT_/ce/sbin/config-uwc}}
For detailed instructions, see [Communications Express 6.3 Initial Configuration].
h6. *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|CommSuite:Configuring Messaging Server for High Availability].
h6. *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)|CommSuite:Configuring Calendar Server Software for High Availability (Failover Service)].
h6. *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|CommSuite:Configuring Instant Messaging for High Availability].
h2. 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|commpkg uninstall Usage]
* [Uninstall in Silent Mode|Uninstalling Communications Suite in Silent Mode]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
h2. Deployment Examples: Installation
To come.
{excerpt:hidden=true}
The following deployment examples show how to install Communications Suite 6 Update 2 in different scenarios. The examples provide step-by-step records of running the installers and configuration programs.
* [Deployment Example: Sun Java Communications Suite 6 Update 2 on a Single Host|Sun Java Communications Suite 6 Update 2 on a Single Host]
* [Deployment Example: Installing Communications Suite 6 on a Solaris Zone|Sample Session - Installing Communications Suite 6 on a Solaris Zone]
* [Deployment Example: Sun Java Communications Suite 6 Update 2 on Multiple Hosts|Sun Java Communications Suite 6 Update 2 on Multiple Hosts]
{excerpt}
h2. 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|commpkg info Usage]
* [Communications Suite Installer: General Syntax and Verbs|commpkg - General Syntax and Commands]
To determine which version of Application Server you have installed, see [Verify Application Server Version|Verify Application Server Version].