IBM Support

Readme for Cloud Pak for Business Automation 22.0.2 IF001

Fix Readme


Abstract

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

Content

Readme file for: IBM Cloud Pak® for Business Automation
Product Release: 22.0.2
Update Name: 22.0.2 IF001
Fix ID: 22.0.2-WS-CP4BA-IF001
Publication Date: 26 January 2023

Before installation
  1. Ensure you take regular backups of any databases associated with the environment.
  2. Ensure your operators are in a healthy state, before 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. Check the status of the following CRs when 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 you are 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

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 a production installation when you upgrade.
Breaking change(s):
  1.  In this interim fix, the URLs for Content Management Interoperability Services (CMIS) have changed (i.e., "cmis" context root was introduced):
    • The previous CPD route for CMIS has changed
      • from:  https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp 
      • to:  https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
    • The previous Openshift route for CMIS has changed
      • from:  https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp 
      • to:  https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
The CASE package associated with this interim fix is ibm-cp-automation-4.1.1.tgz.  Download the CASE package to wherever you are planning to perform the online installation or upgrade of this interim fix (for example, the infrastructure node of your OCP cluster) and extract the CASE package into a directory. For offline/Airgap installation or upgrade follow below mentioned Scenario 8.
Cloud Pak for Business Automation 22.0.2 interim fixes are released to the v22.2 operator channel. 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.
If your environment has access to IBM entitled registry and has an automatic v22.2 channel subscription then production installations are upgraded automatically. This upgrade generally occurs when the interim fix is released or when images are mirrored for air gap setup.

Starting with 21.0.3-IF007 interim fix, we "pin" the version of Cloud Pak for Business Automation along with all its dependencies including IBM Automation Foundation and IBM Cloud Pak Foundational Services.  In other words, the automatic updates will be turned off and you will need to perform the steps listed to upgrade your environments in the future. 
This interim fix contains the following version of Cloud Pak for Business Automation,  IBM Automation Foundation (IAF), and Cloud Pak Foundational Services (CPFS):
  • Cloud Pak for Business Automation – 22.0.2-IF001
  • IBM Automation Foundation – 1.3.12
  • Cloud Pak Foundational Services – 3.23.0
