Upgrading Offline Mediation Controller

6 Upgrading Offline Mediation Controller

Learn how to upgrade your existing Oracle Communications Offline Mediation Controller cloud native deployment to the latest release.

Topics in this document:

In this document, the Offline Mediation Controller release running on your production system is called the existing release. The release you are upgrading to is called the new release. For example, if you are upgrading from Offline Mediation Controller 12.0 Patch Set 4 to Offline Mediation Controller 15.0, 12.0 Patch Set 4 is the existing release and 15.0 is the new release.

Upgrading Offline Mediation Controller from 12.0 Patch Set 4 or Later to 15.0

When you upgrade your Offline Mediation Controller cloud native services, it upgrades all core services in your Offline Mediation Controller cloud native environment.

To upgrade your Offline Mediation Controller cloud native services from the 12.0 Patch Set 4 or later release to the 15.0 release:

Download the Helm charts for the Offline Mediation Controller cloud native deployment. See "Downloading Packages for the Offline Mediation Controller Cloud Native Helm Charts".
Download the Offline Mediation Controller cloud native images in one of these ways:
- From the Oracle Container Registry. To do so, see "Pulling Offline Mediation Controller Images from the Oracle Container Registry".
- From the Oracle Software Delivery website. To do so, see "Downloading Offline Mediation Controller Images from Oracle Software Delivery Website".
Extract the Offline Mediation Controller Helm chart from the archive:
```
tar xvzf oc-cn-ocomc-15.0.0.x.0.tgz
```
where x is 0 for the 15.0.0.0.0 release, 1 for Offline Mediation Controller 15.0 Patch Set 1, 2 for Offline Mediation Controller 15.0 Patch Set 2, and so on. If you are extracting an interim patch, the file name will also have the interim patch number appended to it, such as oc-cn-ocomc-15.0.0.x.0-12345678.tgz.
Set the following keys in your override-values.yaml file for oc-cn-ocomc:
- charts.enableCore: Set this to true.
- charts.enableRSM: Set this to true if you want to use Offline Mediation Controller REST Services Manager in your 15.0 release.
- ocomcCore.upgrade.fromRelease: Set this to the Offline Mediation Controller release number you are upgrading from. For example, if you are upgrading from 12.0 Patch Set 5, set the key to 12.0.0.5.0.
- ocomcCore.ocomc.configEnv.forceGenSslcert: Set this to true if SSL is enabled in your system.
- Set the other keys in Table 4-2 as needed.
Run the helm upgrade command from the oc-cn-ocomc directory:
```
helm upgrade NameSpace oc-cn-ocomc -values OverrideValuesFile -n ReleaseName
```
where:
- NameSpace is the namespace in which to create Offline Mediation Controller Kubernetes objects.
- OverrideValuesFile is the path to a YAML file that overrides the default configurations in the chart's values.yaml file.
- ReleaseName is the release name, which is used to track this installation instance.
In your override-values.yaml file for oc-cn-ocomc, reset the ocomcCore.ocomc.configEnv.forceGenSslcert key to false.

Note:

If there are config keys present in the sub-charts, or from previous installations during upgrades, which are not found in the new values.yaml file, users can easily add it to the override-values.yaml file.

Upgrading Offline Mediation Controller from 12.0 Patch Set 3 to 15.0

The process for upgrading Offline Mediation Controller cloud native from the 12.0 Patch Set 3 release to the 15.0 release is a two-step process:

Upgrade your Offline Mediation Controller cloud native system from 12.0 Patch Set 3 to 12.0 Patch Set 4.
Upgrade your Offline Mediation Controller cloud native system from 12.0 Patch Set 4 to 15.0 by following the instructions in "Upgrading Offline Mediation Controller from 12.0 Patch Set 4 or Later to 15.0".

To upgrade your Offline Mediation Controller cloud native services to the 12.0 Patch Set 4 release:

Download Oracle Communications Offline Mediation Controller 12.0 Patch Set 4 from the Oracle Support website (https://support.oracle.com).
Unzip the file. The Zip file includes the oc-cn-ocomc-helm-chart-12.0.0.4.0 archive file for upgrading your system.
Extract the Offline Mediation Controller Helm chart from the archive:
```
tar xvzf oc-cn-ocomc-helm-chart-12.0.0.4.0.tgz
```
In admin-server-pvc, rename your 12.0 Patch Set 3 OMC_home/config/adminserver/systemModel.cfg file to SystemModel.orig.
Move your 12.0 Patch Set 3 wallet files from their existing location (vol-keystore PV) to the vol-external PV.
Set the following keys in your 12.0 Patch Set 4 override-values.yaml file:
- ocomcSoftwareUpgradePath: Set this to /container-scripts/OCOMC-12.0.0.4.0_generic_full.jar.
- ocomc.job.preUpgradeToPS4.flag: Set this to true.
- upgrade.fromRelease: Set this to 12.0.0.3.0.
- ocomc.configEnv.forceGenSslcert: Set this to true.
- ocomc.deployment.nodemgr.count: Ensure this is set to 1.
Run the helmUpgradeToPS4.sh script from the oc-cn-ocomc-helm-chart directory:
```
sh helmUpgradeToPS4 NameSpace OverrideValuesFile ReleaseName LogFile
```
where:
- NameSpace is the namespace in which to create Offline Mediation Controller Kubernetes objects.
- OverrideValuesFile is the path to a YAML file that overrides the default configurations in the chart's values.yaml file.
- ReleaseName is the release name, which is used to track this installation instance.
- LogFile is the path and name to the log file to create.
Wait for the admin-server-app pod to start.
Set the following keys in your 12.0 Patch Set 4 override-values.yaml file:
- ocomc.job.preUpgradeToPS4.flag: Set this to false.
- ocomc.job.postUpgradeToPS4.flag: Set this to true.
- ocomc.job.postUpgradeToPS4.existingNM: Set this to the name of the existing Node Manager pod in the format hostname@host:port, where name is the mediation host's name configured in Node Manager, host is the IP address or hostname of the server on which the mediation host resides, and port is the port number at which the mediation host communicates with the Node Manager pod.

Run the helm upgrade command:

helm upgrade ReleaseName oc-cn-ocomc-helm-chart --values OverridingValueFile -n Namespace

Because the wallet location changed in the 12.0 Patch Set 4 release, update all nodes that use the wallet to point to the correct wallet location.
Set the following keys in your override-values.yaml file:
- ocomc.job.postUpgradeToPS4.flag: Set this to false.
- ocomc.configEnv.forceGenSslcert: Set this to false.