System requirements
The administrator must make sure that the target cluster on OpenShift Container Platform has the capacity for all the capabilities that you plan to install.
The deployment profile to use is starter
(sc_deployment_profile_size=starter). The
starter
profile cannot be used for production usage.
Profile | Description | Scaling (per 8-hour day) | Minimum number of worker nodes |
---|---|---|---|
Starter | For environments that are used by a 2 developers and up to 5 users. This profile is for first-time users and useful for demonstrations or evaluation. |
|
3 |
The cluster hardware architecture can be Intel (amd64 or x86_64 the 64-bit edition for Linux® x86) on all platforms, Linux on IBM Z, or Linux on Power.
The following table shows the minimum requirements for each Cloud Pak capability. Storage includes all persistent volumes (PVs) and all the databases that are needed.
Capability / Pattern | vCPU | Memory | Storage |
---|---|---|---|
Automation Decision Services | 3 master nodes with 4 vCPUs 3 worker nodes with 4 CPUs |
16 Gi on each node | 20 GB |
Automation Document Processing |
3 master nodes with 4 vCPUs 3 worker nodes with 16 vCPUs |
3 master nodes, 16Gi on each node 3 worker nodes, 32Gi on each node |
100 GB |
Business Automation Application | 3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
8 Gi on each node | 60 GB |
Business Automation Workflow and Automation Workstream Services | 3 master nodes with 4 vCPUs 3 worker nodes with 8 vCPUs |
16 Gi on the master node 24 Gi on each worker node |
300 GB |
IBM FileNet® Content Manager | 3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
16 Gi on each node | 70 GB |
Operational Decision Manager | 3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
4 Gi on each node | 20 GB |
Platform foundation For more information about foundational services requirements, see Hardware requirements and recommendations for foundational services. |
3 master nodes with 4 vCPUs 3 worker nodes with 4 vCPUs |
8 Gi on each node | 20 GB per pod |