Configuring Native HA CRR using the IBM MQ Operator

Native HA Cross-Region Replication (CRR) is configured using the QueueManager API, and advanced options are available using an INI file.

Note: This example uses an IBM® MQ Advanced license. From IBM MQ 9.4.2, IBM MQ licensed queue managers can also be configured to use Native HA CRR features by adding additional licenses to a queue manager. For more information, see Configuring Native HA and Cross-Region Replication on IBM MQ licensed Queue Managers by using the IBM MQ Operator.

Native HA CRR is configured by using .spec.queueManager.availability in the QueueManager API. The .spec.queueManager.availability.type field must be set to NativeHA. The .spec.queueManager.availability.nativeHAGroups.local.role field is set to Live or Recovery to specify the role of the local group.

You specify the details of the remote group in the configuration in the .spec.queueManager.availability.nativeHAGroups.remotes section. You give the hostname and port of the OpenShift route used by the remote group where data will be replicated to. The live group must include the remotes section at the minimum to be able to replicate to the recovery group. The recovery group must include the remotes section in order to be able to replicate back to the other site if it ever becomes live. (See Native HA CRR switchover and failover.)

Under .spec.queueManager.availability, you can also configure a TLS secret and ciphers to use between queue manager instances when replicating. This is strongly recommended, and a step-by-step guide is available in Example: Configuring Native HA using the IBM MQ Operator.

You must configure a TLS secret and ciphers to use between the live and recovery groups when replicating. You can use the same secret as specified for replication between instances, or you can specify another secret for this purpose.