View table: PEArchitecture

Jump to: navigation, search

Table structure:

  • productshort - String
  • Role - String
  • DisplayName - String
  • TocName - String
  • Dimension - String
  • Context - Wikitext
  • Product - String
  • Manual - String
  • UseCase - String
  • PEPageType - String
  • IntroductionText - Wikitext
  • Image - String
  • AltText - String

This table has 17 rows altogether.

Page productshort Role DisplayName TocName Dimension Context Product Manual UseCase PEPageType IntroductionText Image AltText
Draft:PEC-Email/Current/EmailPEGuide/Architecture Draft:PEC-Email Architecture Learn about Email's architecture. Email EmailPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The architecture diagram is common for IWD, IWD Data Mart, and Email. For illustration on a sample deployment of Email, see IWD Architecture.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

Draft:PEC-IWD/Current/IWDDMPEGuide/Architecture Draft:PEC-IWD Architecture Learn about the iWD Data Mart's architecture. Intelligent Workload Distribution IWDDMPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The architecture diagram is common for IWD, IWD Data Mart, and Email. For illustration on a sample deployment of IWD Data Mart, see IWD Architecture.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

Draft:PEC-REP/Current/PulsePEGuide/Architecture Draft:PEC-REP Architecture Learn about Genesys Pulse architecture. Reporting PulsePEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc Pulse PE Arch Diagram v5.png
Draft:PEC-REP/Current/RAAPEGuide/Architecture Draft:PEC-REP Architecture Learn about Reporting and Analytics Aggregates (RAA) architecture. Reporting RAAPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The RAA container contains only RAA and Netcat. Netcat is is used by RAA to expose Prometheus metrics, which optionally provide internal monitoring of RAA performance, containers, and so on. Prometheus metrics are for administrator and troubleshooting use only. GCXI CloudArchitecture.jpg GCXI Architecture
Draft:PrivateEdition/Current/TenantPEGuide/Architecture Draft:PrivateEdition Architecture Learn about the Tenant Service architecture. Genesys Multicloud CX Private Edition TenantPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For information about the overall Genesys Multicloud CX Private Edition architecture, see Architecture.

For examples of high-level architecture that include all of the Voice Microservices, see Voice Microservices architecture.

The following diagram shows an example of the high-level architecture specific to the Tenant Service.

voicemcs_tenant_k8s_highlevel_architecture_diagram.png Tenant Service high-level architecture sample for the Kubernetes platform
Draft:VM/Current/VMPEGuide/Architecture Draft:VM Architecture Learn about Voice Microservices architecture. Voice Microservices VMPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For information about the overall Genesys Multicloud CX Private Edition architecture, see Architecture.

The following diagram shows an example of the high-level architecture for Voice Microservices.

voicemcs_private_edition_architecture_diagram.png Voice Services high-level architecture sample for the Kubernetes platform
GVP/Current/GVPPEGuide/Architecture GVP Architecture Learn about GVP architecture. Genesys Voice Platform GVPPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc Genesys Voice Platform (GVP) comprises five services:
  • GVP Configuration Server
  • Service Discovery
  • Reporting Server
  • Resource Manager
  • Media Control Platform

The diagrams in this topic illustrate the architecture of Genesys Voice Platform and the individual Pods.

For more information on the Genesys Multicloud CX private edition architecture, refer to the Architecture topic in the Setting up Genesys Multicloud CX private edition document.

The following diagram shows the GVP architecture:

GVP PE architecture v4.png
IXN/Current/IXNPEGuide/Architecture IXN Architecture Learn about Interaction Server architecture. Interaction Server IXNPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The architecture diagram in this topic illustrates the deployment of the IXN Server.

For more information on the Genesys Multicloud CX private edition architecture, refer to the Architecture topic in the Setting up Genesys Multicloud CX private edition document.


ixn_service_architecture.png IXN architecture
PEC-CAB/Current/CABPEGuide/Architecture PEC-CAB Architecture Learn about Genesys Callback architecture. Callback CABPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For information about the full Genesys Multicloud CX private edition architecture, see Architecture.

For architecture information about GES in relation to the Voice Microservices, including the Tenant Service, see the Voice Microservices Private Edition Guide and the Tenant Service Private Edition Guide.