Note:  This interim fix only supports the Automation Foundation and Cloud Pak Foundational Services listed above. It is important that you deploy or upgrade Cloud Pak for Business Automation using the catalog sources in this readme document (the same catalog sources are also in the referenced CASE package).  If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Automation Foundation  and Cloud Pak Foundational Services versions, listed above, with other Cloud Paks' specifications.
Depending on the current setup and state of your existing environment, there are various upgrade actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.
  • Scenario 1: You are deploying a Starter deployment
    Actions: Starter deployments do not support upgrades. Although you can use this interim fix content to perform a Starter deployment.  To deploy a Starter deployment using the content of this interim fix, please see install a new Starter environment and use the CASE package from this interim fix.
  • Scenario 2: You are deploying a Production deployment
       Actions: You can use this interim fix content to perform a Production deployment.  To deploy a Production deployment using the content of this interim fix,
       please see install a new Production environment and use the CASE package from this interim fix.
  • Scenario 3: Your installed version is prior to 22.0.2.
       Actions: Follow the upgrade instructions while using the case package details from this iFix. 
       Warning: If you are using Business Automation Applications, you must upgrade from 22.0.1-IF006 due to DT174377. Upgrading from an earlier release could
       result in corrupted business applications.

       Important: When upgrading Cloud Pak Foundational Services, be sure to upgrade to the needed channel for the iFix as documented in the upgrade instructions.
       Note: If you are upgrading from a version prior to 22.0.1, then you will need to perform incremental upgrades from each prior version.
  • Scenario 4: You already have a Production deployment installed with 22.0.2 GA, and now you want to install another Production deployment using this interim fix on the same Openshift cluster.
    Actions: If you have existing production deployment with 22.0.2 GA and you want to install another production deployment of this interim fix using pinned catalogs, then you must first upgrade existing Cloud Pak Foundational Services to version 3.23.0 before you install another production deployment with this interim fix. You also needs to be aware that when applying the catalog sources from this interim fix on the Openshift cluster, the existing production deployment of CP4BA will also be updated to this interim fix.
    • Refer to the Cloud Pak Foundational Services upgrade section in the What's new in 22.0.2.  Make sure that you upgrade the Cloud Pak Foundational Services to 3.23.0 before you apply the catalog sources
      1. Log in to the cluster as an administrator by using the oc login command.
      2. Download the upgrade_common_services.sh script to your local machine.
      3. Run the script with the all namespaces flag and channel version to the command:
        • ./upgrade_common_services.sh -a -c v3.23
        • If you installed foundational services in specific namespaces (an unusual use case), add the namespaces and channel version to the command. For example, if you want to upgrade foundational services in a Cloud Pak namespace cp4ba and foundational services namespace cp4ba-cs to version v3.23, run the following command:
          • ./upgrade_common_services.sh -cloudpaksNS cp4ba -csNS cp4ba-cs -c v3.23
      4. You need to apply below updated catalog sources and you are not required to execute update_subscription.sh script to change the subscription.
        1. Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, IBM Foundational Services with Cloud Pak for Business Automation.
          You can apply the catalog sources below from a command line by creating a YAML file (for example, cp4ba_catalog_sources.yaml) with the catalog sources below and performing "oc apply -f cp4ba_catalog_sources.yaml", or you can apply the catalog sources using the OCP console
          Note:  The IBM Business Team Service, and Postgres catalog sources are dependent components of Cloud Pak for Business Automation. 
          # CP4BA 22.0.2 IF001 catalog
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp4a-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-cp4a-operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-catalog@sha256:95ff5f4c93fa26ee47fa4f620425b87bc5acce106b27a9c2497bc17681253349
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Base 1.3.12
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp-automation-foundation-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-foundation-catalog@sha256:61b40644c6442b21cce3d32eb07b3ae9bc4443b43d33575a8c73fb9cac6bfb57
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Core 1.3.12
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-automation-foundation-core-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Core Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-automation-foundation-core-catalog@sha256:39ba42e91d7493d1ff7326d5364b99fe7305dbe713a71948de97b6a730314ede
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Cloud Foundational Services 3.23.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:12744600eaa9d509ecca3d0a7d48f1fe022fade59eacd7c8f646c1d0f1e9dd64
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM Business Teams Service version 3.23.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: bts-operator
  namespace: openshift-marketplace
spec:
  displayName: BTS Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:1cbb05e621a8b0e6eacb720c823814ce4d9d178c9aad98252599e9972f911671
  updateStrategy:
    registryPoll:
      interval: 45m
---
# Cloud Native PostgresSQL 4.9.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: cloud-native-postgresql-catalog
  namespace: openshift-marketplace
