Architecture

From Genesys Documentation
Jump to: navigation, search
This is a draft page; the published version of this page can be found at PEC-OU/Current/CXCPEGuide/Architecture.


Learn about CX Contact architecture.

Related documentation:

CX Contact is set of microservices that run in Kubernetes containers, each scalable in N+1 horizontal mode. It has a state-of-the-art user interface (UI) and middleware components, and uses Genesys servers on the back end (Configuration Server, Outbound Contact Server (OCS), and Stat Server). Genesys Web Services (GWS) is a prerequisite.

CX Contact Compliance Manager and Dial Manager support Horizontal Pod Autoscaler (HPA).

The diagram below shows the architecture of the CX Contact service. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level

#mintydocs_link must be called from a MintyDocs-enabled page (Draft:PEC-OU/Current/CXCPEGuide/Architecture).

page:

PE engage-cloud architecture.png



Core components

The table below provides a description of each of the CX Contact core components:

Component Description
List Builder *Responsible for operations related to lists.

*Creates contact lists and suppression lists in Configuration Manager.

*Reads Compliance data from a compliance data provider.

*Copies files from FTP to NFS for List Builder consumption.

List Manager *Responsible for operations related to lists.

*Creates contact lists and suppression lists in Configuration Manager.

*Reads Compliance data from a compliance data provider.

*Copies files from FTP to NFS for List Builder consumption.