This information describes the best practices for upgrading prior versions of Oracle Communications Unified Communications Suite (formerly known as Sun Java Communications Suite). For a list of those individual product version numbers see Oracle Communications Unified Communications Suite Products and Components.
- About This Information
- About the Communications Suite Upgrade Process
- Defining Your Target Communications Suite Deployment
- Determining the Sequence of Product Upgrades
- Preparing to Upgrade
- Upgrading Messaging Server
- Upgrading Calendar Server (Calendar Server 7)
- Upgrading Instant Messaging Server
- Upgrading Convergence
- Upgrading Indexing and Search Service
- Upgrading Delegated Administrator for Oracle Communications Unified Communications Suite
- Upgrading comm_dssetup.pl
- Upgrading Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite
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.
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.
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 to use Convergence. You only want to upgrade the products and components that are necessary to use Convergence.
See Product Version Compatibility Requirements for Convergence 2 for the minimum versions of products that run Convergence.
- 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.
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 Messaging Server prior to version 6.3, first you must upgrade the message store components to version 6.3 or later, then you can upgrade the webmail server (previously called Messenger Express Multiplexor, or MEM) to version 6.3 or later.
The following sections describe how to upgrade each of the Communications Suite products.
Before starting an upgrade, it is good practice to make a backup copy of customized files and configuration files. In particular, the following files should be backed up:
Instant Messaging: /opt/sun/comms/im/config/iim.conf
To upgrade from Convergence 2 to Convergence 2 Patch 2, see Upgrading Convergence.
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. See: DSsetup Patches By Release.
If you are running DSsetup 6.4 Patch 24, refer to the DSsetup 6.4-24 Sample Session - Upgrade.
Run commpkg upgrade to upgrade comm_dssetup.pl, and then run perl comm_dssetup.pl. For upgrade details, see commpkg upgrade Usage.