WikiSysop: Created page with "{{ArticlePEServiceArchitecture |ServiceId=bd34fb74-a5d2-4463-8a08-05cb52928172 |IntroductionText=CX Contact is set of microservices that run in Kubernetes containers, each sca..."

2022-06-30T12:45:59Z

Created page with "{{ArticlePEServiceArchitecture |ServiceId=bd34fb74-a5d2-4463-8a08-05cb52928172 |IntroductionText=CX Contact is set of microservices that run in Kubernetes containers, each sca..."

New page

{{ArticlePEServiceArchitecture
|ServiceId=bd34fb74-a5d2-4463-8a08-05cb52928172
|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.
|Image=CXC PE architecture diagram.png
|PEConnections={{PEConnections
|Connection=1
|SourceType=API
|SourceAPI=Customer Browser/API
|DestinationType=Other
|DestinationOther=CXC Front-end Ingress
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=443
|Purpose=RTP connection to CX Contact from a customer browser or API client.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=2
|SourceType=Included Service
|SourceIncluded=100a6d42-35ae-48c2-b16f-aa8799d13cb7
|DestinationType=Other
|DestinationOther=SFTP server
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=20, 21, 22
|Purpose=A connection for remote authentication on customer-specified SFTP server.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=3
|SourceType=Other
|SourceOther=Compliance data provider
|DestinationType=Included Service
|DestinationIncludedService=a83b6aab-42e4-4960-abbc-ae39fd8ec319
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=443
|Purpose=A connection to read compliance data and rules from a compliance data provider.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=4
|SourceType=UI
|SourceUI=CX Contact UI
|DestinationType=Other
|DestinationOther=CX Contact Backend
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=3004-3008
|Purpose=HTTP connection between the CX Contact UI and backend services.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=5
|SourceType=Service
|SourceService=bd34fb74-a5d2-4463-8a08-05cb52928172
|DestinationType=Third Party
|DestinationThirdParty=3aee73ed-68e0-4c70-8693-2421c68b86cd
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=6379
|Purpose=TCP connection between CX Contact and Redis for caching data on user sessions and dialing history.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=6
|SourceType=Service
|SourceService=bd34fb74-a5d2-4463-8a08-05cb52928172
|DestinationType=Other
|DestinationOther=Network file share
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=2049
|Purpose=A connection for network/cloud file storage to store import and export files for both contacts and suppression lists.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=7
|SourceType=Service
|SourceService=bd34fb74-a5d2-4463-8a08-05cb52928172
|DestinationType=Third Party
|DestinationThirdParty=1a407778-58fe-4acd-8ca7-5af8eac31283
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=5432
|Purpose=Connection between CX Contact and PostgreSQL to store data about contact and suppression lists from different outbound campaigns.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=8
|SourceType=Service
|SourceService=6e2088c1-2827-43ad-9adc-98fde851ad37
|DestinationType=Service
|DestinationService=bd34fb74-a5d2-4463-8a08-05cb52928172
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=8888
|Purpose=Connection between Outbound contact server (back-end components) and CX Contact.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=9
|SourceType=Other
|SourceOther=GWS
|DestinationType=Service
|DestinationService=6e2088c1-2827-43ad-9adc-98fde851ad37
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=5050
|Purpose=A connection between GWS and Outbound contact server for config data.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=10
|SourceType=Other
|SourceOther=GWS
|DestinationType=Other
|DestinationOther=Config server
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=8888
|Purpose=A connection between GWS and Config server for config data.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=11
|SourceType=Service
|SourceService=bd34fb74-a5d2-4463-8a08-05cb52928172
|DestinationType=Other
|DestinationOther=GWS
|Protocol=b3f7f755-b303-4d97-b8ed-02531a897c2f
|Port=443
|Purpose=An HTTPS connection between CX Contact and GWS for managing config data, campaigns, tenant settings, and authentication.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=12
|SourceType=Service
|SourceService=bd34fb74-a5d2-4463-8a08-05cb52928172
|DestinationType=Other
|DestinationOther=Nexus
|Protocol=b3f7f755-b303-4d97-b8ed-02531a897c2f
|Port=443
|Purpose=An HTTPS connection between CX Contact and Nexus for SMS/Email support.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=13
|SourceType=Service
|SourceService=6e2088c1-2827-43ad-9adc-98fde851ad37
|DestinationType=Third Party
|DestinationThirdParty=1a407778-58fe-4acd-8ca7-5af8eac31283
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=5432
|Purpose=A connection for Outbound DB access to update contact list data.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}
}}

PEC-OU/Current/CXCPEGuide/Architecture new - Revision history

WikiSysop: Created page with "{{ArticlePEServiceArchitecture |ServiceId=bd34fb74-a5d2-4463-8a08-05cb52928172 |IntroductionText=CX Contact is set of microservices that run in Kubernetes containers, each sca..."