spec:
  displayName: Cloud Native Postgresql Catalog
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:5b9eb4816ff00bfe1c063d2f707d55c2ea1df745bde4e7a17712214f62ebdf24
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
        2. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
          Note:  It is not recommended to set subscriptions to manual, this makes the upgrade more error prone.  By default all subscriptions are set to automatic.
      5. Follow the steps to perform validation of your Production deployment
  • Scenario 5: Your installation is version 21.0.3-IFxxx and you're not using pinned catalog
    Actions: If you are using 21.0.3-IFxxx and not pinned catalogs, then your deployment is automatically updated to the latest interim fix of 21.0.3 in the v21.3 channel. To change this behavior , please follow Upgrading operators that are not pinned instructions.
  • Scenario 6: Your installation is version 21.0.3-IFxxx and you're using pinned catalog (note that pinned catalog was available with 21.0.3-IF007 or later)
    Actions: If your installation is 21.0.3-IFxxx and using pinned catalogs, then you must upgrade the operators for all of the Cloud Pak operators to 22.0.1-IF006. You can use the OpenShift console or the command line, please follow Upgrading operators that are pinned instructions.
  • Scenario 7:  Your installation is 22.0.2 GA or 22.0.2 + any interim fix and you're using pinned catalog (which is common use case as only pinned catalogs were provided in this version)
    Actions:  If you are using version 22.0.2 GA, then you must first upgrade existing Cloud Pak Foundational Services to version 3.23.0 before you install another production deployment with this interim fix.
    • Refer to the Cloud Pak Foundational Services upgrade section in the What's new in 22.0.2.  Make sure that you upgrade the Cloud Pak Foundational Services to 3.23.0 before you apply the catalog sources below.
      1. Log in to the cluster as an administrator by using the oc login command.
      2. Download the upgrade_common_services.sh script to your local machine.
      3. Run the script with the all namespaces flag and channel version to the command:
        • ./upgrade_common_services.sh -a -c v3.23
        • If you installed foundational services in specific namespaces (an unusual use case), add the namespaces and channel version to the command. For example, if you want to upgrade foundational services in a Cloud Pak namespace cp4ba and foundational services namespace cp4ba-cs to version v3.23, run the following command:
          • ./upgrade_common_services.sh -cloudpaksNS cp4ba -csNS cp4ba-cs -c v3.23
    • You need to apply below updated catalog sources and does not require to execute update_subscription.sh script to change the subscription. 
      1. Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, IBM Foundational Services with Cloud Pak for Business Automation.
        You can apply the catalog sources below from a command line by creating a YAML file (for example, cp4ba_catalog_sources.yaml) with the catalog sources below and performing "oc apply -f cp4ba_catalog_sources.yaml", or you can apply the catalog sources using the OCP console
        Note: you can apply only one catalog source at a time using the OCP console. 
        Note:  The IBM Business Team Service, and Postgres catalog sources are dependent components of Cloud Pak for Business Automation. 
        # CP4BA 22.0.2 IF001 catalog
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp4a-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-cp4a-operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-catalog@sha256:95ff5f4c93fa26ee47fa4f620425b87bc5acce106b27a9c2497bc17681253349
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Base 1.3.12
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp-automation-foundation-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-foundation-catalog@sha256:61b40644c6442b21cce3d32eb07b3ae9bc4443b43d33575a8c73fb9cac6bfb57
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Core 1.3.12
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-automation-foundation-core-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Core Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-automation-foundation-core-catalog@sha256:39ba42e91d7493d1ff7326d5364b99fe7305dbe713a71948de97b6a730314ede
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Cloud Foundational Services 3.23.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:12744600eaa9d509ecca3d0a7d48f1fe022fade59eacd7c8f646c1d0f1e9dd64
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM Business Teams Service version 3.23.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: bts-operator
  namespace: openshift-marketplace
spec:
  displayName: BTS Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:1cbb05e621a8b0e6eacb720c823814ce4d9d178c9aad98252599e9972f911671
  updateStrategy:
    registryPoll:
      interval: 45m
---
# Cloud Native PostgresSQL 4.9.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: cloud-native-postgresql-catalog
  namespace: openshift-marketplace
