Planning

Prepare for your installation of IBM Cloud Pak® for Integration.

For known issues and workarounds, see Known limitations.
To obtain logs or open a support case, see Troubleshooting.

System requirements
Prior to installation, ensure that your servers meet the minimum hardware and software requirements for IBM Cloud Pak for Integration.
Licensing
This document provides information about licensing and entitlements for IBM Cloud Pak® for Integration.
Structuring your deployment
Get best practices for planning your installation of IBM Cloud Pak for Integration to fit your use case.
Node placement considerations
When a workload (such as IBM Cloud Pak for Integration) is deployed on the Red Hat OpenShift Container Platform, the OpenShift scheduler makes decisions about the optimal node in the cluster for each pod to run on.
Installing on a single node OpenShift (SNO) cluster
IBM Cloud Pak for Integration supports installations on single node OpenShift (SNO).
Cluster logging
IBM Cloud Pak for Integration supports both OpenShift cluster logging and user-defined logging solutions. For more information, see Installing and configuring cluster logging.
Cluster monitoring
Monitoring in IBM Cloud Pak for Integration can be done with IBM Instana or with the OpenShift monitoring stack.
Deploying custom images
This page describes support for custom images of IBM Cloud Pak for Integration components.
Disaster recovery
Disaster Recovery (DR) is the process of creating a copy of your [product] environment in a different cluster (and possibly in a different physical location) in order to restore service following an unrecoverable failure that impacts your main environment.
Additional Services
z/OS Connect Enterprise Edition is an available supplemental service that interoperates with this Cloud Pak.