Communications Suite Installation Guide

Skip to end of metadata
Go to start of metadata

Oracle Communications Unified Communications Suite Installation Guide
Version 7 Update 1

The following information is intended for any evaluator, system administrator, or software technician who wants to install any portion of the Communications Suite software.

Topics:

See also:

Oracle Communications Unified Communications Suite Installation Overview

This information describes how to install specific Communications Suite products on a specific machine (a machine can mean either a computer or a Solaris Zone). It describes the product installation tasks required for new deployments and upgrades. The following table shows the products that are available in the installer software.

Oracle Communications Unified Communications Suite Products and Components
Version 7 Update 1
Product Version
Oracle Communications Messaging Exchange Server 7 Update 4
Oracle Communications Instant Messaging Server 8 Update 3
Convergence 2
Oracle Communications Calendar Server for CALDAV Clients 7 Update 1
Delegated Administrator for Oracle Communications Unified Communications Suite 7 (latest patch)
Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite 7.3 Update 1 (latest patch)
Oracle Communications Calendar Server 6.3 (latest patch)
Indexing and Search Service for Oracle Communications Unified Communications Suite 1 Update 1
Sun Java System Communications Sync Removed
Messaging Server HA Agent (MS_SCHA) 7
Calendar Server HA Agent (CS_SCHA) 6.3
Instant Messaging HA Agent (IM_SCHA) 7.3
Dssetup for Oracle Communications Unified Communications Suite (comm_dssetup) 6.4 (latest patch)

The Communications Suite installer does not install Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite, although the product is included with the distribution.

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

This information assumes that you have already made your architectural and design decisions and that you know 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, or if you do not have an existing architecture or design, refer to Communications Suite Deployment Planning Guide.

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

Evaluating Communications Suite

To help you install and evaluate the product, see the following information:

Communications Suite Multi-host Deployment

If you are planning a multi-host deployment, you may appreciate the features available in the Enterprise Messaging Reference Architecture (EMRA) Toolkit, 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 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 Java System products that support Communications Suite
  • Directs you to specific sets of installation instructions based on your decisions

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

Installing Communications Suite

The information in this section describes the steps to install Communications Suite products. These steps provide a high-level process flow for installing any or all of the Communications Suite products.

1. Check that your platform and operating system support Communications Suite.

Recommended platforms for Oracle Communications Unified Communications Suite are:

Operating System CPU Comments
Solaris OS 10 SPARC, x64 Minimum recommended version: Solaris OS 10 10/09 (Update 9)
See the Solaris 10 10/09 Release and Installation documentation for more information.
Red Hat Linux 5.3 Update 3 64-bit x64 See the Red Hat Enterprise Linux documentation for more information.

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

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

Note
The following products require that you have Java 1.6 installed: Sun GlassFish Enterprise Server 2.1.1, Calendar Server 7 Update 1, Indexing and Search Service 1 Update 1, and Instant Messaging 8 Update 3.

2. Install the Non-Communications Suite Products required to run Communications Suite.

Which products are required to support the Communications Suite products?

The Product Version Compatibility Requirements for Communications Suite 7 Update 1 table lists the products and versions that are compatible with the Communications Suite 7 Update 1 products.

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

Note
GlassFish Message Queue 4.4 Update 1 is a shared component to the Communications Suite installer and is only installed when you install a dependent product, such as Messaging Server or Indexing and Search Service. It does not explicitly appear in the list of items to install, upgrade, or uninstall in the Communications Suite installer. The Communications Suite installer also installs Network Security Services (NSS) and other shared components.

How Do You Install the Non-Communications Suite Products?

The Communications Suite installer does not install software products that are not included with the Communications Suite software. To install these additional products, perform the following steps:

  1. Download the software.
    For links to download sites, go to Get the Software.
  2. Install GlassFish Server 2.1.1 with High-Availability Database (HADB) software by using the instructions in Installation Scenario - GlassFish Server.
  3. Install Directory Server 7 by using the instructions in Installation Scenario - Directory Server.
  4. Install the following optional products by running the Java ES 5 Update 1 installer:
    • Access Manager 7.1: Delegated Administrator 7 no longer requires Access Manager. Only install Access Manager if you are using it for particular features of Instant Messaging Server.
    • Web Server 7.0: In general, you should use GlassFish instead of Web Server.

To install Access Manager or Web Server, follow the instructions in the Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Here are other information sources and methods for installing these products:

3. Define and set up additional requirements for individual Communications Suite products.

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

Messaging Server 7 Update 4

  • You must ensure that Domain Name System (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 that you do not configure conflicting port numbers 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 Update 1

Install the Oracle Communications Calendar Server for CALDAV Clients back-end database first. Then, install and configure the Oracle Communications Calendar Server for CALDAV Clients front end.

Calendar Server 6.3

As of Communications Suite 7, Oracle Calendar Calendar Server 6.3 (formerly Sun Java System Calendar Server 6.3) has been deprecated.
If you are not using Convergence 1, you should no longer be installing Calendar Server 6.3. Instead, install Oracle Communications Calendar Server for CALDAV Clients, which is supported by Convergence 2.

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

4. Install Communications Suite products.

After you have complied with the previous platform and software requirements, complete 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. The commpkg utility does all the necessary preparation work before installing the product software on the system. As root, run the following command:
    ./commpkg install

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

Sample Sessions: Running commpkg

The following examples document output from 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:

For details, see Communications Suite Directory Server Setup Script (comm_dssetup.pl).

Note
If you install or upgrade Directory Server before you run the Communications Suite installer, the Directory Server installation process might place a previous 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, if a previous version of comm_dssetup.pl is installed then the Communications 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.

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 customizing the configuration.

You should usually configure the back-end servers before configuring clients. Client configurations require that certain server attributes be defined.

Delegated Administrator 7

Run the initial configuration program:

INSTALLROOT/da/sbin/config-commda

For detailed instructions, see Delegated Administrator Initial Configuration.

Messaging Server 7 Update 4

Run the initial configuration program:

INSTALLROOT/messaging64/bin/configure

For detailed instructions, see Messaging Server Initial Configuration.

Calendar Server 7 Update 1

Run the initial configuration program:

INSTALLROOT/sbin/init-config

For detailed instructions, see Oracle Communications Calendar Server for CALDAV Clients Initial Configuration.

Sun Java System 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 Oracle Communications Calendar Server Initial Configuration.

Indexing and Search Service 1 Update 2

Run the initial configuration program:

INSTALLROOT/bin/setup

For detailed instructions, see Indexing and Search Service Initial Configuration. As of Indexing and Search Service 1 Update 2, the setup.sh configuration program was renamed to simply setup.

Instant Messaging 8 Update 3

Run the initial configuration program:

INSTALLROOT/im/sbin/configure

For detailed instructions, see Instant Messaging Initial Configuration.

Convergence 2

Run the initial configuration program:

INSTALLROOT/iwc/sbin/init-config

For detailed instructions, see Convergence 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 high availability (HA) agent with the Sun Cluster HA software. You must have the Sun Cluster HA software installed before you issue 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 that are installed on the local machine, run the following commands:

cd <INSTALLROOT>/CommsInstaller/bin 
./commpkg uninstall

For detailed instructions, see the following information:

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

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

To determine which version of GlassFish Server you have installed, see Verifying the GlassFish Server Version.

Labels:
installing installing Delete
commsuite commsuite Delete
guide guide Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

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.