Requirements

Last Updated : Oct 12, 2023 |

The following are the requirements for enabling Geo-Redundancy in POM:

  • Install POM in the CCElite mode.

  • Use MSSQL supported database version and ensure that the database is pre-configured with its AlwaysOn feature and Manual Failover.

  • Use MSSQL in asynchronous commit mode as the communication is performed over the WAN between Data Center -1 and Data Center -2.

  • POM supports Geo-Redundancy on Standard/Enterprise edition of MSSQL.

  • Ensure that the primary instance of the MSSQL database is on the active data center.

  • Configure MS SQL Availability Group Listener.

  • Ensure that the organizations, users, and zones available on Experience Portal in Data Center 1 are also created on Experience Portal in Data Center 2.

  • Configure EPM in the ACTIVE-ACTIVE deployment and ensure that the licenses are configured on both sites.

    • Note that Experience Portal is deployed as 2 independent systems. One Experience Portal system per data center. ACTIVE-ACTIVE refers to the way Experience Portal licenses are handled and that both systems can handle traffic in inbound scenarios.

  • Configure Communication Manager in Data Center 1 with Surviable Core Server (ESS) in Data Center 2.

  • Configure Call Management System in the High Availability (HA) mode.

  • Configure Application Enablement Services in the GRHA mode or ensure that Application Enablement Services is available in both data centers.

  • In a multi-site POM setup, install the POM certifcates on each other's trust store. For more information, see Exchanging POM certificates in a multiple site setup.

    POM Geo-Redundancy with MSSQL Always On High Availability requires:

  • A local Availability Group on each Data Center, grouping the local databases of the Data center.

  • A Distributed Availability Group (AG) connecting both Data centers in Asynchronous mode.

  • POM servers on each Data center must point to their local AG to support local Database failover within the local AG and not to the Distributed Availability Group (DAG).

  • Note:

    Pointing POM servers to the Distributed Availability Group (DAG) is not supported.