IBM Support

Readme for Cloud Pak for Business Automation 23.0.1 IF002

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 23.0.1 IF002. 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: 23.0.1
Update Name: 23.0.1 IF002
Fix ID: 23.0.1-WS-CP4BA-IF002
Publication Date: 31 August 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:
  3. oc get icp4acluster -o yaml 
oc get content -o yaml
oc get Foundation -o yaml
  4. Remove any image settings in CRs
    If you used any individual image tag settings in your CRs, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade. This doesn't apply to starter installation as it requires a new install.

Installing the interim fix

This interim fix contains the following version of Cloud Pak for Business Automation and Cloud Pak Foundational Services (CPFS):
  • Cloud Pak for Business Automation 23.0.1-IF002
  • Cloud Pak Foundational Services 4.1
Note:  This interim fix only supports the 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 Cloud Pak Foundational Services versions, listed above, with other Cloud Paks' specifications.
Important interim fix details:
The CASE package content is used to help facilitate installation and upgrade operation. See the various instructions for more specific details.
Cloud Pak for Business Automation 23.0.1 interim fixes are released to the v23.1 operator channel. Once the operators are upgraded, it triggers rolling updates for all the pods it manages to ensure they are updated to the appropriate version to match the operator.
Step 1: Setup the CASE package
  1. Download the CASE package provided with this interim fix to a Linux based machine (RHEL or macOS).
  2. Use the tar command to extract the cert-kubernetes directory. 
    tar -xvzf ibm-cp-automation-5.0.2.tgz
cd ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs
tar -xvf cert-k8s-23.0.1.tar
cd cert-kubernetes/scripts
Step 2:  Perform the installation or update the existing deployment
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 installing a Starter deployment or have an existing Starter deployment
    Actions: Starter deployments do not support upgrades.  Although you can use this interim fix content to perform an installation 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.
    Note: If you have an existing Cloud Pak Foundation Services instance installed in the cluster or in the namespace where CP4BA is being installed, then it is not supported.  The Starter deployment of CP4BA is only supported when deploying into a new namespace without CPFS. 
  • Scenario 2: You are installing 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.
    Note: If you have an existing Cloud Pak Foundation Services instance installed in the cluster or in the namespace where CP4BA is being installed, then it is not supported.  The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFS.
  • Scenario 3: Your installed Production deployment version is 22.0.2 IF00x (at least IF002).
    Actions:  
    •  Upgrade OCP Cluster version
      • Before you start an upgrade of OpenShift Container Platform (OCP), define a backup recovery process, and take snapshots to enable rollback if needed. You cannot properly roll back if you do not back up your data.
    • Backing up your Databases
      • Create a full backup of volumes and configuration files that can help you roll back your upgrade if needed.
    • Upgrading the operators in an online environment
      • When you are applying the catalog sources use the catalog source from this ifix case package.
  • Scenario 4:  Your installed Production deployment is 23.0.1 GA or any previous 23.0.1 iFix and is online
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    1. If CP4BA is installed with deployment scripts, you could upgrade to this interim fix with the following steps: 
      * Running the script to upgrade a CP4BA deployment from 23.0.1 GA/23.0.1.X to 23.0.1.X.
      - Run the script in [upgradeOperator] mode to upgrade the CP4BA operator
      Example: 
      ./cp4a-deployment.sh -m upgradeOperator -n <project_name>
      Alternatively the catalog sources can be applied to pin to the specified versions for Cloud Pak Foundational Services and Cloud Pak for Business Automation.  In the case package the needed catalogSource yaml file is located here 
      ibm-cp-automation\inventory\cp4aOperatorSdk\files\deploy\crs\cert-k8s-23.0.1\cert-kubernetes\descriptors\op-olm\catalog_source.yaml
      Execute 
      oc apply -f catalog_source.yaml
    2. Alternatively you can create the catalog_source.yaml file with the following text. 
      # CP4BA 23.0.1-IF002 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:ff465bc6fb8c576f7efd18db4fbd0b4bd4e34433e2df33c1974d174cef8410da
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM CS Flink Operator Catalog 1.3.14
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cs-flink-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM CS Flink Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cs-flink-operator-catalog@sha256:732e3afb4c43bb3367175c0e2d4461faed9a29eb1ba47c63875efdcb7d6ae54f
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM CS Elastic Operator Catalog 1.3.14
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cs-elastic-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM CS Elastic Search Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cs-elastic-operator-catalog@sha256:a41ad89177f39a200f666310d7505848c7953965db08017a97781c5d51f78642
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM Certificate Manager 4.1
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cert-manager-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-cert-manager-4.1.0
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cert-manager-operator-catalog@sha256:c1b6196c5499a5c0abcaddba4d64cee67d9893d672c96d839020bc68392089d0
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM License Manager 4.1
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-licensing-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-licensing-4.1.0
  publisher: IBM
  image: icr.io/cpopen/ibm-licensing-catalog@sha256:3c5a9afce735053967b8458a9170fb99efff5cb442533db222c76d20e06295c8
  sourceType: grpc
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Cloud Foundational Services 4.1
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: opencloud-operators-v4-1
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:c1fbc5080364b95be0a499b944f37b09ad662913c1bca3abc3f3da733a8a7dac
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100    
---
# IBM Business Teams Service version 3.28.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: bts-operator
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
spec:
  displayName: BTS Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:6460b1172321e6088d2d97bb7da6a0ca9a50c23eb5973dc3ac6295eaf3e52229
  updateStrategy:
    registryPoll:
      interval: 45m
