Fix Readme
Abstract
The following document is for IBM Cloud Pak for Business Automation 21.0.2 IF009. It includes the CASE package download, installation information, and the list of APARs that are resolved in this interim fix.
Content
Readme file for: | IBM Cloud Pak® for Business Automation |
---|---|
Product Release: | 21.0.2 |
Update Name: | 21.0.2 IF009 |
Fix ID: | 21.0.2-WS-CP4BA-IF009 |
Publication Date: | 30 March 2022 |
Last modified date: | 30 March 2022 |
Contents
Components impacted
Before installation
Installing the interim fix
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history
Prerequisites and supersedes
- Supersedes all prior interim fixes for CP4BA 21.0.2.
- Common Services 3.16.3 is available and is recommended for this ifix.
Components impacted
- General
- Cloud Pak for Business Automation Operator
- Automation Document Processing
- Automation Decision Services
- Business Automation Application
- Business Automation Insights
- Business Automation Navigator
- Business Automation Studio
- Business Automation Workflow including Automation Workstream Services
- Enterprise Records
- FileNet Content Manager
- Operational Decision Management
- User Management Service
- Workflow Process Service
Before installation
- Ensure you take regular backups of any databases associated with the environment.
- 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 \ > 'app.kubernetes.io/name=ibm-business-automation-insights'
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
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 demo installation.Actions: Demo environments do not support upgrades. Although you can use the interim fix content, install a new demo environment and use the CASE package from this interim fix.
- Scenario 2: Your installation is version 21.0.1.x or earlier.
Actions: If you are using a version before 21.0.2, 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.2 CASE package while you follow the instructions. -
Scenario 3: You are using an air gapped environment.Actions: To upgrade a 21.0.2 air gapped environment, you must first mirror all the new images to your internal registry. Follow the steps in "Setting up a mirror image registry" although be 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.2 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
- Required when using Business Automation Insights
You must update the IBM Automation Foundation operators to the v1.3 channel to ensure Business Automation Insights can be updated and continue to work and to address log4j vulnerability (CVE-2021-44228) for all IBM Automation Foundation components. For more information on how to upgrade channels, see the Upgrade the IBM Automation Foundation Core and IBM Automation Foundation subscriptions to the v1.1 channel section.
When using Business Automation Insights and upgrading from an IBM Automation Foundation version prior to 1.3, the operator will fail to become ready after the upgrade and kafka/zookeeper pods will show SSL errors. To resolve the issue, follow the "To renew the leaf certificates for Kafka" instructions in Changes to CA certificate and key does not automatically rotate Kafka leaf certificates. -
Review the installationIt 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 theibm-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. - Required when using Workflow Process Service
- 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.
- Back up your database backup, docker-compose.yml and folder for docker volumes “production_workflow_runtime_data” and “production_workflow_runtime_logs”.
- (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 cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-server:21.0.2-IF009 \ > <server>/workflow-ps-server:21.0.2-IF009 docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-authoring:21.0.2-IF009 \ > <server>/workflow-ps-authoring:21.0.2-IF009 docker push <server>/workflow-ps-server:21.0.2-IF009 docker push <server>/workflow-ps-authoring:21.0.2-IF009
- Run
docker-compose down
command to stop the Workflow Process Server container. - Update the image url's tags in docker-compose.yml.
<server>/workflow-ps-server:21.0.2-IF009 <server>/workflow-ps-authoring:21.0.2-IF009
- 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. - 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.10.x - Rule Designer 8.10.5.1
- Proceed with installation.
Uninstalling
List of Fixes
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 |
- General
- Cloud Pak for Business Automation Operator
- Automation Document Processing
- Automation Decision Services
- Business Automation Application
- Business Automation Insights
- Business Automation Navigator
- Business Automation Studio
- Business Automation Workflow including Automation Workstream Services
- Enterprise Records
- FileNet Content Manager
- Operational Decision Management
- User Management Service
- Workflow Process Service
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A |
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-2021-41092,CVE-2020-25649,PRISMA-2022-0065,CVE-2020-29562,CVE-2019-9704,CVE-2019-9705,CVE-2019-20372,CVE-2021-3872,CVE-2021-3984,CVE-2021-4019,CVE-2021-4192,CVE-2021-4193,CVE-2021-4122,CVE-2021-37136,CVE-2021-37137,CVE-2021-43797,CVE-2020-15257,CVE-2021-21334,CVE-2020-1953,CVE-2020-26160,CVE-2019-17495,CVE-2022-0355,CVE-2021-23017,CVE-2022-0538
Previous interim fixes will have included fixes which are also addressed with this interim fix. Consult the Related links section for readmes of previous interim fixes, at the bottom of this document.
|
X | X |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64769 | IBM FILENET CONTENT MANAGER CONTAINER FAILS TO DEPLOY |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64700 | ADP IFIX UPGRADE RELOADS DEFAULT ONTOLOGY WITH STARTER DEPLOYMENT | X | X |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64327 | SECURITY APAR - MULTIPLE SECURITY VULNERABILITIES IN JAVASCRIPT LIBRARIES |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64327 | SECURITY APAR - MULTIPLE SECURITY VULNERABILITIES IN JAVASCRIPT LIBRARIES |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A
|
N/A
|
For a cumulative list of all fixes included in this and prior interim fixes, please seeFileNet Content Manager Release Fix List APARs for IBM Cloud Pak for Business Automation
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
RS03894 | UNABLE TO EDIT A DECISION TABLE IN BUSINESS CONSOLE | |||
RS03808 | IN SOME CASES, ALL NUMERIC TYPES ARE TREATED AS DOUBLE IN ARL WHICH CAUSES BINDING ISSUE AND PREVENTS THE RULE FROM EXECUTING | |||
RS03833 | USING DECISION ENGINE CONCAT DOES NOT WORK BETWEEN A STRING AND A BIGDECIMAL OR BIGINTEGER | |||
RS03853 | ERROR DURING DE RULESET GENERATION WHEN USING A FUNCTION RETURNING A NUMBER | |||
RS03881 | USING DECISION ENGINE, PRIMITIVE NUMERIC EXPRESSIONS ARE BOXED TO JAVA.LANG.DOUBLE WHEN JAVA.LANG.NUMBER IS EXPECTED |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64159 | OPENSHIFT AUTHENTICATION OPTION DOES NOT WORK WITH CLOUD PAK FOR BUSINESS AUTOMATION | X |
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64756 | WORKFLOW PROCESS SERVICE PERSISTENCE DOES NOT WORK WITH DOCKER-COMPOSE VERSION 2.2.2 | X |
Known Limitations
Document change history
Related Information
[Supersedes 21.0.2-IF008] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF007] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF006] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF005] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF004] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF003] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF002] Readme for Cloud Pak for Business Automation 21.0.2 I…
[Supersedes 21.0.2-IF001] Readme for Cloud Pak for Business Automation 21.0.2 I…
Was this topic helpful?
Document Information
Modified date:
28 April 2022
UID
ibm16565027