Planning and initial preparation

Decide on endpoint, host, and namespace names. Prepare your Cloud Pak for Integration environments for 2DCDR API Connect.

1. Decide on naming. Both data centers must use the same names for:
   • API Connect namespace.
   • API Connect Cluster CR name. Also known as the API Connect instance name, and referred to in this document as <apic-instance-name>.
   • Management subsystem endpoints
     • cloudManagerEndpoint
     • apiManagerEndpoint
     • platformAPIEndpoint
     • consumerAPIEndpoint
     • consumerCatalogEndpoint
   • Portal subsystem endpoints
     • portalAdminEndpoint
     • portalUIEndpoint

   Important: Each data center must use a different backup path for your management database backups. For portal database backups each data center must use the same backup path. For more information, see Backup and restore requirements for a 2DCDR deployment.
2. Create a namespace for your API Connect deployment in both data centers.
   The API Connect namespace must be the same in both data centers, set it with:

   oc create ns <namespace>

3. Install the API Connect operators in both your data centers. See Installing operators. Return here when the operators are installed.
4. Decide which data center will start as the active and which will start as the warm-standby.
5. On the CLI of the active data center, where you run oc commands, create a directory called 2dcdr-active-yamls. On the CLI of the warm-standby data center, create a directory called 2dcdr-ws-yamls.