---
# Cloud Native PostgresSQL 4.14.0+20230619
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: cloud-native-postgresql-catalog
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
spec:
  displayName: Cloud Native Postgresql Catalog
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:a06b9c054e58e089652f0e4400178c4a1b685255de9789b80fe5d5f526f9e732
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM FileNet Content Manager Standalone catalog.
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-fncm-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-fncm-operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-fncm-catalog@sha256:2fd6f301b908d2385c0600554f74b35baa287f1e821ea7ea4cb14b133296a055
  updateStrategy:
    registryPoll:
      interval: 45m
    3. If you have any subscriptions set to manual, then you need to approve any pending InstallPlans.
      The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone. By default all subscriptions are set to automatic.
    4. Since Cloud Pak Foundational Services channel is changed to v4.1 , execute the following steps to upgrade Cloud Pak Foundational Services , IBM License Service and IBM Certificate Manager to 4.1
      1. cd cert-kubernetes/scripts/cpfs/installer_scripts/cp3pt0-deployment
      2. ./setup_singleton.sh --enable-licensing --cert-manager-source ibm-cert-manager-catalog --licensing-source ibm-licensing-catalog --license-accept -v 1 -c v4.1
      3. Once the above scripts completed , execute below to upgrade Cloud Pak Foundational Services
      4. ./setup_tenant.sh --operator-namespace <CP4BA Namespace> -s opencloud-operators-v4-1 -c v4.1 --license-accept -v 1
      5. Wait for the upgrade to finish.
    5. If CP4BA is installed with deployment scripts, you could check the status of the upgrade of the CP4BA operator and CP4BA deployment to this interim fix with the following steps:
      1. Run the script in [upgradeOperatorStatus] mode to check that the upgrade of the CP4BA operator and its dependencies is successful.
        Example:  
        ./cp4a-deployment.sh -m upgradeOperatorStatus -n <project_name>
      2. Run the script in [upgradeDeploymentStatus] mode to check that the upgrade of the CP4BA deployment is successful.
        Example: 
        ./cp4a-deployment.sh -m upgradeDeploymentStatus -n <project_name>
  • Scenario 5:  Your installed Production deployment is 23.0.1 GA or any previous 23.0.1 iFix and using airgap/offline.
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    Note: If your Cloud Pak Foundational Services instance is at an earlier release review the channel upgrade info in Before Installation.
    1. Get the case package mirror file, cp4ba-case-to-be-mirrored-23.0.1-IF002.txt, for interim fix and you must rename the file to cp4ba-case-to-be-mirrored-23.0.1-IF002.yaml. Then execute this command to download the case files: 
      oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-23.0.1-IF002.yaml
      The (absolute path to file) needs to be a path starting from "/". For example, "/opt"
      For more information, see Downloading the CASE files.
    2. Follow the instructions for either mirroring option in Mirroring images to the private registry.
      Important: You must set export CASE_NAME=ibm-cp-automation and export CASE_VERSION=5.0.2 and that is the version for this iFix.
    3. Update the catalog with the new version. 
      cat $HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml | sed 's/opencloud-operators/opencloud-operators-v4-0/g' | oc apply -f -
    4. If you have any subscriptions set to manual, then you need to approve any pending InstallPlans.
      The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone. By default all subscriptions are set to automatic.
    5. Since Cloud Pak Foundational Services channel is changed to v4.1 , execute the following steps to upgrade Cloud Pak Foundational Services , IBM License Service and IBM Certificate Manager to 4.1
      1. cd cert-kubernetes/scripts/cpfs/installer_scripts/cp3pt0-deployment
      2. ./setup_singleton.sh --enable-licensing --cert-manager-source ibm-cert-manager-catalog --licensing-source ibm-licensing-catalog --license-accept -v 1 -c v4.1
      3. Once the above scripts completed , execute below to upgrade Cloud Pak Foundational Services
      4. ./setup_tenant.sh --operator-namespace <CP4BA Namespace> -s opencloud-operators-v4-1 -c v4.1 --license-accept -v 1
      5. Wait for the upgrade to finish.
  • Scenario 6: Your installed Production deployment is 22.0.2 IF00x (at least IF002) and using airgap/offline.
    Actions:  

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 you are using Workflow Process Service Docker Compose Edition
    1. Follow the step 2 of section "3. Running your environment23.0.1?topic=installing-workflow-process-service-docker" rel="noopener" target="_blank">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, 23.0.1-IF002.
    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, 23.0.1-IF002.
    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.
  3. 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.12.x - Rule Designer
    • Proceed with installation.
  4. Required If you are installing or upgrading Business Automation Insights with this iFix
    You must update CP4BA Custom Resource with digests for iaf-flink & iaf-eventprocessing-proxy images before applying custom resource to deploy this iFix.
    • Update custom resource file to add below with correct digests for Flink.
    • apiVersion: icp4a.ibm.com/v1