spec:
  displayName: Cloud Native Postgresql Catalog
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:5b9eb4816ff00bfe1c063d2f707d55c2ea1df745bde4e7a17712214f62ebdf24
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
      2. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
        Note: It is not recommended to set subscriptions to manual, this makes the upgrade more error prone . By default all subscriptions are set to automatic.
    • Follow the steps to perform validation of your Production deployment
  • Scenario 8:  Your installation is air gap and 22.0.2 GA
    Actions:  If you are using version 22.0.2 GA, then you must first upgrade existing Cloud Pak Foundational Services to version 3.23.0 before you install another production deployment with this interim fix.
    • Refer to the Cloud Pak Foundational Services upgrade section in the What's new in 22.0.2.  Make sure that you upgrade the Cloud Pak Foundational Services to 3.23.0 before you apply the catalog sources.
      1. Log in to the cluster as an administrator by using the oc login command.
      2. Download the upgrade_common_services_airgap.sh script to your local machine.
      3. Run the script with the all namespaces flag and channel version to the command:
        • ./upgrade_common_services_airgap.sh -a -c v3.23
        • If you installed foundational services in specific namespaces (an unusual use case), add the namespaces and channel version to the command. For example, if you want to upgrade foundational services in a Cloud Pak namespace cp4ba and foundational services namespace cp4ba-cs to version v3.23, run the following command:
          • ./upgrade_common_services_airgap.sh -cloudpaksNS cp4ba -csNS cp4ba-cs -c v3.23
    • Follow the steps below on the bastion host where you previously deployed 22.0.2:
      1. Set up the environment variables for CASE (Using IBM-Pak Plugin)
        1. Get the cp4ba-case-to-be-mirrored-22.0.2-IF001.txt file for 22.0.2 IF001 and you must rename the file to cp4ba-case-to-be-mirrored-22.0.2-IF001.yaml
          oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-22.0.2-IF001.yaml
          The (absolute path to file) needs to be a path starting from "/". For example, "/opt"
        2. Define the environment variable $TARGET_REGISTRY by running the following command
          export TARGET_REGISTRY=<target-registry>
          The <target-registry> refers to the registry (hostname and port) where the images are mirrored to and accessed by the OCP cluster. For example: 172.16.0.10:5000
        3. Create the following environment variables with the installer image name and the version.
          export CASE_NAME=ibm-cp-automation
          export CASE_VERSION=4.1.1
        4. Set the environment variable of the --inventory parameter
          export CASE_INVENTORY_SETUP=cp4aOperatorSetup
        5. Follow instructions from 1c onwards under procedure section mentioned in Mirroring images to the private registry.
        6. Update the catalog with the new version by running the install-catalog action. 
          oc ibm-pak launch $CASE_NAME \
--version $CASE_VERSION \
--action install-catalog \
--inventory $CASE_INVENTORY_SETUP \
--namespace $NAMESPACE \
--args  "--registry $TARGET_REGISTRY --recursive --inputDir ~/.ibm-pak/data/cases/$CASE_NAME/$CASE_VERSION"
        7. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
          Note: It is not recommended to set subscriptions to manual as it can make the upgrade more error prone. By default all subscriptions would be set to automatic.
      2. Set up the environment variables for CASE (Using cloudctl which is deprecated)
        1. export CASE_NAME=ibm-cp-automation 
          export OFFLINEDIR=/opt/cp4ba2202-if001
          export CASE_VERSION=4.1.1
          export CASE_INVENTORY_SETUP=cp4aOperatorSetup 
          export CASE_ARCHIVE=${CASE_NAME}-${CASE_VERSION}.tgz 
          export CASE_LOCAL_PATH=${OFFLINEDIR}/${CASE_ARCHIVE}

          Note: The values are specific to the interim fix, however, you can choose a different empty directory for the OFFLINEDIR if you need to put the files somewhere else.
        2. Save this specific set of case packages
          cloudctl case save --case docker://icr.io/cpopen/ibm-cp-automation-case-cache@sha256:691a9ebae2ca40fefd53eabf8cfff965eb042aea962cf96294f03c0c26ec6534 --outputdir ${OFFLINEDIR}
          Once the command completes, all the Case archive and inventory are saved under /opt/cp4ba2202-if001.
        3. Mirror the entitled registry images to the local registry by completing the same steps used during installation. For more information about mirroring, see Mirroring images to the private registry.
          Make sure to use the CASE image OFFLINEDIR (/opt/cp4ba2202-if001) from step 1.
        4. Update the catalog with the new version by running the install-catalog action. 
          cloudctl case launch \
--case ${OFFLINEDIR}/${CASE_ARCHIVE} \
--inventory ${CASE_INVENTORY_SETUP} \
--action install-catalog \
--namespace ${NAMESPACE} \
--args "--registry ${LOCAL_REGISTRY} --inputDir ${OFFLINEDIR} --recursive"
        5. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
          Note: It is not recommended to set subscriptions to manual as it can make the upgrade more error prone. By default all subscriptions would be set to automatic.
      3. Follow the steps to perform validation of your Production deployment

