Upgrading IBM Workflow Process Service Runtime on Red Hat OpenShift from 22.0.1

If you installed IBM Workflow Process Service Runtime 22.0.1 on Red Hat OpenShift, you can upgrade to IBM Workflow Process Service Runtime 22.0.2 on Red Hat OpenShift.

Before you begin

If you saved federated searches that are stored in the Elasticsearch index, you must migrate your saved searches before upgrading. Otherwise, your saved searches will be lost.
Back up your data and take snapshots. You need this data to roll back after you upgrade. For more information, see Backing up your environments.

The following diagram highlights the components that are always installed when you install IBM Workflow Process Service Runtime, along with the optional components. If you are upgrading IBM Workflow Process Service Runtime in your custom resource (CR), then make sure that you update all the relevant versions for all of the capabilities that are in your CR file.

Workflow Process Service capability diagram

To upgrade Workflow Process Service, complete the following steps.

Procedure

Update your dependencies to the newest supported versions. For more information, see Upgrading dependencies.
Upgrade the operator before you update the custom resource. To prevent connection problems during the upgrade, make sure to update your passwords for your database and LDAP that are close to expiring. When you upgrade from any version, you can upgrade the operator and keep the container image tags from the previous version. Upgrade your operator by following the steps in Upgrading a non-air gapped environment.
Open the custom resource YAML file that you used to install IBM Cloud Pak® for Business Automation.
1. Update the metadata.labels.release parameter value to the new version.
2. Update the appVersion parameter value in the spec section to the new version.
Apply and verify the upgraded CR.

Increase the pod startup time. When upgrading to 22.0.2, the pod requires more time to complete the commands for upgrading. Run the following commands, replacing <WfPS_CR_Name> with your Workflow Process Service instance name:

oc patch wfps <WfPS_CR_Name> --type='json' -p '[{ "op": "replace", "path": "/spec/node/probe/startupProbe/failureThreshold", "value": 800 }]' 
oc patch wfps <WfPS_CR_Name> --type='json' -p '[{ "op": "replace", "path": "/spec/node/probe/startupProbe/periodSeconds", "value": 10 }]'

Open the custom resource YAML file that you used to install Workflow Process Service. Change the spec.appVersion parameter value in the spec section to the new version. Apply the changed custom resource YAML file.
Verify your Workflow Process Service deployment.
1. Verify the configuration of your applications and the status of your pods by running the following command:
```
oc get pods -w
```
2. Verify the instance details in the custom resource status fields of the components by running the following command:
```
oc get wfps <instance_name> -o yaml
```
3. Verify your upgrade to 22.0.2 by running the following command:
```
oc get statefulset <instance_name>-wfps-runtime-server -o yaml
```
  Make sure that the value of cloudpakVersion is 22.0.2.
4. Make sure that you can access the Workplace console. For more information on how to get the console URL and other verification, see "Verifying your Workflow Process Service deployment" in Installing Workflow Process Service Runtime deployments.
  If you are unable to access the Workplace URL or the Workplace page is blank, run the following command. Replace <WfPS_Instance_Name> with your Workflow Process Service instance name.
```
oc exec -it <WfPS_Instance_Name>-wfps-runtime-server-0 -- /bin/bash -c "/opt/ibm/wlp/ibmProcessServer/bin/updateSystemApp defaultServer"
```