Upgrading automation containers

If you installed any Cloud Pak for Business Automation capability from 21.0.2 in an enterprise deployment and you want to continue to use them in 21.0.3, you can upgrade them. If you installed a version before 21.0.2, then you must upgrade incrementally before you upgrade to 21.0.3 unless you installed a 20.0.3 Cloud Pak for Business Automation deployment with FileNet Content Manager, Business Automation Workflow, or Operational Decision Manager. You can upgrade these capabilities only from 20.0.3 by using the documented steps.

Before you begin

Before you start an upgrade, define a backup recovery process, and take snapshots to enable rollback if needed. If you do not back up your data, you cannot properly roll back.
  1. Read Preparing your deployed custom resource for an upgrade.
  2. Determine what upgrade channel to subscribe to, and follow the upgrade procedure for your containers for specific instructions.
  3. Read Backing up your environments for additional instructions that are not covered in the container upgrade sections.
  4. As the admin username in secrets is case-sensitive, if it is the LDAP user, make sure you use the same case as in the LDAP.
Tip: The new version might introduce new parameters or require different values in the custom resource (CR) of your CP4BA deployment. To get a look at these changes, you can generate a CR file by using the deployment script from the new version and then compare your previous CR with the generated CR. If you do want to compare the CR files, it is important to choose the same capabilities and optional components in the new script that are included in your deployed CR. For more information about running the deployment script, see Generating the custom resource with the deployment script.

About this task

It is the deployment that you use to scale down the previous version of the applications, and scale up the new version in a controlled fashion with zero downtime.

Important: Due to the number of dependencies that each pattern has it is advisable not to try to upgrade individual containers in your deployment. Upgrade everything within your deployment at the same time.