kind: ICP4ACluster
metadata:
  name: icp4adeploy
spec:
  shared_configuration: 
    ---
  ##############################################################################
  ########      IBM Business Automation Insights (BAI) configuration    ########
  ##############################################################################
  bai_configuration:
    flink:
      manager_image: cp.icr.io/cp/iaf-flink@sha256:0a5e18b137524877b4378113f362a67c1768453ff65273fd667dc57d55afa005
      eventprocessing_proxy_image: cp.icr.io/cp/iaf-eventprocessing-proxy@sha256:954ef0ee64b447736dd69083ec94afeae4229382798f1317cc44a0a208e5b82e
    • Apply the modified custom resource

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-2023-1428, CVE-2023-32731, CVE-2023-32732, CVE-2023-34453, CVE-2023-34454, CVE-2023-34455, CVE-2023-40336, CVE-2023-40337, CVE-2023-40338, CVE-2023-40339, CVE-2020-24736, CVE-2023-36665, CVE-2023-22044, CVE-2023-25193, CVE-2023-2828, CVE-2023-35887, CVE-2023-37276, RHSA-2023:3106, RHSA-2023:2963, RHSA-2023:3018, CVE-2022-43552, CVE-2023-27535, CVE-2022-35252, CVE-2023-38325, CVE-2022-36087, CVE-2023-2828, CVE-2023-36665, CVE-2022-25883, CVE-2023-34034, CVE-2023-34453, CVE-2023-34454, CVE-2023-34455, RHSA-2023:4419, CVE-2023-40336, CVE-2023-40338, CVE-2023-40337, CVE-2023-40339
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.
DT228840 Unsigned signature field getting recognized as signed when line runs through field X X
DT236685 Documents with large tables fail with maximum recursion depth exceeded in comparison X X
DT237956 Accessibility - JAWS Reader can't tab to cancel Training X X
DT237960 Runtime application only shows first ten columns of a table X X
DT237963 Accessibility - JAWS Reader does not select the Project Import radio buttons X X
DT237965 The Show table feature in the verify client should display the table in read-only mode 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.
DT224799 Messages sent to topics related to Kafka services within the first 5 minutes after a version is created, installed, or imported might not be processed
DT228407 IBM Business Automation WorkflowCase administration (BAWAdmin) client doesn't open in Workflow center

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT215116 CVE-2023-33858 REFLECTED CROSS-SITE SCRIPTING IN PROCESS ADMIN CONSOLE X
DT225151 SECURITY APAR DT225151 - CVE-2021-33813 MAY AFFECT CUSTOM APPS IN IBM BUSINESS AUTOMATION WORKFLOW X
DT224071 SECURITY APAR - MULTIPLE VULNERABILITIES IN SNAPPY-JAVA MAY AFFECT BAW EVENT EMMITERS X
DT223183 Case Builder saves and loads solutions from an incorrect project area in a CP4BA Workflow Authoring cluster
DT223725 PROCESS ADMIN CONSOLE DOES NOT DISPLAY WEB SERVICE SERVER IN SERVERS TAB
DT224070 YOU SEE ERROR CWTBG0019E: UNEXPECTED EXCEPTION DURING EXECUTION. EXCEPTION INFORMATION: 'NULL' IN PROCESS MONITOR PAGE OF PROCESS ADMIN CONSOLE
DT224799 Messages sent to topics related to Kafka services within the first 5 minutes after a version is created, installed, or imported might not be processed
DT227809 THE TOTAL NUMBER OF ITEMS IS NOT LISTED AS AN OPTION FOR THE PAGE SIZE IN PROCESS ADMIN CONSOLE
DT228408 Remove the useless case_workitem_search_in_es parameter from CR template
DT228650 SNAPSHOT DEPLOYMENT FAILS WITH NULLPOINTEREXCEPTION
DT228796 Pods do not restart automatically when internal certificates are renewed

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.
DT222723 THERE ARE NO SECONDS IN DATE TIME EDITOR IN THE SIMULATION EDITOR
DT225197 SLOW PERFORMANCE WHEN DEBUGGING A RULESET
DT225452 MISSING ARTIFACTS IN DECISION CENTER AFTER DATABASE MIGRATION
DT233519 DC LDAP SYNC FAILS DUE TO 'BRM.LOCK' ERROR

