Upgrading App Connect (Upgrading from Version 5.0 to Version 5.1)

5.1.0 5.1.1 5.1.2 This task applies only to IBM® Software Hub Version 5.1.0, Version 5.1.1, and Version 5.1.2.

If your environment includes watsonx™ Orchestrate, you must ensure that IBM App Connect in containers is running at the correct version.

Upgrade phase

Updating your client workstation
Collecting required information
Preparing to run an upgrade in a restricted network
Preparing to run an upgrade from a private container registry
Upgrading prerequisite software
Upgrading shared cluster components
Preparing to upgrade an instance
Upgrading an instance

Who needs to complete this task?

Cluster administrator A cluster administrator must complete this task.

When do you need to complete this task?

Complete this task only if you plan to upgrade an instance of IBM Cloud Pak® for Data where the watsonx Orchestrate service is installed.

Repeat as needed Each instance of watsonx Orchestrate requires a dedicated instance of App Connect. If you plan to upgrade an instance of IBM Cloud Pak for Data where watsonx Orchestrate is installed, you must upgrade the instance of App Connect that is associated with the instance that you plan to upgrade.

Before you begin

Best practice: You can run the commands in this task exactly as written using the installation environment variables. Ensure that you added the new environment variables from Updating your environment variables script.

In addition, ensure that you source the environment variables before you run the commands in this task.

Use the following table to determine whether you need to upgrade App Connect:

Current IBM Cloud Pak for Data Version	App Connect upgrade required?
Version 5.0.0	Yes
Version 5.0.1	Yes
Version 5.0.2	Yes
Version 5.0.3	No

Before you upgrade App Connect, ensure that you have the App Connect CASE package on your client workstation.

If you completed Downloading CASE packages before running upgrade commands in a restricted network (Upgrading from Version 5.0 to Version 5.1) you should already have the ibm-appconnect-${AC_CASE_VERSION}.tgz file on your workstation. However, make sure that you still have the AC_CASE_VERSION environment variable set on your workstation.

Check the version of the environment variable

Run the following command to check the version that is set for the AC_CASE_VERSION environment variable:

echo ${AC_CASE_VERSION}

Use the following table to ensure that the environment variable is set to the correct version for the release of IBM Software Hub you plan to upgrade to:

IBM Software Hub version	CASE package version
5.1.3	Not applicable. Prerequisite removed.
5.1.2	12.5.0
5.1.1	12.5.0
5.1.0	12.5.0

Download the App Connect CASE package

curl -sSLO https://github.com/IBM/cloud-pak/raw/master/repo/case/ibm-appconnect/${AC_CASE_VERSION}/ibm-appconnect-${AC_CASE_VERSION}.tgz

The CASE is downloaded to the current working directory.

Note: Move the CASE package to the work directory.

About this task

App Connect enables the watsonx Orchestrate service to connect to the applications where you want to automate work, such as email applications and customer relationship management (CRM) applications.

Procedure

To upgrade IBM App Connect in containers:

Log in to Red Hat® OpenShift® Container Platform as a user with sufficient permissions to complete the task.
```
${OC_LOGIN}
```
Remember: OC_LOGIN is an alias for the oc login command.
Change to the directory where the App Connect CASE package is stored and extract the file:
```
tar -xf ibm-appconnect-${AC_CASE_VERSION}.tgz
```

Create the catalog source for the App Connect operator:

oc patch \
--filename=ibm-appconnect/inventory/ibmAppconnect/files/op-olm/catalog_source.yaml \
--type=merge \
-o yaml \
--patch="{\"metadata\":{\"namespace\":\"${PROJECT_IBM_APP_CONNECT}\"}}" \
--dry-run=client \
| oc apply -n ${PROJECT_IBM_APP_CONNECT} -f -

The command returns the following response:

catalogsource.operators.coreos.com/appconnect-operator-catalogsource created

Create the subscription for the App Connect operator:

cat <<EOF | oc apply -f -
  apiVersion: operators.coreos.com/v1alpha1
  kind: Subscription
  metadata:
    name: ibm-appconnect-operator
    namespace: ${PROJECT_IBM_APP_CONNECT}
  spec:
    channel: ${AC_CHANNEL_VERSION}
    config:
      env:
      - name: ACECC_ENABLE_PUBLIC_API
        value: "true"
    installPlanApproval: Automatic
    name: ibm-appconnect
    source: appconnect-operator-catalogsource
    sourceNamespace: ${PROJECT_IBM_APP_CONNECT}
EOF

The command returns the following response:

subscription.operators.coreos.com/ibm-appconnect-operator created

Wait for the App Connect operator to be ready:

oc wait csv \
--namespace=${PROJECT_IBM_APP_CONNECT} \
--selector=operators.coreos.com/ibm-appconnect.${PROJECT_IBM_APP_CONNECT}='' \
--for='jsonpath={.status.phase}'=Succeeded

What to do next

Now that you've upgraded App Connect, you're ready to complete Upgrading shared cluster components (Upgrading from Version 5.0 to Version 5.1).