Capability storage requirements

Cloud Pak for Business Automation (CP4BA) components require persistent volumes to be provided as either Read Write Once (RWO) or Read Write Many (RWX) persistence. The persistence type depends upon the type of workload that they support.

CP4BA components that use block storage do not require the storage provider to perform cross-Availability Zone (AZ) replication when they run in a multi-replica mode because they include their own built-in replication. For more information, see Availability of stored data.

Block storage is suitable for databases and other data storage systems that require high-performance persistence, like MongoDB, Db2 and OpenSearch. RWO persistent volumes are often provisioned for databases and indexed workloads. Components that depend on RWX file storage rely on the storage provider to replicate across AZs. When possible, S3 storage is the preferred persistence for read-write-many scenarios as it is easily replicable by the storage provider.

Note: None of the CP4BA components require “raw block device” storage. In Kubernetes terms, the RWO storage is mounted into the pod as a directory inside the container that uses a Volume Mode of Filesystem.
The following tables provide details on different aspects of the storage requirements.
Table 1. Storage type requirements
Component RWO single-zone

(For example, EBS)

RWX

(replicated File)

S3

(replicated object storage)

Platform UI (Zen) * Yes (EDB Postgres **) Yes (Zen usermgmt - file system)  
Cloud Pak foundational services Yes (MongoDB **)    
Automation Decision Services Yes, optional (MongoDB) Yes, optional (archive storage for runtime)  
Automation Document Processing Yes, optional (MongoDB) Yes (5 different components)  
Automation Workstream Services * Yes (Liberty JMS) Yes (2 different components)  
Business Automation Application   Yes  
Business Automation Insights * Yes (Kafka ** and OpenSearch **) Yes  
Business Automation Navigator   Yes  
Business Automation Studio * Yes (Liberty JMS) Yes  
Business Automation Workflow Yes (Liberty JMS) Yes  
FileNet Content Manager   Yes (6 different components) Yes (optional document content store)
Operational Decision Manager   Yes (2 optional scenarios)  
Resource Registry   Yes  
Workflow Process Service Authoring * Yes (Liberty JMS, Postgres) Yes  
Note:

* Component requires both RWO and RWX for different purposes.

** Native HA is recommended over multi-instance due to storage simplicity.

The following table lists the storage type and disk space requirements for production deployments. Ranges are for small to large environments.

The following table also provides storage requirements for production deployments. Kubernetes access modes include Read Write Once (RWO), Read Write Many (RWX), and Read Only Many (ROX).

Table 2. Storage space requirements
Capability or runtime Storage type Disk space Access mode Number of persistent volumes for non-HA/HA Posix compliance
Automation Decision Services [optional] mongo_embedded: File or Block

[optional] runtime storage: File

50 GB   1 (non-HA)

1 (shared)

Posix compliance needed

Posix compliance not needed

Automation Document Processing File

Block (for mongo)

64 GB  
  • 1 for CDS
  • 3 for CDRA
  • 2 for CPDS
  • 7 for ViewOne
  • 3 for Gitgateway
  • 1 for mongo
  • (Optional) 2 for Document Processing engine
Posix compliance needed
Automation Workstream Services File 9 GB RWX 4 for Workflow Server (log, dump, messaging, file) Posix compliance not needed
Business Automation Application File Application Engine: 50 MB   1 Posix compliance not needed
Business Automation Insights File

Block (mandatory for OpenSearch)

Flink: 20 GB
  • Flink using OpenSearch snapshot storage: 30 GB
  • Flink using OpenSearch data storage: 10 GB

Sizing depends on the size of the projects.

  • Kafka: 2 GB x Event rate x Event size x retention duration x 1.10 x replica
  • Flink: 10 GB + 2 x Event rate x event size x average duration of event x replica
  • OpenSearch: Event rate x Event size x retention duration x (replicas +1)
    Posix compliance not needed
Business Automation Navigator File     6 for BAN Posix compliance not needed
Business Automation Studio File

File

2 - 6 GB  
  • 1 for jms
  • 4 (playback, dump, index, log)
Posix compliance not needed
Business Automation Workflow with or without Automation Workstream Services File

File

Workflow Runtime: 21 GB

Workflow Authoring: 39 GB

RWO

RWX

Workflow Runtime
  • 4 for Workflow Server (log, dump, messaging, file)
  • 3 for machine learning
Workflow Authoring
  • 1 for jms
  • 9 (3 for machine learning, 2 for Process Federation Server dump/log, 4 for Workflow Authoring log/dump/index/file)
Posix compliance not needed
Process Federation Server File 6 GB RWO 2 for Process Federation Server Posix compliance not needed
FileNet Content Manager File Component logs and configuration information: 500 MB for each component.

