Architecture - Reporting Server

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Voice Platform Private Edition Guide for version Current of Genesys Voice Platform.

Learn about Genesys Voice Platform- reporting server architecture

Introduction

The following diagram displays the architecture for GVP Reporting Server.

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 Genesys Voice Platform as a service in the network.

Pe-gvp-reporting-server.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 Genesys Voice Platform as a service in the network. Egress means the Genesys Voice Platform service is the source, and Ingress means the Genesys Voice Platform 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 RS Config Server TCP 8888 Egress TCP messages. RS connects to configuration server to fetch configuration data.
2 RS SQL Server TCP 1433 Egress TCP messages. RS connection to database.
3 RS Master Agent TCP 1705 Egress TCP messages. RS posts SNMP metric and traps to SNMP MA.
4 Kubelet RS TCP 61616 / 8080 61616 for liveness and 8080 for readiness. Note: The protocol is not just TCP, but TCP/HTTP.
5 Prometheus SNMP Exporter HTTP 9116 Ingress HTTP Messages. RS Custom SNMP metric upload to Prometheus.
6 RS-Init Config Server TCP 8888 Egress TCP messages. RS-Init container connects to GVP CS to create RS application.
7 RM RS TCP 61616 Ingress ActiveMQ messages. RM posts billing data to RS.
8 MCP RS TCP 61616 Ingress ActiveMQ messages. MCP posts billing data to RS.