Updating WebSphere Automation from 1.6.4 to 1.7.x

You can update WebSphere Automation. Instructions are provided for both network-connected installations and installations in air gap environments.

Before you begin

If your WebSphere Automation installation is not version 1.6.4, update it to version 1.6.4 before you update it to version 1.7.x.

Updating a network-connected installation

To update a network-connected installation, follow these instructions.
  1. Update IBM Cloud Pak foundational services to version 4.9.

    After running the appropriate script to update IBM Cloud Pak foundational services based on your chosen namespace scenario, you are directed to instructions to install the WebSphere Automation 1.7 operator.

Updating an installation in an air gap environment

To update an installation of WebSphere Automation in an air gap environment, follow these instructions.
Note: Many of these steps link to steps in the airgap installation instructions. When you complete such a step in the airgap installation instructions, return to this page to find the next step in the updating process. Do not continue to the subsequent steps in the airgap installation instructions.
Important: IBM Cloud Pak foundational services must be at the latest version of 3.23.x before you can update WebSphere Automation from 1.6.4 to 1.7.x. Updating WebSphere Automation to version 1.6.4 updates IBM Cloud Pak foundational services to version 3.23.12 or higher.
  1. Ensure that your cluster still meets all of the prerequisites for an air-gapped deployment.
  2. On your Red Hat OpenShift cluster, set the environment variables and download CASE files.
  3. Mirror the updated images to the offline registry.
  4. Configure ImageContentSourcePolicy and create a global pull secret.
  5. Update the catalog source.
  6. Update IBM Cloud Pak foundational services to version 4.9.
  7. Validate the installation.

Updating custom roles

If you created custom roles with the can_view_websphere_inventory permission in a previous version, you must change them to use a different permission. Using the UI with such a custom role in a later version results in an error when the UI displays some of the pages.

For instructions on updating the custom roles, see The MyCustomRole role includes an invalid permission: can_view_websphere_inventory.

What to do next

Validate the installation and access the WebSphere Automation UI.

If your installation stalls during an update, you might need to update the WebSphereSecure custom resource (CR) to use a storage class that supports ReadWriteMany (RWX) access mode. For more information, see Installation stalls during an update.