Compute resources for development environments
Resource requirements for operators and deployed instances of IBM Cloud Pak® for Integration in development environments.
Resource requirements for Cloud Pak for Integration
This table indicates the minimum required values for installation of Cloud Pak for Integration in various environments.
| Use case | Nodes | Cores per node | Memory request (GiB) |
|---|---|---|---|
| Minimal proof of concept environment with no failover | 1 | 24 | 24 |
| Small production environment with multiple workers for failover | 3 | 8 | 24 |
| Large production environment with multiple components installed | 3 | 32 | 64 |
Notes:
A minimal proof of concept environment does not provide failover (because there is only one node). The value provided here for "cores per node" is the mimimum.
A small production environment provides failover, but limited space for workload.
A large production environment provides both failover and ample space for workload.
Resource requirements for operators
Cloud Pak for Integration operators must be installed before the associated integration capabilities can be deployed. This table lists the minimum resources for operators that should be factored in when sizing a cluster:
| Operator | CPU request (cores) | CPU limit (cores) | Memory request (GiB) | Memory limit (GiB) | Disk space (GB) |
|---|---|---|---|---|---|
| IBM Cloud Pak for Integration | 0.4 | 0.9 | 0.5 | 1.8 | None |
| IBM Automation Foundation assets | 0.4 | 1.3 | 0.7 | 1.5 | None |
| IBM Cloud Pak for Integration Operations Dashboard | 0.1 | 0.2 | 0.1 | 1 | None |
| IBM API Connect | 0.8 | 3.5 | 0.6 | 3.2 | None |
| IBM MQ | 1 | 1 | 1 | 1 | None |
| IBM Event Streams | 0.2 | 1 | 1 | 1 | None |
| IBM App Connect | 0.2 | 2 | 0.3 | 1.5 | None |
| IBM DataPower Gateway | 0.5 | 2 | 0.5 | 2 | None |
| IBM Aspera HSTS | 0.3 | 0.7 | 0.3 | 0.7 | None |
CPU (cores) and Memory values represent the total amount of CPU and memory required for the cluster as whole, not the required amount per node.
Resource requirements for deployed instances of capabilities
This table lists the requirements for deployed instances of integration capabilities. Below the table is a list of detailed provisioning information for each capability.
| Capability (operator name, for reference) | CPU request (cores) | CPU limit (cores) | Memory request (GiB) | Memory limit (GiB) | Disk space (GB) |
|---|---|---|---|---|---|
| Platform UI (IBM Cloud Pak for Integration) | 2.2 | 11.1 | 4.6 | 16 | 40 |
| Automation assets (IBM Automation Foundation assets) | 0.7 | 0.7 | 1 | 1 | 0.4 |
| Integration tracing (Operations Dashboard) | 8.6 | 8.6 | 16 | 16 | 12 |
| Integration tracing, collector and agent | 0.5 | 0.8 | 0.8 | 0.8 | None |
| API management (IBM API Connect) | 4.3 | 28 | 20 | 67 | 280 |
| Event Endpoint Management (IBM API Connect) | 3.6 | 19.4 | 10 | 48 | 331 |
| Messaging (IBM MQ) | 0.5 | 0.5 | 1 | 1 | 2 |
| Event streams (IBM Event Streams) | 2.8 | 12.2 | 6 | 14 | 2 |
| Application integration Dashboard (IBM App Connect) | 0.1 | 0.75 | 0.2 | 1 | 2.3 |
| Application integration Designer (IBM App Connect) | 1.6 | 7.2 | 2.9 | 7.4 | 10 |
| Gateway (IBM DataPower Gateway) | 1 | 1 | 4 | 4 | None |
| High-speed transfer server (IBM Aspera HSTS) | 5.2 | 52 | 5 | 30 | 120 |
| Foundational services (IBM Cloud Pak Foundational services) | 5.2 | 21 | 8.5 | 16 | 60 |
CPU (cores) and Memory values represent the total amount of CPU and memory required for the cluster as whole, not the required amount per node.
Provisioning details for capabilities
- Platform UI
Centralized management of Cloud Pak for Integration capabilities.
- Asset sharing and reuse
Capability provided by deploying Automation assets.
- Integration tracing for troubleshooting
Capability provided by deploying Operations Dashboard.
- Integration tracing and troubleshooting (collector and agent)
Provided for each component pod that is traced with the Operations Dashboard.
- API management
Capability provided by deploying IBM API Connect. For specific requirements, see IBM API Connect system requirements.
- Event Endpoint Management
Capability provided by deploying IBM API Connect operator.
- Messaging
Capability provided by deploying IBM MQ. For specific requirements, see IBM MQ system requirements.
- Event streams
Capability provided by deploying IBM Event Streams. For specific requirements, see IBM Event Streams system requirements and disk space for persistent volumes.
- Application integration Dashboard
Capability provided by deploying IBM App Connect Enterprise. For specific requirements, see App Connect Dashboard reference.
- Application integration with Designer
Capability provided by deploying IBM App Connect Enterprise.
- Gateway
Capability provided by deploying IBM DataPower Gateway. For specific requirements, see IBM DataPower Gateway system requirements.
- High-speed transfer server
Capability provided by deploying IBM Aspera HSTS. For specific requirements, see Resource requirements.
- Foundational Services (platform UI, monitoring, licensing, managing users)
IBM Cloud Pak foundational services that are included in the Cloud Pak. These values correspond to the "small" profile in Hardware requirements and recommendations for foundational services, which is recommended for both high availability (HA) and non-HA scenarios.