This chapter explains how to upgrade Oracle Communications Convergence.
This chapter does not explain how to install patches on Convergence.
In this chapter, the release from which you are upgrading is called the old release, and the release to which you are upgrading is called the new release.
Upgrading to a new release of Convergence consists of the following tasks:
Planning the upgrade
Reviewing the upgrade impacts
Performing the pre-upgrade tasks
Upgrading Convergence
Performing the post-upgrade tasks
Before upgrading a production environment, you should first test the upgrade in a test environment. See "Testing the Upgrade in a Test Environment" for more information.
You can upgrade to the new version of Convergence from the following old versions:
From release 3.0.0, 3.0.0.1, or 3.0.0.2
See "Upgrading from 3.0.0 to 3.0.1" for more information.
Depending on the components affected by the upgrade, your upgrade team may include the following:
A system administrator, to manage any changes to Oracle GlassFish Server and to upgrade other Oracle Communications software.
A UNIX administrator, to manage accounts, network setup, and IP configurations.
Identify who might be affected by the upgrade. For example:
You might need to give your system administrators and users notice of any system downtime.
Tell your system administrator in advance about any changes to the system architecture.
Train your administrators, users, and developers on new functionality introduced by the upgrade that has an impact on their role.
You might need to make changes to your system after the upgrade is complete to accommodate new or modified features or functionality. For example, if the new release provides new security functionality, additional system configuration steps may be required. See "Upgrade Impacts" for more information.
The best way to estimate the duration of an upgrade is to perform it on a test system with a copy of the production data. See "Testing the Upgrade in a Test Environment" for more information.
Oracle recommends scheduling your upgrade during non-peak hours to minimize the disruption to your operations.
Oracle recommends running the upgrade procedure on a test system that models your production system. Test the upgrade by doing the following:
Successfully completing all the pre-upgrade, upgrade, and post-upgrade tasks.
Comparing the default behavior between the old and the new releases.
Test that your customizations are preserved. Recreate any custom configurations and customizations that could not be upgraded.
Confirming that all new behavior and functionality works.
Restarting the Convergence server.
Log into Convergence and verify its version number
This section explains any important system changes introduced by an upgrade.
New features and new functionality are described in Convergence Release Notes.
Upgrading to this version of Convergence requires the following system changes:
The new version of Convergence requires an updated version of the Java Development Kit (JDK) on the Convergence server. See "Software Requirements" for more information.
Upgrade Java before upgrading Convergence.
The new version of Convergence may be compatible with new versions of other Unified Communications Suite software, which you may want or need to upgrade. See "Software Requirements" for more information.
Also, the new version of Convergence can integrate with Oracle Communications Contacts Server to deliver the address book service. Contacts Server is an optional component. If you choose to integrate Convergence with Contacts Server, you must migrate users' address book data after the upgrade is complete. See "Post-Upgrade Tasks (3.0.0 to 3.0.1)" for more information.
Convergence no longer supports Access Manager. Instead, access management is provided by Oracle Access Manager.
Oracle Access Manager is an optional component. If you decide to use Oracle Access Manager as part of your Convergence deployment, install it and set it up before upgrading Convergence.
You can integrate this release of Convergence with Oracle Enterprise Manager to gain enhanced and cloud-based monitoring functionality.
Enterprise Manager is an optional component. If you decide to use Enterprise Manager as part of your Convergence deployment, install it and set it up before upgrading Convergence.
To upgrade to the new release of Convergence, you must complete the following:
Before upgrading Convergence, do the following:
Install or upgrade the following software:
Upgrade the JDK
(Optional) Install Oracle Access Manager
(Optional) Install Oracle Enterprise Manager
Upgrade or install all required and optional Unified Communications Suite software needed to deliver your existing and planned Convergence services. For example, if you are integrating Convergence with Contacts Server to deliver the address book service, install Contacts Server. If you decide to upgrade to a new version of Oracle Communications Messaging Server, upgrade Messaging Server.
Refer to your application installation documentation for upgrade and installation instructions.
Create a directory (dir) on each Convergence host system.
Download the Convergence software for your operating system from the Oracle software delivery web site:
The Convergence software is included in the Oracle Communications Messaging Server or Oracle Communications Calendar Server media pack.
Extract the Convergence software to a temporary directory (dir).
You use the commpkg upgrade command to upgrade to the new version of Convergence. The commpkg upgrade command upgrades Convergence with an in-place package replacement that cannot be reversed.
To upgrade Convergence on each Convergence host system:
Verify that the GlassFish server is running.
Verify that the directory server is running.
Verify that Oracle Communications Messaging Server, Oracle Communications Calendar Server, and any other Unified Communications Suite software with which you intend to integrate Convergence is running.
From dir, run the upgrade installer:
./commpkg upgrade
See the discussion about the commpkg upgrade command and syntax on the Oracle wiki for more information:
From the list of available Communications Products for upgrade, select Convergence and proceed with the upgrade.
When the installer has completed the upgrade, restart the GlassFish server domain on which Convergence is deployed:
asadmin restart-domain Convergence_Domain
After the Convergence upgrade has completed successfully, do any of the following that apply to you:
Configure Convergence to work with newly installed Unified Communications Suite software. For example, if, as part of this upgrade, you are integrating Convergence with Contacts Server for the first time, you need to configure Convergence to communicate with Contacts Server.
See "Configuring Convergence" for more information.
If, as part of this upgrade, you are integrating Convergence with Contacts Server to provide the address book service, you must migrate users' personal address book data to Contacts Server.
See the discussion about migrating information to Contacts Server in Contacts Server System Administrator's Guide for more information.