Upgrading your instances
After upgrading from an earlier to the latest Long Term Support (LTS) version of IBM® App Connect Operator 5.0.x, follow these instructions if you need to manually upgrade your existing App Connect Dashboard, App Connect Designer, switch server, and integration server instances. You can generally upgrade by using the Red Hat® OpenShift® web console or CLI, or from the IBM Cloud Pak Platform UI in your IBM Cloud Pak for Integration deployment.
Before you begin
- Ensure that you have cluster administrator authority or have been granted the appropriate role-based access control (RBAC).
- Ensure that your Operator has been upgraded, as described in Upgrading from an earlier to a later 5.0.x version of the IBM App Connect Operator.
- Review the Upgrade considerations for channels, versions, and licenses.
Close any existing App Connect Dashboard or App Connect Designer instance that is currently open in your browser before you attempt this upgrade.
If an existing instance is currently open in a browser during an upgrade to the latest (fully qualified) operand version, you might observe an error when you try to refresh the Dashboard or Designer page in the browser. As a workaround, reload the Dashboard or Designer instance by using the URL that is presented in the custom resource (CR).
About this task
If you want to apply custom resources from the latest Operator version to your existing instances of the App Connect Dashboard, App Connect Designer, switch server, and integration server, update the version and license settings as follows to allow the upgrade to proceed:
- Ensure that the spec.version value is set to subscribe to the
12.0-lts
or12.0.12-lts
custom resource channel, or is set to a fully qualified version of12.0.12.2-rX-lts
.Note: If you are upgrading to IBM App Connect Operator 5.0.4 or later, the Red Hat OpenShift version that you upgrade to determines which channels or versions are supported for your App Connect Dashboard, App Connect Designer, switch server, and integration server instances. For more information, see Implications for the installed Red Hat OpenShift version. - Update the spec.license.licence value to an appropriate licence for the Operator version.
Unable to load integrationservers from the cluster: ...
App Connect Designer instances at version 12.0.12.0-r1-lts or later do not require a flowdocAuthoring container so when you upgrade from 12.0.11.3-r1-lts or earlier, the flowdocAuthoring pod is removed while the new ui pod starts up. During the upgrade, any flows in your Designer instance might not be visible until the ui pod is fully started.
You can upgrade any of your existing App Connect Dashboard, App Connect Designer, integration server, and switch server instances by using the Red Hat OpenShift web console or CLI. You can also upgrade integration servers directly from the App Connect Dashboard. From the IBM Cloud Pak Platform UI, you can directly upgrade only App Connect Dashboard and App Connect Designer instances.
After you upgrade your instances, ensure that Red Hat OpenShift is upgraded to a supported version in your cluster. For more information, see Upgrading your cluster to Red Hat OpenShift Container Platform 4.12 or 4.14.
- Upgrading your instances from the Red Hat OpenShift CLI
- Upgrading your instances from the Red Hat OpenShift web console
- Upgrading the Dashboard or Designer from the IBM Cloud Pak Platform UI
- Upgrading integration servers directly from the App Connect Dashboard
- Useful commands for checking or verifying your versions and license values
Upgrading your instances from the Red Hat OpenShift CLI
Procedure
To upgrade your instances, complete the following steps:
Upgrading your instances from the Red Hat OpenShift web console
Procedure
To upgrade your instances, complete the following steps:
Upgrading the Dashboard or Designer from the IBM Cloud Pak Platform UI
Procedure
To upgrade your App Connect Dashboard and App Connect Designer instances, complete the following steps:
Upgrading integration servers directly from the App Connect Dashboard
From your App Connect Dashboard instance, you can change the
versions of your integration servers from the options menu on the tile if required. This
capability provides a way for you to upgrade your integration servers after the IBM App Connect Operator has been upgraded.
For more information, see Changing the version of a deployed integration server.
Useful commands for checking or verifying your versions and license values
Use these commands to check your versions and license values if required before upgrading, or to verify that your intended values have been applied after the upgrade.
Example
In these commands, the value of kind can be any of:
Dashboard
, DesignerAuthoring
, SwitchServer
, or
IntegrationServer
. (These values are not case sensitive.) The
instanceName variable denotes the name of the instance that is specified as the
metadata.name value.
If necessary, include the -n namespace
setting.
- This command lists existing instances of a specific kind and shows which App Connect versions are running.
The output displays the running App Connect versions in the
RESOLVEDVERSION
column.oc get kind
Examples:
oc get IntegrationServer NAME RESOLVEDVERSION REPLICAS AVAILABLEREPLICAS CUSTOMIMAGES STATUS AGE is-01-quickstart 12.0.6.0-r1-lts 1 1 false Ready 8d des-ma-johndoe-designer 12.0.6.0-r1-lts 1 1 false Ready 5d4h des-leemajor-designer 12.0.6.0-r1-lts 1 1 false Ready 2d1h designer-josie-designer 12.0.6.0-r1-lts 1 1 false Ready 7d3h baton-test-upgrade-server 12.0.5.0-r1-lts 1 1 false Ready 20d
oc get dashboard NAME RESOLVEDVERSION REPLICAS CUSTOMIMAGES STATUS URL AGE db-01-quickstart 12.0.6.0-r1-lts 1 false Ready https://cpd-cp4i.apps.acecc-lts.acme.com/integration/run/integrations/ace-fiona/db-01-quickstart/ 5d7h db-02-quickstart 12.0.6.0-r1-lts 1 false Ready https://cpd-cp4i.apps.acecc-lts.acme.com/integration/run/integrations/ace-fiona/db-02-quickstart/ 4d23h
- This command lists the spec and status settings of an
existing instance and shows what versions can be chosen, and which one is active:
oc get kind instanceName -o yaml
In the output, status.versions.available identifies the available channels and fully qualified versions as well as licensing details, and status.reconciled identifies the App Connect version that is running.