The following diagram shows the Genesys Engagement Service architecture. There must be at least two GES nodes spread across availability zones, forming a single service for load balancing and high availability.

Configure Redis as primary-replica, non-clustered, single-shard distributed across availability zones. There is a primary node for read-write and one read-only replica, which is a standby in case the primary node experiences a failure.

ges_architecture_private_edition_diagram.png
PEC-Email/Current/EmailPEGuide/Architecture PEC-Email Architecture Learn about Email's architecture. Email EmailPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The architecture diagram is common for IWD, IWD Data Mart, and Email. For illustration on a sample deployment of Email, see IWD Architecture.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

PEC-IWD/Current/IWDDMPEGuide/Architecture PEC-IWD Architecture Learn about the iWD Data Mart's architecture. Intelligent Workload Distribution IWDDMPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc The architecture diagram is common for IWD, IWD Data Mart, and Email. For illustration on a sample deployment of IWD Data Mart, see IWD Architecture.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

PEC-OU/Current/CXCPEGuide/Architecture PEC-OU Architecture Learn about CX Contact architecture. Outbound (CX Contact) CXCPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc 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 Architecture page:

PE_engage-cloud_architecture.png CX Contact private edition architecture diagram
PEC-REP/Current/GCXIPEGuide/Architecture PEC-REP Architecture Learn about Genesys Customer Experience Insights (GCXI) architecture. Reporting GCXIPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc

RAA

GCXI relies on the Reporting and Analytics Aggregates (RAA) aggregation layer, which aggregates Genesys Info Mart data, and then stores the aggregated data in Genesys Info Mart. The RAA container contains only RAA and Netcat. Netcat is is used by RAA to expose Prometheus metrics, which optionally provide internal monitoring of RAA performance, containers, and so on. Prometheus metrics are for administrator and troubleshooting use only.

GCXI

GCXI includes the following containers:

  • gcxi - The main GCXI container, which runs as a StatefulSet.
  • gcxi-control - A supplementary container, which is used for GCXI first-install initialization and for cleanup.
  • alpine / ubi8-minimal - An init container, used to set up log volume permissions. You can instead use any suitable container able to run simple bash commands.

For more information about the over all suite-level architecture, see: Architecture. GCXI does not support Disaster Recovery, cross-regional deployment, or auto-scaling.

GCXI_CloudArchitecture_v2.png GCXI Cloud Architecture
PEC-REP/Current/PulsePEGuide/Architecture PEC-REP Architecture Learn about Genesys Pulse architecture. Reporting PulsePEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc Pulse PE Architecture Diagram v3.png
PrivateEdition/Current/TenantPEGuide/Architecture PrivateEdition Architecture Learn about the Tenant Service architecture. Genesys Multicloud CX Private Edition TenantPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For information about the overall Genesys Multicloud CX Private Edition architecture, see Architecture.

For examples of high-level architecture that include all of the Voice Microservices, see Voice Microservices architecture.

The following diagram shows an example of the high-level architecture specific to the Tenant Service.

voicemcs_tenant_k8s_highlevel_architecture_diagram.png Tenant Service high-level architecture sample for the Kubernetes platform
VM/Current/VMPEGuide/Architecture VM Architecture Learn about Voice Microservices architecture. Voice Microservices VMPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For information about the overall Genesys Multicloud CX Private Edition architecture, see Architecture.

The following diagram shows an example of the high-level architecture for Voice Microservices.

voicemcs_voice_k8s_highlevel_architecture_diagram.png Voice Services high-level architecture sample for the Kubernetes platform
WebRTC/Current/WebRTCPEGuide/Architecture WebRTC Architecture Learn about WebRTC architecture. WebRTC WebRTCPEGuide e38fb4a6-02d6-48d0-a6f1-32635fb394bc For more information about the overall architecture of Genesys Private Edition Cloud, see: Architecture.

Genesys Web Services (GWS) provides Tenant specific information to WebRTC. Workspace Web Edition (WWE) Agent Workspace retrieves all the required information such as tenant ID and WebRTC locations from GWS and sends them to WebRTC.

WebRTC_HLA_Azure.png WebRTC HLA
Retrieved from "https://all.docs.genesys.com/Special:CargoTables/PEArchitecture (2024-04-20 03:12:07)"