Temporary working space: Workload dependent, with a minimum of 1 GB for each component.

CPE and CSS content and index stores: Size of the content elements your users store/index, which grows over time.

 
  • 6 for CPE
  • 5 for CSS
  • 2 for GraphQL
  • 3 for Task Manager (TM)
  • 2 for CMIS
  • 2 for ExtShare
Posix compliance not needed
Operational Decision Manager [optional] File For product customization

[optional] DB support to retrieve jdbc driver

10 - 100 GB

If the database is outside the cluster, the size of internal storage is reduced to 1 GB.

  1 (non-HA)

1 (non-HA)

Posix compliance not needed

Posix compliance not needed

Resource Registry File Resource Registry: 5 - 16 GB   1 Posix compliance not needed
Workflow Process Service Authoring File 2 – 6 GB  
  • 1 for jms
  • 1 for EDB PostgreSQL if you are using it
  • 4 for authoring file, dump, index, log
Posix compliance not needed
Note: For information about sizing and storage options for the foundational services, see Hardware requirements and recommendations and Storage options.

The following table shows an example of CP4BA storage in the public cloud on AWS.

Table 3. Storage example of AWS
Component AWS EBS

(Single-zone block RWO)

AWS EFS

(replicated File RWX)

AWS S3

(Replicated object storage)

AWS FSx ONTAP

(offers replicated RWO, RWX)

OpenShift Data Foundation

(offers replicated RWO, RWX)

Portworx

(offers replicated RWO, RWX)

Platform UI (Zen) Yes Yes   Yes Yes Yes
Cloud Pak foundational services Yes Yes   Yes Yes Yes
Automation Decision Services Yes, optional (MongoDB) Yes, optional (archive storage for runtime)   Yes, optional Yes, optional Yes, optional
Automation Document Processing Yes, optional (MongoDB) Yes (5 different components)   Yes Yes Yes
Automation Workstream Services Yes (Liberty JMS) Yes (2 different components)   Yes Yes Yes
Business Automation Application   Yes   Yes Yes Yes
Business Automation Insights Yes (Kafka and OpenSearch) Yes   Yes Yes Yes
Business Automation Navigator   Yes   Yes Yes Yes
Business Automation Studio Yes (Liberty JMS) Yes   Yes Yes Yes
Business Automation Workflow Yes (Liberty JMS) Yes   Yes Yes Yes
FileNet Content Manager   Yes (6 different components) Yes (optional document content store) Yes Yes Yes
Operational Decision Manager   Yes (2 optional scenarios)   Yes (2 optional scenarios) Yes (2 optional scenarios) Yes (2 optional scenarios)
Resource Registry   Yes   Yes Yes Yes
Workflow Process Service Authoring Yes (Liberty JMS, Postgres) Yes   Yes Yes Yes
Note:

AWS EFS requires NFS subdir external provisioner.

Use the Trident ontap-nas driver.

ODF is not currently supported for use with the ROSA managed OpenShift platform, see ODF support on ROSA.

Some components require both RWO and RWX for different purposes.

The following table shows an example of CP4BA storage in the public cloud on Azure.

Table 4. Storage example of Azure
Component Azure Disks

(single-zone or replicated RWO)

Azure Files

(replicated File RWX)

Azure Blob

(replicated object storage)

OpenShift Data Foundation

(offers replicated RWO, RWX)

Portworx

(offers replicated RWO, RWX)

Platform UI (Zen) Yes Yes   Yes Yes
Cloud Pak foundational services Yes     Yes Yes
Automation Decision Services Yes, optional (MongoDB) Yes, optional (archive storage for runtime)   Yes, optional Yes, optional
Automation Document Processing Yes, optional (MongoDB) Yes (5 different components)   Yes Yes
Automation Workstream Services Yes (Liberty JMS) Yes (2 different components)   Yes Yes
Business Automation Application   Yes   Yes Yes
Business Automation Insights Yes (Kafka and OpenSearch) Yes   Yes Yes
Business Automation Navigator   Yes   Yes Yes
Business Automation Studio Yes (Liberty JMS) Yes   Yes Yes
Business Automation Workflow Yes (Liberty JMS) Yes   Yes Yes
FileNet Content Manager   Yes (6 different components) Yes (optional document content store) Yes Yes
Operational Decision Manager   Yes (2 optional scenarios)   Yes (2 optional scenarios) Yes (2 optional scenarios)
Resource Registry   Yes   Yes Yes
Workflow Process Service Authoring Yes (Liberty JMS, Postgres) Yes   Yes Yes
Note:

Use the Azure Files NFS driver, and not the SMB driver.