Enabling Geo-Redundancy

Last Updated : Feb 28, 2023 |

Each data center must contain all components on which POM depends.

Geo-Redundancy in POM can only be enabled with MSSQL database configured with the AlwaysOn feature. The MSSQL database high availability nodes configured with AlwaysOn must be located on different data centers that are intended to be configured for Geo-Redundancy. The POM database must be a part of Availability Database and must be synchronized with all other database nodes.

For example, if two data centers are planned for configuring Geo-Redundancy, each data center must contain:

  • Components such as Experience Portal, App Servers, Communication Manager, Call Management System, Media Processing Platform, and System Manager.

  • MSSQL Database with AlwaysOn feature, and high-availability node on another data center.

  • MSSQL Availability Group Listener.

Note:

If two hundred campaigns are going to run on the Geo system, set the value as three hundred for parameter hikari_PIMCM in the file PIMHibernate.cfg.xml. The file is located at POM_Home/config on Proactive Outreach Manager server. The default value of the environment variable POM_Home is /opt/Avaya/avpom/POManager.