Performing the necessary tasks after installation

  1. Update Kafka certificates when you are using Business Automation Insights
    If you are using Business Automation Insights and upgrading from an IBM Automation Foundation version before 1.3, the operator will fail to become ready after the upgrade, and kafka/zookeeper pods 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.
  2. 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.
  3. Required when you are 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.
  4. Required when you are using Workflow Process Service Docker Compose Edition
    1. Follow the step 2 of section "3. Running your environment" in Installing Workflow Process Service to log in 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 by using the following commands: 
      docker login <server>
docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-server:<tag> \
 <server>/workflow-ps-server:<tag>
docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-authoring:<tag> \
 <server>/workflow-ps-authoring:<tag>
docker push <server>/workflow-ps-server:<tag>
docker push <server>/workflow-ps-authoring:<tag>
      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. Also, replace <tag> with the corresponding tag matching this interim fix's tag in the form of <release>-IFxxx, for example, 22.0.2-IF001.
    4. Run docker-compose down command to stop the Workflow Process Server container.
    5. Update the image url's tags in docker-compose.yml. 
      <server>/workflow-ps-server:<tag>
<server>/workflow-ps-authoring:<tag>
      Where <tag> is the corresponding tag matching this interim fix's tag in the form of <release>-IFxxx, for example, 22.0.2-IF001.
    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.
  5. Required when you are 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.

Uninstalling

There is no procedure to uninstall the interim fix.

List of Fixes

APARs/Known Issues fixed by this interim fix are listed in the following tables.
The columns are defined as follows: 
Column title Column description
APAR/Known Issue 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/Known Issue document
General
Known Issue 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-2022-41880, CVE-2022-41884, CVE-2022-41886, CVE-2022-41887, CVE-2022-41888, CVE-2022-41889, CVE-2022-41890, CVE-2022-41891, CVE-2022-41893, CVE-2022-41894, CVE-2022-41895, CVE-2022-41896, CVE-2022-41897, CVE-2022-41898, CVE-2022-41899, CVE-2022-41900, CVE-2022-41901, CVE-2022-41902, CVE-2022-41907, CVE-2022-41908, CVE-2022-41909, CVE-2022-41910, CVE-2022-41911, GHSA-cqvq-fvhr-v6hc, GHSA-xf83-q765-xm6m, CVE-2022-31690, CVE-2022-31692, CVE-2022-2047, CVE-2022-2048, CVE-2022-42898, CVE-2022-30595, CVE-2022-45198, CVE-2022-45199, CVE-2022-36087, CVE-2020-15228, CVE-2022-41900, CVE-2022-41880, CVE-2022-41910, CVE-2022-41902, CVE-2022-35941, CVE-2022-41888, CVE-2022-41889, CVE-2022-41890, CVE-2022-41891, CVE-2022-41893, CVE-2022-41895, CVE-2022-41896, CVE-2022-41897, CVE-2022-41898, CVE-2022-41899, CVE-2022-41887, CVE-2022-41901, CVE-2022-41886, CVE-2022-41907, CVE-2022-41908, CVE-2022-41909, CVE-2022-41884, CVE-2022-41911, CVE-2022-2047, CVE-2022-31692, CVE-2022-36944
Previous interim fixes 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.

Back to top

Cloud Pak for Business Automation Operator
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Automation Document Processing
Known Issue Title Sec. Cont. B.I.
DT179105 Cannot connect to Automation Document Processing HADR database servers X X
DT188601 Excel incorrectly interprets CSV export values as formulas X X X
DT188603 Verify client gives TypeError: view._onChange is not a function error X X
DT188626 Cannot add Date and Time datatype in Data Standardization X X
DT188631 Some value types are changed to text when the value is not in the document X X
DT188636 The Document Reference object is not supporting the setDocumentId api function X X
DT188638 The Document Reference object is displaying the document class symbolic name instead of the display name X X
DT188642 Project Export fails if there are unprocessed documents in the runtime API X X
DT188645 Processing a document fails if it is associated with a document class that has no KVPs defined X X
DT188859 Cannot open documents from content list in runtime when desktop not specified X X

Back to top

