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 environment

The following describes the supported operating environment for IBM Cloud Pak for Integration release 2020.2.1;
  • Red Hat® OpenShift Container Platform
    • Version 4.4.4 or later (with 4.4.13 or later preferred)
    • Version 4.5 or later
  • Common Services 3.4.x or later (with 3.4.3 or later preferred)
  • x86 platform
  • Multi-zone and single-zone deployments where appropriate storage providers are available to support that deployment model

Note that since IBM Cloud Pak for Integration requires Red Hat OpenShift Container Platform, the Cloud Pak is not available in other environments, such as Docker or open-source Kubernetes distributions.

For more information about installing Red Hat OpenShift Container Platform, see OpenShift Container Platform 4.4 Documentation.

To ensure that the cluster is set up correctly, access the Red Hat OpenShift Container Platform web console. The web console can be found by running this command: oc -n openshift-console get route

You will get output similar to the following example:

openshift-console          console             console-openshift-console.apps.new-coral.purple-chesterfield.com                       console                  https   reencrypt/Redirect     None
In the example above, the URL for the console is https://console-openshift-console.apps.new-coral.purple-chesterfield.com. Copy the URL in your browser and check the result.

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. For information about high availability requirements, see High Availability.

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

Required by the base product.

8.125 cores 35.64 Gb 120 Gb
Platform Navigator

The base product.

0.5 cores 640 Mb None needed
Asset Repository

Optional asset management capability.

3.6 cores 5 Gb 3 Gb
Operations Dashboard

Optional transaction tracing capability.

6 cores 16 Gb 16 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.

8.8 cores 9.1 Gb 1.5 Gb
Application Integration Dashboard

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

1 core 4 Gb 2.3 Gb
Application Integration Designer

This capability is provided by deploying IBM App Connect Enterprise Designer.

1 core 5.75 Gb 30 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 in the IBM Cloud Pak for Integration use persistent storage to provide reliable and resilient storage of state data. The cluster administrator must provide appropriate storage classes that meet the requirements of the respective integration component.

The following recommended storage providers that have been validated across all the components of IBM Cloud Pak for Integration;

  • OpenShift Container Storage version 4.x from version 4.2 or higher
  • IBM Cloud Block storage and IBM Cloud File storage

Other storage providers are also recommended for specific components. Refer to the notes for that component in the following table.

Note: The internals of the storage provider components are not supported directly by the IBM Cloud Pak for Integration support team. Users must ensure that they have an appropriate support arrangement, so in the event that an issue is identified within a storage provider, they can engage with the provider directly.

Table 2. Storage requirements
Integration capability Storage type

(block or file)

Access mode

(see note 1)

Notes
Asset Repository File for asset data

Block for CouchDB

File RWX

Block RWO

Operations Dashboard Block RWO 10 IOPS/GB performance
API Lifecycle and Management Block RWO See API Connect v10 deployment requirements and Section 10 of API Connect v10 deployment whitepaper for details.

Minimum: 4 IOPS/GB, Recommended: 10 IOPS/GB

Application Integration Dashboard  File RWX See AppConnect Dashboard storage for details.

1 IOPS/GB

Application Integration Server  N/A N/A N/A
Application Integration Designer  Block RWO See AppConnect Designer storage for details.
Aspera High Speed File Transfer  File RWX
Event Streams  Block RWO See Event Streams storage for details.
MQ File RWX

Notes

  1. Kubernetes Access Modes include Read Write Once (RWO), Read Write Many (RWX) and Read Only Many (ROX)