This information describes the best practices for upgrading earlier versions of Communications Suite products to version 7. (For a list of those individual product version numbers see Communications Suite 7 Products and Components.)
- About the Communications Suite Upgrade Process
- Defining Your Target Communications Suite Deployment
- Determining the Sequence of Product Upgrades
- Upgrading Messaging Server
- Upgrading Calendar Server in Solaris OS
- Upgrading Instant Messaging Server
- Upgrading Sun Convergence
- Upgrading Delegated Administrator
- Upgrading comm_dssetup.pl
- Upgrading Sync
- Upgrading Outlook Connector
In the information provided here, the term product refers to 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 components refers to software components that are not part of Communications Suite or other support products, but are required for Communications Suite products to operate. Examples include NFS, SASL, and Java.
Communications Suite 7 consists of a number of individual products, product components and shared components, and no single system utility 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 information. Some of these procedures are as simple as adding upgrade patches 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.
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 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:
- 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.
- 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 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 7.
Once you have chosen the scenario that best fits your situation, you know 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, you would type ~1. You can type multiple selections, separating your entries with a comma.
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:
- 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.
To upgrade from Sun Convergence 1 Update 2 to Sun Convergence 1 Update 3, see Upgrading to Convergence 1 Update 3.
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
Using Sun Java System Communications Sync with Communications Suite 7 and Sun Convergence requires Sun Java System Communications Sync Version 3.1. Sync 3.1 is the same as Sync 3.0 but with additional fixes.