Installing a two data center deployment with Cloud Pak for Integration

How to deploy a two data center disaster recovery (2DCDR) deployment on OpenShift with Cloud Pak for Integration.

Introduction

Ensure that you understand the concepts of 2DCDR in API Connect. For more information, see Two data center warm-standby deployment on Kubernetes and OpenShift.

Familiarize yourself with the Cloud Pak for Integration installation instructions linked from Deploying on OpenShift and Cloud Pak for Integration.
Note: During a 2DCDR installation, the management subsystem remains in a Warning state until the management subsystems in both data centers synchronize their databases. The management Warning status prevents the deployment and registration of the portal, gateway, and analytics subsystems. When the management subsystem databases are synchronized and both in Ready state, the deployment and registration of the other subsystems starts.

Prerequisites

The prerequisites for a 2DCDR deployment with Cloud Pak for Integration are as follows.

  • The management and portal endpoints must be the same on both data centers.
  • The network latency between data centers must be no more than 80 ms.
  • The management cluster in each data center must use the same encryption secret.
  • The portal cluster in each data center must use the same encryption secret.
  • The ingress-ca certificate must be the same on both data centers.
  • The API Connect namespace name must be the same in both clusters.
  • The APIConnectCluster CR name must be identical on both clusters.
Restrictions: