Draft:PEC-OU/Current/CXCPEGuide/Architecture - Revision history

WikiSysop: Redirected page to Draft:PEC-OU/Current/CXCPEGuide/Architecture new

2022-06-30T10:45:41Z

Redirected page to Draft:PEC-OU/Current/CXCPEGuide/Architecture new

Arjun.D.IX at 10:48, January 27, 2022

2022-01-27T10:48:18Z

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:34:34Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Mary.hachey@genesys.com at 13:40, October 26, 2021

2021-10-26T13:40:23Z

Mary.hachey@genesys.com at 19:46, August 24, 2021

2021-08-24T19:46:29Z

Mary.hachey@genesys.com at 13:03, August 24, 2021

2021-08-24T13:03:19Z

Mary.hachey@genesys.com at 13:02, August 24, 2021

2021-08-24T13:02:19Z

Mary.hachey@genesys.com at 12:52, August 24, 2021

2021-08-24T12:52:16Z

Mary.hachey@genesys.com at 12:46, August 24, 2021

2021-08-24T12:46:17Z

Mary.hachey@genesys.com at 12:33, August 24, 2021

2021-08-24T12:33:38Z

← Older revision		Revision as of 10:45, June 30, 2022
Line 1:		Line 1:
−	~~{{PEArchitecture~~	+	#REDIRECT [[Draft:PEC-OU/Current/CXCPEGuide/Architecture_new]]
−	~~\|DisplayName=Architecture~~
−	~~\|Context=Learn about CX Contact architecture.~~
−	\|IntroductionText=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 supports Horizontal Pod Autoscaler (HPA) for Compliance Manager and Dial Manager.~~
−
−	The diagram below shows the CX Contact service architecture. For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level {{SuiteLevelLink\|architecture}} page:
−	~~\|Image=PE_engage-cloud_architecture.png~~
−	~~\|AltText=CX Contact private edition architecture diagram~~
−	~~\|Section={{Section~~
−	~~\|sectionHeading=Included services~~
−	~~\|anchor=CXCore~~
−	~~\|alignment=Vertical~~
−	~~\|structuredtext=The table below provides a description of the CX Contact included services:~~
−	~~{{{!}} class="wikitable"~~
−	~~{{!}}+~~
−	~~!Included service~~
−	~~!Description~~
−	~~{{!}}-~~
−	~~{{!}}List Builder~~
−	~~{{!}}~~
−	*Manages 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~~
−	~~{{!}}~~
−	*Manages 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.
−	~~{{!}}-~~
−	~~{{!}}Compliance Manager~~
−	~~{{!}}~~
−	*Manages dynamic compliance rules validation.
−	*Reads suppression entries from Redis and responds to OCS pre-validation requests.
−	~~{{!}}-~~
−	~~{{!}}Campaign Manager~~
−	~~{{!}}~~
−	*Manages operations related to campaigns.
−	*Executes preloading of campaigns. Processing is done in Outbound Database.
−	~~{{!}}-~~
−	~~{{!}}Job Scheduler~~
−	~~{{!}}Creates and invokes jobs at the right time, providing for automation of tasks.~~
−	~~{{!}}-~~
−	~~{{!}}Dial Manager~~
−	~~{{!}}Manages SMS and email interactions with Genesys Message Aggregation.~~
−	~~{{!}}-~~
−	~~{{!}}API Aggregator~~
−	~~{{!}}This is the entry point of APIs to CX Contact. Ensures APIs stay invariant when internal implementation changes.~~
−	~~{{!}}-~~
−	~~{{!}}User Interface (UI)~~
−	~~{{!}}A set of static HTML5 pages served by Nginx.~~
−	~~{{!}}}~~
−	~~\|Status=No~~
−	}}
−	~~\|Standalone=No~~
−	~~\|ComingSoon=No~~
−	~~\|PEPageType=e38fb4a6-02d6-48d0-a6f1~~-~~32635fb394bc~~
−	}}

@@ Line 13: / Line 13: @@
 |anchor=CXCore
 |alignment=Vertical
-|structuredtext=The table below provides a description of the CX Contact includes services:
+|structuredtext=The table below provides a description of the CX Contact included services:
 {{{!}} class="wikitable"
 {{!}}+

@@ Line 6: / Line 6: @@
 CX Contact supports Horizontal Pod Autoscaler (HPA) for Compliance Manager and Dial Manager.
-The diagram below shows the CX Contact service architecture. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level {{SuiteLevelLink|architecture}} page:
+The diagram below shows the CX Contact service architecture. For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level {{SuiteLevelLink|architecture}} page:
 |Image=PE_engage-cloud_architecture.png
 |AltText=CX Contact private edition architecture diagram

@@ Line 10: / Line 10: @@
 |AltText=CX Contact private edition architecture diagram
 |Section={{Section
-|sectionHeading=Core components
+|sectionHeading=Included services
 |anchor=CXCore
 |alignment=Vertical
-|structuredtext=The table below provides a description of each CX Contact core component:
+|structuredtext=The table below provides a description of the CX Contact includes services:
 {{{!}} class="wikitable"
 {{!}}+
-!Component
+!Included service
 !Description
 {{!}}-

@@ Line 4: / Line 4: @@
 |IntroductionText=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).
+CX Contact supports Horizontal Pod Autoscaler (HPA) for Compliance Manager and Dial Manager.
-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 {{SuiteLevelLink|architecture}} page:
+The diagram below shows the CX Contact service architecture. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level {{SuiteLevelLink|architecture}} page:
 |Image=PE_engage-cloud_architecture.png
 |AltText=CX Contact private edition architecture diagram

@@ Line 14: / Line 14: @@
 |alignment=Vertical
 |structuredtext=The table below provides a description of each of the CX Contact core components:
 {{{!}} class="wikitable"
 {{!}}+
@@ Line 22: / Line 21: @@
 {{!}}List Builder
 {{!}}
-*Responsible for operations related to lists.
+*Manages operations related to lists.
 *Creates contact lists and suppression lists in Configuration Manager.
 *Reads Compliance data from a compliance data provider.
@@ Line 29: / Line 28: @@
 {{!}}List Manager
 {{!}}
-*Responsible for operations related to lists.
+*Manages operations related to lists.
 *Creates contact lists and suppression lists in Configuration Manager.
 *Reads Compliance data from a compliance data provider.
@@ Line 36: / Line 35: @@
 {{!}}Compliance Manager
 {{!}}
-*Responsible for dynamic compliance rules validation.
+*Manages dynamic compliance rules validation.
-*Reads suppression entries from Redis and responds to OCS prevalidation requests.
+*Reads suppression entries from Redis and responds to OCS pre-validation requests.
 {{!}}-
 {{!}}Campaign Manager
 {{!}}
-*Responsible for operations related to campaigns.
+*Manages operations related to campaigns.
 *Executes preloading of campaigns. Processing is done in Outbound Database.
 {{!}}-
 {{!}}Job Scheduler
-{{!}}Responsible for creating and invoking jobs at the right time, providing for automation of tasks.
+{{!}}Creates and invokes jobs at the right time, providing for automation of tasks.
 {{!}}-
 {{!}}Dial Manager
-{{!}}Responsible for managing SMS and email interactions with Genesys Message Aggregation.
+{{!}}Manages SMS and email interactions with Genesys Message Aggregation.
 {{!}}-
 {{!}}API Aggregator

@@ Line 22: / Line 22: @@
 {{!}}List Builder
 {{!}}
-* Responsible for operations related to lists.
+*Responsible for operations related to lists.
-* Creates contact lists and suppression lists in Configuration Manager.
+*Creates contact lists and suppression lists in Configuration Manager.
-* Reads Compliance data from a compliance data provider.
+*Reads Compliance data from a compliance data provider.
-* Copies files from FTP to NFS for List Builder consumption.
+*Copies files from FTP to NFS for List Builder consumption.
 {{!}}-
 {{!}}List Manager
 {{!}}
-* Responsible for operations related to lists.
+*Responsible for operations related to lists.
-* Creates contact lists and suppression lists in Configuration Manager.
+*Creates contact lists and suppression lists in Configuration Manager.
-* Reads Compliance data from a compliance data provider.
+*Reads Compliance data from a compliance data provider.
-* Copies files from FTP to NFS for List Builder consumption.
+*Copies files from FTP to NFS for List Builder consumption.
 {{!}}-
 {{!}}
-{{!}}
+*Responsible for dynamic compliance rules validation.
 {{!}}-
 {{!}}
-{{!}}
+*Responsible for operations related to campaigns.
 {{!}}-
 {{!}}