Difference between revisions of "PrivateEdition/Current/TenantPEGuide/ArchitectureMain"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
Line 113: Line 113:
 
|Port=8888
 
|Port=8888
 
|Purpose=Genesys Authentication access to provisioning
 
|Purpose=Genesys Authentication access to provisioning
 +
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 
}}{{PEConnections
 
}}{{PEConnections
 
|Connection=12
 
|Connection=12
 +
|SourceType=Service
 +
|SourceService=fad64937-a7c8-43ca-836d-68582478f982
 +
|DestinationType=Service
 +
|DestinationService=c4749716-a442-4050-ab1a-ca34e082b5c0
 +
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 +
|Port=8888
 +
|Purpose=Configuration and provisioning
 +
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 +
}}{{PEConnections
 +
|Connection=13
 +
|SourceType=Service
 +
|SourceService=fad64937-a7c8-43ca-836d-68582478f982
 +
|DestinationType=Service
 +
|DestinationService=c4749716-a442-4050-ab1a-ca34e082b5c0
 +
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 +
|Port=8000
 +
|Purpose=Voice Microservices events
 +
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 +
}}{{PEConnections
 +
|Connection=14
 
|SourceType=Other
 
|SourceType=Other
 
|SourceOther=Prometheus
 
|SourceOther=Prometheus
Line 121: Line 142:
 
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
 
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
 
|Port=15000
 
|Port=15000
|Purpose=Tenant Service provides metrics for monitoring and alerting with Prometheus
+
|Purpose=Tenant Service provides metrics for monitoring and alerting with Prometheus.
 
|Classification=b2dff270-19d6-4258-a380-da06305a143c
 
|Classification=b2dff270-19d6-4258-a380-da06305a143c
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=13
+
|Connection=15
 +
|SourceType=Included Service
 +
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 +
|DestinationType=Third Party
 +
|DestinationThirdParty=1a407778-58fe-4acd-8ca7-5af8eac31283
 +
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 +
|Port=5432
 +
|Purpose=Persistent SQL storage for provisioning data
 +
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 +
}}{{PEConnections
 +
|Connection=16
 
|SourceType=Service
 
|SourceType=Service
 
|SourceService=58e238b9-a7f6-4af9-8050-0fe1b7cb1c39
 
|SourceService=58e238b9-a7f6-4af9-8050-0fe1b7cb1c39
Line 134: Line 165:
 
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=14
+
|Connection=17
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
Line 141: Line 172:
 
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 
|Port=5432
 
|Port=5432
|Purpose=Persistent SQL storage for provisioning data
+
|Purpose=Persistent storage for outbound campaigns and calling lists
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=15
+
|Connection=18
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|DestinationType=Third Party
 
|DestinationThirdParty=1a407778-58fe-4acd-8ca7-5af8eac31283
 
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
 
|Port=5432
 
|Purpose=persistent storage for outbound campaigns and calling lists
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
}}{{PEConnections
 
|Connection=16
 
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
Line 161: Line 182:
 
|Purpose=For information, see connections 16, 27, and 32 in the Voice Microservices {{Link-AnywhereElse|product=VM|version=Current|manual=VMPEGuide|topic=Architecture1|anchor=ConnectionsTable|display text=Connections table}}.
 
|Purpose=For information, see connections 16, 27, and 32 in the Voice Microservices {{Link-AnywhereElse|product=VM|version=Current|manual=VMPEGuide|topic=Architecture1|anchor=ConnectionsTable|display text=Connections table}}.
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=17
+
|Connection=19
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
Line 171: Line 192:
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=18
+
|Connection=20
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
Line 181: Line 202:
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=19
+
|Connection=21
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
Line 191: Line 212:
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
 
}}{{PEConnections
 
}}{{PEConnections
|Connection=20
+
|Connection=22
 
|SourceType=Included Service
 
|SourceType=Included Service
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba
 
|SourceIncluded=5a34ac72-3fae-4368-afd8-5b899e1c52ba

Latest revision as of 18:15, September 22, 2022

Introduction

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

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

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

See also High availability and disaster recovery for information about high availability/disaster recovery architecture.

Architecture diagram — Connections

The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. The direction of the arrows indicates where the connection is initiated (the source) and where an initiated connection connects to (the destination), from the point of view of Tenant Service as a service in the network.

Pe tenant architecture diagram.png

Connections table

The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of Tenant Service as a service in the network. Egress means the Tenant Service service is the source, and Ingress means the Tenant Service service is the destination. Intra-cluster means the connection is between services in the cluster.

Connection Source Destination Protocol Port Classification Data that travels on this connection
1 Billing Data Service Tenant Service TCP 8888 Intra-cluster Configuration and provisioning
2 Genesys Pulse Tenant Service TCP 8888 Intra-cluster Configuration and provisioning
3 Genesys Pulse Tenant Service TCP 8000 Intra-cluster Voice Microservices events
4 Interaction Server Tenant Service TCP 8888 Intra-cluster Configuration and provisioning
5 Tenant Service Interaction Server TCP 7120 Intra-cluster Multimedia transactions status
6 Interaction Server Tenant Service TCP 2060 Intra-cluster Agent status for multimedia
7 Genesys Web Services and Applications Tenant Service TCP 8888 GWS (Configuration Service) access to provisioning
8 Genesys Web Services and Applications Tenant Service TCP 8000 Intra-cluster GWS call control events
9 Genesys Web Services and Applications Tenant Service TCP 2060 Intra-cluster GWS statistics
10 Genesys Web Services and Applications Tenant Service TCP 5050 Intra-cluster Outbound campaign control through GWS
11 Genesys Authentication Tenant Service TCP 8888 Intra-cluster Genesys Authentication access to provisioning
12 Gplus Adapters for WFM Tenant Service TCP 8888 Intra-cluster Configuration and provisioning
13 Gplus Adapters for WFM Tenant Service TCP 8000 Intra-cluster Voice Microservices events
14 Prometheus Tenant Service HTTP 15000 Ingress Tenant Service provides metrics for monitoring and alerting with Prometheus.
15 Tenant Service PostgreSQL TCP 5432 Egress Persistent SQL storage for provisioning data
16 Genesys Engagement Service Tenant Service HTTP 5580 Intra-cluster Routing requests and events
17 Tenant Service PostgreSQL TCP 5432 Egress Persistent storage for outbound campaigns and calling lists
18 Tenant Service Voice Microservices For information, see connections 16, 27, and 32 in the Voice Microservices Connections table.
19 Tenant Service Kafka TCP 9092/9093 Egress Outbound reporting
20 Tenant Service Redis TCP 6379 Egress Voice Microservices call control events
21 Tenant Service Redis TCP 6379 Egress Tenant configuration and provisioning synchronization for in-memory caching
22 Tenant Service Redis TCP 6379 Intra-cluster Cross-region Voice Microservices call control events in remote Redis
Comments or questions about this documentation? Contact us for support!