Automation Decision Services
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Insights
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Navigator
Business Automation Studio
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT178578 WORKFLOW SERVER PODS FREQUENTLY RESTARTING WHEN USING AUTOSCALING
DT179170 PROCESS FEDERATION SERVER OPERATOR DOES NOT MONITOR MULTIPLE NAMESPACES
DT187952 AN UNDEFINED WALKME ERROR CAUSES LOADING ICON TO BE DISPLAYED IN NAVIGATOR WORKPLACE
DT178901 NOCLASSDEFFOUNDERROR OCCURS WHEN EXECUTING THE SCHEMAGENERATOR SCRIPT OF SAVED SEARCH ACCELERATION TOOLS IN LINUX OS

Back to top

Enterprise Records
Known Issue Title Sec. Cont. B.I.
N/A
N/A

Back to top

FileNet Content Manager
Operational Decision Management
Known Issue Title Sec. Cont. B.I.
DT172854 SOME BUSINESS CONSOLE ADMINISTRATION TABS ARE SLOW WHEN MANY GROUPS AND USERS ARE DEFINED
DT173151 DEPLOYMENT FROM DECISION CENTER MAY PRODUCE CORRUPTED RULESETS
DT173156 STRUCT DEFINED IN MODEL EXTENSION CANNOT BE HIDDEN
DT173219 AFTER UPDATING THE BUSINESS MODEL EXTENSION DATA, DECISION CENTER NEEDS TO BE RESTARTED AND ALL USERS MAY SEE AN ERROR &quot;CANNOT DISPLAY CONTENT TREE&quot; WHILE BROWSING THE BRANCH CONTENTS.
DT173272 THE RULE EDITOR TOOLTIP THROWS A NULLPOINTEREXCEPTION WHEN THE SERVER CANNOT PARSE RULE
DT173761 SAVING A RULE IN THE RULE EDITOR DOES NOT WORK WHEN THE RULE CANNOT BE PARSED
DT173771 THE LIBRARY TAB MAY LIST ALL THE DECISION SERVICES UNDER SOME CIRCUMSTANCES
DT173906 LAST CHANGED ON DATES DO NOT ALWAYS SHOW THE TIME
DT173997 DOUBLE BYTES CHARACTERS IN ARTIFACT DESCRIPION IS MALFORMED DISPLAYED AFTER SAVE
DT174051 INDEXOUTOFBOUNDSEXCEPTION WHEN COMPARING RULE DIFFERENCES IN SNAPSHOT COMPARE
DT174404 INJECTION XML (XXE)
DT178111 SAVE RULE BUTTON IN BUSINESS CONSOLE UNEXPECTEDLY BECOMES INACTIVE
DT178410 CANNOT SAVE DECISION TABLE AFTER DISPLAYING DETAILS
DT178423 LISTING THE DECISION SERVICES IS SLOWER FOR A NON-ADMIN USER WHEN PROJECT SECURITY IS ENABLED AND THERE ARE MANY BASELINES
DT178763 NORWEGIAN VERBALIZATION ERRORS IN BAL
DT178774 VARIABLES RELATED ERRORS DURING DEPLOYMENT OF BIG PROJECTS
DT179421 EDITING A GROUP IS SLOW WHEN THERE ARE MANY USERS DEFINED IN THE DATABASE
DT179755 2022 JANUARY - SECURITY ISSUES IN OPERATIONAL DECISION MANAGER
DT187737 CANNOT RENAME SHARED BRANCH OF A MIGRATED CLASSIC RULE PROJECT

Back to top

User Management Service
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Workflow Process Service
Known Issue Title Sec. Cont. B.I.
DT178901 NOCLASSDEFFOUNDERROR OCCURS WHEN EXECUTING THE SCHEMAGENERATOR SCRIPT OF SAVED SEARCH ACCELERATION TOOLS IN LINUX OS

Back to top

Known Limitations

Document change history

  • 7 February 2023: Adding ODM Known Issues.
  • 31 January 2023: Adding ODM Known Issues.
  • 26January 2023: Initial publish.

    • [{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"Other-\u003ECloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"22.0.2"}]

    Document Information

    Modified date:
    07 November 2023

    UID

    ibm16857209

    Page Feedback