User: Jdruker/GIMPEGuide-Architecture

Writer's note: Lavender font = service-specific info entered by the writer. Highlight = suggested new template content.

Introduction

Genesys Info Mart is the historical reporting back-end service that performs extract, transform, and load (ETL) processing of data generated by contact center activity. Genesys Info Mart comprises the following services:

...

The diagram below shows the architecture of the Genesys Info Mart services. For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

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

The following diagrams show the <service> architecture.

• Architecture diagram — Connections is from the point of view of network connections.
• Architecture diagram — Data flows is from the point of view of data.

See also [link to HA page] for information about high availability/disaster recovery architecture.

Architecture diagram — Connections

The direction of the arrows indicates where the connection is initiated (the source) and where it connects to (the destination), from the point of view of <service>. In the Connections table that follows the diagram [link], Egress means <service> is the source, and Ingress means <service> is the destination.

Connections table

Connection	Source	Destination	Protocol	Port	Classification	Data that travels on this connection
1	GIM Stream Processor	Object storage	HTTPS	443	Egress	GSP state information, checkpoints, and other data used during processing
2	GIM Config Adapter	Object storage	HTTPS	443	Egress	Configuration data stored as a GCA snapshot used during processing
3	GIM Config Adapter	Configuration Database	TCP	5432	Egress	Contact center configuration data, which GCA uses to construct the GCA snapshot used during processing
4	GIM Config Adapter	Info Mart database	TCP	5432	Egress	Configuration data to synchronize the GCA snapshot with configuration data stored in the Info Mart database
5	GIM	Info Mart database	SSL	5432	Egress	Transformed reporting data to be stored in the Info Mart database. GIM also uses this connection to perform database maintenance.
6	GIM	Object storage	HTTP	443	Egress	Reporting data exported from the Info Mart database
7	Prometheus	GIM Stream Processor	HTTP	9249	Ingress	Metrics for monitoring and alerting
8	Prometheus	GIM	HTTP	8249	Ingress	Metrics for monitoring and alerting
9	GIM Stream Processor	Kafka	Kafka	9092	Egress	Message bus for receiving and sending reporting data
10	GIM Config Adapter	Kafka	Kafka	9092	Egress	Message bus for sending configuration data
11	GIM	Kafka	Kafka	9092	Egress	Message bus for receiving transformed reporting data

Ports used for internal purposes

Writer's note: I don't know if the following is actually correct, but I'm putting it in as an example of potential additional content.

GSP uses the following ports for internal connections with Flink.

Port	Protocol
Task manager
6122	RPC
Job manager
6123	RPC
6124	Blob
8081	REST

Architecture diagram — Data flows

The direction of the arrows indicates the direction of data flows.

[Same as connections diagram except for the arrows.]