IBM Support

Readme for Cloud Pak for Business Automation 21.0.3 IF002

Fix Readme


The following document is for IBM Cloud Pak for Business Automation 21.0.3 IF002. It includes the CASE package download, installation information, and the list of APARs that are resolved in this interim fix.


Readme file for: IBM Cloud Pak® for Business Automation
Product Release: 21.0.3
Update Name: 21.0.3 IF002
Fix ID: 21.0.3-WS-CP4BA-IF002
Publication Date: 14 January 2022
Last modified date: 1 February 2022


Prerequisites and supersedes

  • Supersedes all prior interim fixes for CP4BA 21.0.3.

Components impacted

Before installation

  1. Ensure you take regular backups of any databases associated with the environment.
  2. Ensure your operators are in a healthy state prior to upgrading.
    If one or more operators are failing then it can prevent the system from completing an upgrade.
    It is recommended to check a few of the important CR statuses to ensure there are not failures and the statuses appear ready for the various installed components. It is recommended to check the status for this list of CRs if they exist:
    oc get icp4acluster -o yaml
    oc get AutomationUIConfig -o yaml 
    oc get Cartridge -o yaml 
    oc get AutomationBase -o yaml 
    oc get CartridgeRequirements -o yaml
  3. Required when using Business Automation Insights
    If Business Automation Insights is deployed, prune the Business Automation Insights deployment and jobs before you apply the updated custom resource YAML file.
    $ oc delete Deployment,Job -l \
    > ''
    Tip: For Flink event processing to resume from its previous state, make sure that savepoints are created before the upgrade and specified in the updated CR. For more information see, Restarting from a checkpoint or savepoint

Installing the interim fix

Cloud Pak for Business Automation 21.0.3 interim fixes are released to the v21.3 operator channel. If your environment has access to IBM entitled registry and has an automatic v21.3 channel subscription then production  installations are upgraded automatically. This upgrade generally occurs when the interim fix is released. Once the operator is upgraded, it triggers rolling updates for all the pods it manages to ensure they are updated to the appropriate version to match the operator.
Important: If you used any individual image tag settings in your CP4BA CR, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings for an production  installation when you upgrade.
The CASE package associated with this interim fix is ibm-cp-automation-3.2.2.tgz.

Depending on the current setup and state of your existing environment, there are various manual actions that might be required. The following scenarios cover what actions might be needed for a particular setup.
  • Scenario 1: You are using a starter installation.
    Actions: Starter environments do not support upgrades. Although you can use the interim fix content, install a new starter environment and use the CASE package from this interim fix.
  • Scenario 2: Your installation is version 21.0.2.x or earlier.
    Actions: If you are using a version before 21.0.3, then you must upgrade first. To upgrade your environment, follow the "Upgrading automation containers" instructions.
    When you perform the upgrade, you can substitute the CASE package from this interim fix for the 21.0.3 CASE package while you follow the instructions.
  • Scenario 3: You are using an air gapped environment.
    Actions: To upgrade a 21.0.3 air gapped environment mirror the entitled registry images to the local registry by completing the same steps on the bastion host that you used to install. For more information, see Setting up a mirror image registry.
    Make sure to use the CASE package from this interim fix.
    Once the images are mirrored, the automatic channel subscription completes the upgrade.
  • Scenario 4: Your v21.3 channel subscription is set to manual.
    Actions: If your channel subscription is set to manual, then you must approve any operator upgrades.
      a. Select the CP4BA operator from the OCP web console under Operators>Installed Operators.
      b. Go to the subscription tab for the operator.
      c. Trigger the operator update.
    Once the operator is updated, it triggers the upgrade of the other CP4BA images.

