Communications Suite 6 Update 2 Upgrade Guide

Skip to end of metadata
Go to start of metadata

Sun Java Communications Suite 6 Update 2 Upgrade Guide

This document describes the best practices for upgrading earlier versions of Communications Suite products to version 6 Update 2. (For a list of those individual product version numbers see Communications Suite 6 Update 2 Release Notes.) In this guide, 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 the Communications Suite or other support products, but are required for Communications Suite products to operate. Examples include NFS, SASL, and Java.

Communications Suite 6 Update 2 consists of a number of individual products, product components and shared resources, and there is no single system utility that upgrades all Communications Suite components at once. Upgrading a Communications Suite deployment consists of upgrading component-by-component and computer-by-computer, using the component-specific upgrade procedures described in this document. Some of these procedures are as simple as adding upgrade patches to the existing software. Other procedures require considerably more planning, preparation, and complexity. Proper upgrading starts with knowing what products you want to upgrade and the order in which to upgrade them.

This page contains the following sections:

Define Your Target Deployment

A successful upgrade depends on knowing where you are (your current deployment) and where you are going (your target deployment). By defining your target deployment, you will know what products and components you need to upgrade and which ones can remain as is.

The three most common Communications Suite upgrade scenarios are:

  1. Upgrade for a Product Feature. There is a specific feature you want from a specific product and you are only interested in upgrading the products and components necessary to support that feature.

    In this scenario, you simply upgrade the desired product. See the product-specific upgrade section(s)on this page.

  2. Upgrade to use Sun Convergence. You only want to upgrade the products and components necessary to use Sun Convergence.

    The minimum product versions that can still run Convergence are listed in Product Version Compatibility Requirements for Convergence 1 Update 2.

  3. You want to upgrade all products and components to the latest release.

    You upgrade each product individually, host-by-host. See Requirements for Communications Suite 6 Update 2.

Once you have chosen the scenario that best fits your situation, you will know what products to upgrade.

Tip
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 32-bit, at the Product Selection prompt, you would type ~1. You can type multiple selections, using a comma to separate your entries.

Determine the Sequence of Product Upgrades

The order in which the Communications Suite product and versions are upgraded can be critical. Use the following guidelines to determine the upgrade sequence for Communications Suite products:

  • If you are upgrading Communications Express from a version earlier than 6.3, then you must upgrade to Messaging Server 6.3 or later first.
  • For upgrading a pre-6.3 Messaging Server you must upgrade the messages store components to 6.3 or later before upgrading the webmail server (previously called MEM) to 6.3 or later.

The rest of this guide describes how to upgrade each of the Communications Suite products.

Upgrading Messaging Server

See Messaging Server 7 Update 2 Upgrade.

Upgrading Messaging Server in an HA (High Availability) Environment

See Upgrading to Messaging Server 7 Update 2 in an HA Environment.

Upgrading Calendar Server in the Solaris OS

See Calendar Server 6.3 Upgrade.

Upgrading the Calendar Server in an HA (High Availability) Environment

See Upgrading Calendar Server 6.3 in an HA Environment.

Upgrading Instant Messaging Server

See Instant Messaging 8 Update 1 Upgrade.

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

See Upgrading to Instant Messaging 8 Update 1 in an HA Environment

Upgrading Sun Convergence

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

Upgrading Delegated Administrator

See Delegated Administrator 7 Upgrade.

Upgrading comm_dssetup.pl

It is important to run the latest version of comm_dssetup.pl 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 comm_dssetup.pl and then run perl comm_dssetup.pl. For upgrade details see commpkg upgrade Usage

Upgrading Communications Express

See Communications Express 6.3 Upgrade.

Upgrading Sync

Using Sun Java System Communications Sync with Communications Suite 6 Update 1 and Sun Convergence requires the following:

  1. Sun Java System Communications Sync Version 3.1. Note that Sync 3.1 is the same as 3.0 with additional fixes.
  2. Installation or upgrade to Communications Express 6.3. (See Communications Express 6.3 Upgrade or the Sun Java Communications Suite 6 Update 2 Installation Guide.)

Upgrading Outlook Connector

See Connector for Microsoft Outlook 7.3 Update 1 Upgrade Guide.

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

    It would be useful to have a matrix of certified (QA tested) & supported (not tested but theoretically possible) combinations & not-supported (known to not work) of products & configurations. This will help address the common support questions that occur after the introduction of new products e.g. can I use directory server 5 with messaging server 6.3? Do I need to upgrade to Schema 2? Can I use legacy/realm Access Manager configuration with Instant Messenger?

    This is especially true now that components such as directory server/web server/access manager etc. are no longer bundled with the installer.

    So for messaging server 7 for example, you can use any Sun directory server that is supported by the comm_dssetup.pl utility (as this is a pre-requisite). comm_dssetup.pl works with 5.2 and 6.0/6.1/6.2, but we don't test against 5.2 anymore so this is not a certified combination. On the other hand another 3rd party directory e.g. openldap is not-supported.

    Need information on how to migrate customisations with updated versions e.g. Delegated Administrator interface customisations will need to be reapplied manually, UWC customisations are kept as part of the patch-config/install-newconfig steps.

    backout strategies - this is especially important for messaging server store data which is being fundamentally changed in MS7.0 due to the large mailbox store.* related changes.

  2. Jul 02, 2008

    How about this section for a requirements/compatibility matrix .

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.