Communications Suite Upgrade Guide

Skip to end of metadata
Go to start of metadata
For the most current documentation, see Communications Suite 7 Update 5 Wiki.

Oracle Communications Unified Communications Suite Upgrade Guide
Version 7 Update 1

This information describes the best practices for upgrading prior versions of Communications Suite (formerly known as Sun Java Communications Suite) to Oracle Communications Unified Communications Suite. (For a list of those individual product version numbers see Oracle Communications Unified Communications Suite Products and Components.)


About This Information

In this information, the terms products, product components, and shared components are used. Products are items such as Messaging Server, Calendar Server, Delegated Administrator, and Instant Messaging Server. Product components are functional parts of the products. For example, Messaging Server has message stores, relays, and messaging multiplexors. Calendar Server has front-end and back-end servers. Shared resources are software components that are not part of Communications Suite or other support products, but are required for Communications Suite products to operate. Examples include Network File System (NFS), Simple Authentication and Security Layer (SASL), and Java software.

About the Communications Suite Upgrade Process

Communications Suite consists of a number of individual products, product components, and shared resources. Unfortunately, Communications Suite does not provide a single system utility to upgrade all Communications Suite components at the same time. Therefore, upgrading a Communications Suite deployment consists of upgrading one component at a time and one computer at a time, by using the component-specific upgrade procedures described in the following sections. Some upgrade procedures are simple, such as applying a patch to the existing software. Other procedures are more complex and require considerably more planning and preparation. Proper upgrading starts with knowing what products you want to upgrade and the order in which to upgrade them.

Defining Your Target Communications Suite Deployment

A successful upgrade depends on identifying both your current deployment and your target deployment. By defining your target deployment, you identify which products and components you need to upgrade and which ones can remain as is.

The three most common Communications Suite upgrade scenarios include:

  • Upgrade for a product feature. You want a feature from a specific product and you are only interested in upgrading the products and components that are necessary to support that feature.

    In this scenario, you upgrade the desired product as described in the upgrade information for that product.
  • Upgrade all products and components to the latest release. You want to run the latest versions of all Communications Suite products and components.

    Upgrade each product and component individually, host by host. See Requirements for Communications Suite.

When you have chosen the scenario that best fits your situation, you can determine what products to upgrade.

Installing only shared components: To install just the shared components for a component product, launch the Communications Suite installer, then prefix your product selection with a tilde (~). For example, to install only the shared components for Messaging Server 64-bit, at the Product Selection prompt, type ~1. You can type multiple selections, separating each of your entries with a comma.

Determining the Sequence of Product Upgrades

The order in which you update the Communications Suite products and versions can be critical. Use the following guidelines to determine the sequence for upgrading Communications Suite products:

  • To upgrade a pre-6.3 Messaging Server, first you must upgrade the message store components to version 6.3 or later, then you can upgrade the webmail server (previously called MEM) to version 6.3 or later.

The following sections describe how to upgrade each of the Communications Suite products.

Upgrading Messaging Server

See Messaging Server Upgrade.

Upgrading Messaging Server in a High Availability (HA) Environment

See Upgrading to Messaging Server in an HA Environment.

Upgrading Calendar Server for CALDAV Clients (Calendar Server 7)

See Upgrading Calendar Server for CALDAV Clients (Calendar Server 7).

Upgrading Calendar Server in Solaris OS

See Calendar Server 6.3 Upgrade.

Upgrading Calendar Server in a High Availability (HA) Environment

See Upgrading Calendar Server 6.3 in an HA Environment.

Upgrading Instant Messaging Server

See Instant Messaging Upgrade.

Upgrading the Instant Messaging Server in a High Availability (HA) Environment

See Upgrading to Instant Messaging in an HA Environment.

Upgrading Convergence

To upgrade from Sun Convergence 1 Update 3 to Convergence 2, see Upgrading Convergence.

Upgrading Indexing and Search Service

See Upgrading Indexing and Search Service.

Upgrading Delegated Administrator for Oracle Communications Unified Communications Suite

See Delegated Administrator Upgrade.


Run the latest version of to prepare the schema, index, and data in your Directory Server to work with Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, or any products that depend on the Directory Server.

Run commpkg upgrade to upgrade, and then run perl For upgrade details, see commpkg upgrade Usage.

Upgrading Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite

See Connector for Microsoft Outlook Upgrade Guide.

commsuite commsuite Delete
guide guide Delete
upgrading upgrading 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.