Performing the necessary tasks after installation

  1. Review the installation
    It is recommended that you review the CR yaml status section and operator logs after the upgrade to ensure there are no failures preventing your pods from upgrading.
    oc get icp4acluster -o yaml > CP4BAconfig.yaml
    oc logs deployment/ibm-cp4a-operator -c operator > operator.log
    If you are interested in verifying the expected image digest for a particular image, then you can review the ibm-cp-automation\inventory\cp4aOperatorSdk\resources.yaml file in the CASE package. This file has a listing of the images managed by the CP4BA operator and their expected digest for this particular interim fix level.
  2. Required when using Workflow Process Service OCP deployment
    If you used any individual image tag settings in your WfPSRuntime CR, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade.
  3. Required when using Workflow Process Service Docker Compose Edition
    1. Follow the step 2 of section "3. Running your environment" in Installing Workflow Process Service to login to the entitled registry with your entitlement key.
    2. Back up your database backup, docker-compose.yml and folder for docker volumes “production_workflow_runtime_data” and “production_workflow_runtime_logs”.
    3. (Optional) Push the images to your docker registry. Log in to your docker registry, and push the docker images into your docker registry using the following commands:
      docker login <server>
      docker tag \
      docker tag \
      docker push <server>/workflow-ps-server:21.0.3-IF002
      docker push <server>/workflow-ps-authoring:21.0.3-IF002
      Where <server> is the host of the docker image registry that you want to use to pull the images. For example myregistry.local:5000 or localhost:8080 for a self-hosted registry.
    4. Run docker-compose down command to stop the Workflow Process Server container.
    5. Update the image url's tags in docker-compose.yml.
    6. Run docker-compose up command to start the Workflow Process Server container
    For more detail on Workflow Process Service refer to Installing Workflow Process Service .
    Troubleshooting: If you are using a Docker Desktop version 4.3.0 or greater, you might get an out of memory error when you start the server. For more details and possible resolution to this issue, and other troubleshooting guidance, refer to Troubleshooting Workflow Process Service.
  4. Required when using Operational Decision Manager
    You must update your Rule Designer:
    • Open Eclipse 
    • Open menu Help > Check for Updates
    • select IBM Operational Decision Manager for Developers v8.11.x - Rule Designer
    • Proceed with installation.


There is no procedure to uninstall the interim fix.

List of Fixes

