Architecture

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:

Explain the architecture of all services in the container. Note whether the service supports autoscaling. Link to "suite-level" Architecture page:

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

Include a logical architecture diagram. You'll need to work with the diagram team so that all Genesys Engage cloud private edition architecture diagrams are consistent.

MHachey:I took some of this content from the Help and some from the DG. Does the highlighted text apply to PE?

CX Contact is set of microservices that run in Docker 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.

MHachey: Does the CX Contact architecture support autoscaling? Also, do we have any content that describes the service in more detail, the REST API?, the CX Contact API?, Backend?