Back to top

User Management Service
Known Issue Title Sec. Cont. B.I.
DT225643 SEARCHING FOR USERS OR GROUPS WITH SPECIAL CHARACTERS IS NOT SUPPORTED IN PROCESS ADMIN CONSOLE

Back to top

Workflow Process Service
Known Issue Title Sec. Cont. B.I.
DT215116 CVE-2023-33858 REFLECTED CROSS-SITE SCRIPTING IN PROCESS ADMIN CONSOLE X
DT225151 SECURITY APAR DT225151 - CVE-2021-33813 MAY AFFECT CUSTOM APPS IN IBM BUSINESS AUTOMATION WORKFLOW X
DT224071 SECURITY APAR - MULTIPLE VULNERABILITIES IN SNAPPY-JAVA MAY AFFECT BAW EVENT EMMITERS X
DT223725 PROCESS ADMIN CONSOLE DOES NOT DISPLAY WEB SERVICE SERVER IN SERVERS TAB
DT224070 YOU SEE ERROR CWTBG0019E: UNEXPECTED EXCEPTION DURING EXECUTION. EXCEPTION INFORMATION: 'NULL' IN PROCESS MONITOR PAGE OF PROCESS ADMIN CONSOLE
DT224799 Messages sent to topics related to Kafka services within the first 5 minutes after a version is created, installed, or imported might not be processed
DT227809 THE TOTAL NUMBER OF ITEMS IS NOT LISTED AS AN OPTION FOR THE PAGE SIZE IN PROCESS ADMIN CONSOLE
DT228650 SNAPSHOT DEPLOYMENT FAILS WITH NULLPOINTEREXCEPTION

Back to top

Known Limitations

Document change history

  • 31 August 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":"23.0.1"}]

    Document Information

    Modified date:
    07 November 2023

    UID

    ibm17025263

    Page Feedback