APARs fixed by this interim fix are listed in the following tables.
The columns are defined as follows: 
Column title Column description
APAR The defect number
Title A short description of the defect
Sec. A mark indicates a defect related to security
Cont. A mark indicates a defect specific to the Cloud Pak integration of the component
B.I. A mark indicates the fix has a business impact. Details are found in the title column or the APAR document
APAR Title Sec. Cont. B.I.
Cloud Pak for Business Automation delivers container images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly.
This interim fix includes fixes for these libraries to address:
CVE-2015-9261, CVE-2016-20012, CVE-2018-1000500, CVE-2018-1000517, CVE-2018-12434, CVE-2018-14404, CVE-2018-14567, CVE-2018-20679, CVE-2019-10160, CVE-2019-11045, CVE-2019-11046, CVE-2019-11047, CVE-2019-11048, CVE-2019-11050, CVE-2019-14697, CVE-2019-1547, CVE-2019-1549, CVE-2019-1551, CVE-2019-1563, CVE-2019-15718, CVE-2019-15903, CVE-2019-16056, CVE-2019-16168, CVE-2019-16935, CVE-2019-17594, CVE-2019-17595, CVE-2019-18197, CVE-2019-18224, CVE-2019-19906, CVE-2019-19923, CVE-2019-19925, CVE-2019-19956, CVE-2019-19959, CVE-2019-20218, CVE-2019-20367, CVE-2019-20388, CVE-2019-20907, CVE-2019-5094, CVE-2019-5188, CVE-2019-5481, CVE-2019-5482, CVE-2019-5747, CVE-2019-6477, CVE-2019-9740, CVE-2019-9947, CVE-2019-9948, CVE-2020-10531, CVE-2020-11501, CVE-2020-11656, CVE-2020-11984, CVE-2020-11993, CVE-2020-12243, CVE-2020-12762, CVE-2020-13249, CVE-2020-13434, CVE-2020-13435, CVE-2020-13630, CVE-2020-13632, CVE-2020-13777, CVE-2020-14145, CVE-2020-14349, CVE-2020-14350, CVE-2020-14422, CVE-2020-14765, CVE-2020-14776, CVE-2020-14789, CVE-2020-14812, CVE-2020-15180, CVE-2020-15358, CVE-2020-1712, CVE-2020-1927, CVE-2020-1934, CVE-2020-1967, CVE-2020-1971, CVE-2020-21913, CVE-2020-24659, CVE-2020-24977, CVE-2020-25692, CVE-2020-25694, CVE-2020-25695, CVE-2020-25696, CVE-2020-25709, CVE-2020-25710, CVE-2020-26116, CVE-2020-27350, CVE-2020-2752, CVE-2020-2760, CVE-2020-2812, CVE-2020-2814, CVE-2020-28196, CVE-2020-28928, CVE-2020-29361, CVE-2020-29362, CVE-2020-29363, CVE-2020-36221, CVE-2020-36222, CVE-2020-36223, CVE-2020-36224, CVE-2020-36225, CVE-2020-36226, CVE-2020-36227, CVE-2020-36228, CVE-2020-36229, CVE-2020-36230, CVE-2020-3810, CVE-2020-7059, CVE-2020-7060, CVE-2020-7062, CVE-2020-7063, CVE-2020-7064, CVE-2020-7065, CVE-2020-7066, CVE-2020-7067, CVE-2020-7068, CVE-2020-7069, CVE-2020-7070, CVE-2020-7071, CVE-2020-7595, CVE-2020-8169, CVE-2020-8177, CVE-2020-8231, CVE-2020-8284, CVE-2020-8285, CVE-2020-8286, CVE-2020-8492, CVE-2020-8616, CVE-2020-8617, CVE-2020-8619, CVE-2020-8622, CVE-2020-8623, CVE-2020-8624, CVE-2020-8625, CVE-2020-8927, CVE-2020-9283, CVE-2020-9490, CVE-2021-2022, CVE-2021-20231, CVE-2021-20232, CVE-2021-20305, CVE-2021-2154, CVE-2021-2166, CVE-2021-21702, CVE-2021-21703, CVE-2021-21704, CVE-2021-21705, CVE-2021-2194, CVE-2021-22876, CVE-2021-22890, CVE-2021-22922, CVE-2021-22923, CVE-2021-22925, CVE-2021-22926, CVE-2021-22945, CVE-2021-2372, CVE-2021-23839, CVE-2021-23840, CVE-2021-2389, CVE-2021-24031, CVE-2021-25214, CVE-2021-25215, CVE-2021-25216, CVE-2021-26690, CVE-2021-26691, CVE-2021-27212, CVE-2021-27218, CVE-2021-27219, CVE-2021-27928, CVE-2021-28153, CVE-2021-28831, CVE-2021-30139, CVE-2021-30641, CVE-2021-31618, CVE-2021-3177, CVE-2021-32027, CVE-2021-32028, CVE-2021-32029, CVE-2021-33910, CVE-2021-3393, CVE-2021-3449, CVE-2021-3450, CVE-2021-3516, CVE-2021-3517, CVE-2021-3518, CVE-2021-3520, CVE-2021-3537, CVE-2021-3541, CVE-2021-36159, CVE-2021-3677, CVE-2021-3711, CVE-2021-37750, CVE-2021-3998, CVE-2021-40438, CVE-2021-4122, CVE-2021-41581, CVE-2021-42374, CVE-2021-42376, CVE-2021-42378, CVE-2021-42379, CVE-2021-42380, CVE-2021-42381, CVE-2021-42382, CVE-2021-42383, CVE-2021-42384, CVE-2021-42385, CVE-2021-42386, CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, CVE-2021-45931, CVE-2022-23218, CVE-2022-23219, PRISMA-2021-0131
Cloud Pak for Business Automation Operator
APAR Title Sec. Cont. B.I.
Automation Document Processing
APAR Title Sec. Cont. B.I.
Automation Decision Services
APAR Title Sec. Cont. B.I.
APAR Title Sec. Cont. B.I.
Business Automation Insights
APAR Title Sec. Cont. B.I.
Business Automation Navigator
APAR Title Sec. Cont. B.I.
Business Automation Studio
APAR Title Sec. Cont. B.I.
Business Automation Workflow including Automation Workstream Services
APAR Title Sec. Cont. B.I.
Enterprise Records
APAR Title Sec. Cont. B.I.
FileNet Content Manager
APAR Title Sec. Cont. B.I.
Operational Decision Management
APAR Title Sec. Cont. B.I.
N/A N/A   
User Management Service
APAR Title Sec. Cont. B.I.

Known Limitations

Document change history

  • 14 January 2022: Initial publish.
  • 25 January 2022: Fix installation steps to reflect 21.0.3 documentation 
  • 1 February 2022: Added information about ensuring your operators are in a healthy state prior to upgrading. Some other cosmetic updates.
  • [{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS2JQC","label":"IBM Cloud Pak for Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"CloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

    Document Information

    Modified date:
    02 February 2022