Jump to: navigation, search

Genesys Info Mart Support for Business Continuity

Genesys Info Mart can be deployed in an environment that requires support for Business Continuity. The two approaches discussed in this wiki document help to preserve reporting data in the event of a loss of a particular site: active-active architecture and active-standby architecture. Database replication of the Genesys Info Mart database that is achieved through Oracle GoldenGate plays a crucial role in the active-standby architecture. Database replication is not required in the active-active architecture.

Business Continuity provides protection to enterprise operations in the following situations:

  • Disaster Recovery (Site Failure)
  • Networking Failure Between Sites
  • Graceful Migration

For information about these functions, refer to the Business Continuity section of the SIP Server High-Availability Deployment Guide.

Genesys Info Mart supports Business Continuity by providing contact-center reporting in all three scenarios. In other words, the setup described in this document ensures that Genesys Info Mart continues to gather and process data when one of the sites fails, a network connection fails between the sites, or another Genesys component that supports Graceful Migration is migrated in this manner.

Note, however, that Genesys Info Mart, as an individual component, only supports the Disaster Recovery (Site Failure) scenario. For this reason, instructions in this document do not cover the switchover between Genesys Info Mart instances during a networking failure or for the purposes of application migration.

The Genesys Info Mart setup that is described in this document can be used in conjunction with the Genesys SIP Business Continuity solution.

Terminology Note

Throughout this document, the word database has different meaning, depending on the context. It may refer to Genesys components, such as "Interaction Database" or "Info Mart database." It may also be used in reference to general relational database management system (RDBMS) concepts and procedures, such as "database export" or "database replication." Where it is significant to refer to a particular organization of tables, views, indexes, and other database objects, the term database schema is used. Where it is significant to refer to the RDBMS that manages database files, the term database instance is used. This terminology may not necessarily match the terminology used by leading RDBMS vendors.

This page was last edited on October 5, 2018, at 16:00.
Comments or questions about this documentation? Contact us for support!