System Requirements

System requirements for IBM® Cloud Pak for Integration

Overview

Ensure that your servers meet the minimum hardware and software requirements for IBM Cloud Pak for Integration.

Operating systems

The following table lists supported platforms.

Table 1. Supported operating systems
Platform Operating system
Linux® 64-bit
  • Red Hat OpenShift Container Platform 4.2

Minimum system requirements

For non-production workloads, worker nodes should be added and configured to provide a combined total number of cores, memory, and disk space to meet the minimum requirements in the table below.

Table 2. Minimum system requirements
Integration capability CPU Memory Disk space
Common Services

Required by the base product.

8 cores 32 Gb 40 Gb
Platform Navigator

The base product.

0.25 cores 256 Mb None needed
Asset Repository

Optional asset management capability.

4.25 cores 8.5 Gb 2 Gb
Operations Dashboard

Optional transaction tracing capability.

5.95 cores 1.5 Gb 12 Gb
API Lifecycle and Management 

This capability is provided by deploying IBM API Connect. For specific requirements regarding this capability, see the IBM API Connect system requirements

12 cores 48 Gb 550 Gb
Queue Manager 

This capability is provided by deploying IBM MQ. For specific requirements regarding this capability, see the IBM MQ system requirements

1 core 1 Gb 2 Gb
Event Streams 

This capability is provided by deploying IBM Event Streams. For specific requirements regarding this capability, see the IBM Event Streams system requirements

16.2 cores 25.2 Gb 1.5 Gb
Application Integration 

This capability is provided by deploying IBM App Connect. For specific requirements regarding this capability, see the IBM App Connect system requirements

1 core 4 Gb 2.3 Gb
DataPower Gateway 

This capability is provided by deploying IBM DataPower Gateway. For specific requirements regarding this capability, see the IBM DataPower Gateway system requirements

4 core 4 Gb No minimum
High Speed File Transfer 

This capability is provided by deploying IBM Aspera. For specific requirements regarding this capability, see the IBM Aspera system requirements

4 cores 4 Gb

This is a minimum configuration. Your system requirements will change based on actual usage.

File systems and storage

The Integration capabilities provided by IBM Cloud Pak for Integration should use persistent storage. The cluster administrator must provide a storage class or persistent volume that can be referenced by the respective integration deployment.

 
Table 3. Storage requirements
Integration capability Storage type (block or file) Access mode (Read Write Once RWO, Read Write Many RWX, Read Only Many ROX) IOPs requirement
Asset Repository File + Block RWX + RWO
Operations Dashboard Block RWO 10 IOPS/GB
API Lifecycle and Management Block RWO Minimum: 4 IOPS/GB Recommended: 10 IOPS/GB
MQ File RWX Affected by other limits applied to the file system (such as limiting the number of file locks in AWS EFS). See Queue Managers.
Event Streams  File and/or Block; See Note 1 RWO  
Application Integration Dashboard  File RWX 1 IOPS/GB
Application Integration Server (no MQ)  N/A N/A
Application Integration Server (with MQ)  File RWX Same as MQ
High Speed File Transfer  File RWX

Notes

  1. Event streams requires RWO storage volumes. It is recommended that you use either block storage, formatted by Kubernetes as ext4 or one of the tested filesystem options. Event Streams has been tested using the following storage options. See Event Streams storage.

The Overview tab of the Helm chart presented during installation of each of the integration capabilities provides information regarding specific storage solutions and versions needed for that capability.