Upgrading Convergence

About Upgrading 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.

Supported Upgrade Paths

You can upgrade to the new version of Convergence from 3.0.2.x version.

See "Upgrading from 3.0.2.x to 3.0.3" for more information.

Note:

Convergence deployments can be upgraded from 3.0.2.x.0 to 3.0.3.0.0 using ./commpkg upgrade.
In case of any issue ,use this command ./commpkg --OSversionOverride upgrade.

If you are using a Glassfish deployment, Oracle recommends you to migrate to Weblogic, using the steps provided in "Migrating Convergence Deployment from GlassFish Server to Oracle WebLogic Server".

Planning Your Convergence Upgrade

Depending on the components affected by the upgrade, your upgrade team may include the following:

A system administrator, to manage any changes to Oracle WebLogic 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 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.

Testing the Upgrade in a Test Environment

Oracle recommends running the upgrade procedure on a test system that models your production environment. 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

Upgrade Impacts

This section explains any important system changes introduced in the new release of Convergence.

This section does not describe new features or functionality. See Convergence Release Notes for information about new features.

Upgrade Impacts from Version 3.0.2.x to 3.0.3.0.0

Upgrading to the new version of Convergence includes the following system changes:

Java Development Kit Changes

The new version of Convergence requires an updated version of the Java Development Kit (JDK) on the Convergence server. See "System Requirements" for more information. Upgrade Java before upgrading Convergence.

Directory Server Schema Changes

The new version of Convergence requires an updated version of the directory server schema.

Unified Communications Suite Software Compatibility Changes

The new version of Convergence may be compatible with a few older versions of other Unified Communications Suite software. However, it is recommended to upgrade the other Unified Communications Suite software to the latest version to use with this release of Convergence. See "Software Requirements" for more information.

Upgrading from 3.0.2.x to 3.0.3

To upgrade to the new release of Convergence, complete the following:

Pre-Upgrade Tasks (3.0.2.x to 3.0.3)

Before upgrading Convergence, do the following:

Install or upgrade the following software:
- Upgrade the JDK
- (Optional) Install Oracle Access Manager
- Install OpenLDAP client or Install Directory Server based LDAP client, if your operating system does not provide it by default
Determine whether you need to update the directory server schema version.

See "Preparing the Directory Server" for more information.
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:

https://edelivery.oracle.com/

The Convergence software is included in the Oracle Communications Messaging Server and Oracle Communications Calendar Server software package.
Extract the Convergence software to dir.

Upgrading Convergence (3.0.2.1.0 to 3.0.3.x)

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 Application Server is running.
Verify that the directory server is running.
Verify that all the Unified Communications Suite software with which you intend to integrate Convergence is running.
Make sure that the JAVA_HOME variable is set to JDK_location in the current shell or in GlassFish Server user profile.
From dir, run the upgrade installer:
```
./commpkg upgrade
```
See "commpkg Reference" for more information about the commpkg command.
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 weblogic Admin Server and Weblogic Managed Server domain on which Convergence is deployed.

Post-Upgrade Tasks (3.0.2.x to 3.0.3)

After the Convergence upgrade has completed successfully, do 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.

Migrating Convergence Deployment from GlassFish Server to Oracle WebLogic Server

Prerequisites for migrating Convergence from GlassFish Server to Oracle WebLogic Server are:

A previous version of Convergence is installed on GlassfFish 3 or GlassFish 5.
You must have installed Oracle WebLogic Server 12.2.1.4.

To migrate Convergence deployment from GlassFish Server to Oracle WebLogic Server:

Back up the configuration c11n folder and output of iwcadmin -1 command.
Backup the latest savestate file from Convergence_Home/data/setup/Iwc-config-YYYYMMDDHHMMSS directory.
Install the latest version of Convergence using commpkg tool.
Start Oracle WebLogic Admin Server and Managed Server.
Make sure all the backend servers are up and running.
Configure Convergence using Webogic as application server. Refer to the SaveState file from step 2, for backend and other details.
Make sure Convergence configuration is successful.
Copy the backed up c11n folder to the configured Document Root Directory, data_directory/web-src/client/iwc_static.
Update the missing required configurations on Oracle WebLogic Deployment by comparing the output of iwcadmin -l command in GlassFish and Oracle WebLogic deployments.
Copy the required configuration files from the backed up configuration folder to the new configuration folder. For example, advertising.json.
Restart the Managed Server and Login to Convergence to verify that everything is working as expected. For example,you can login to Convergence and access the configured services.