PEC-REP/Current/GIMPEGuide/ArchitectureMain - Revision history

WikiSysop at 13:31, March 10, 2023

2023-03-10T13:31:25Z

WikiSysop at 16:46, September 2, 2022

2022-09-02T16:46:05Z

WikiSysop at 16:16, September 2, 2022

2022-09-02T16:16:05Z

WikiSysop at 13:00, June 13, 2022

2022-06-13T13:00:45Z

WikiSysop at 18:15, April 27, 2022

2022-04-27T18:15:35Z

WikiSysop at 16:00, April 27, 2022

2022-04-27T16:00:28Z

WikiSysop at 15:16, April 22, 2022

2022-04-22T15:16:30Z

WikiSysop at 20:48, April 21, 2022

2022-04-21T20:48:20Z

WikiSysop: Created page with "{{ArticlePEServiceArchitecture |ServiceId=3b2bdfd2-9eb1-4a99-a181-356f2704bc02 |IntroductionText=Genesys Info Mart is the historical reporting back-end service that performs e..."

2022-04-07T18:45:36Z

Created page with "{{ArticlePEServiceArchitecture |ServiceId=3b2bdfd2-9eb1-4a99-a181-356f2704bc02 |IntroductionText=Genesys Info Mart is the historical reporting back-end service that performs e..."

New page

{{ArticlePEServiceArchitecture
|ServiceId=3b2bdfd2-9eb1-4a99-a181-356f2704bc02
|IntroductionText=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:

*GIM Config Adapter (GCA) — Reads configuration data from the contact center Configuration Database and stores the data into Kafka topics for consumption during transformation processing. There is a separate GCA service for each tenant.
*GIM Stream Processor (GSP) — Processes GCA-sourced configuration data and raw event data streamed to Kafka from upstream services handling interaction and agent activity on Voice and Digital channels. GSP transforms the data into data structures suitable for a data mart for contact center historical reporting.
*GIM — Pulls the transformed data from Kafka and loads the transformed data into the Info Mart database. The GIM service also performs other database-related tasks, such as a regular maintenance job and an export job to export Info Mart data. There is a separate GIM service and Info Mart database for each tenant.

All the Genesys Info Mart services are stateful. This has implications for high availability (HA) and disaster recovery (DR) (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=HADR}}) as well as for upgrade methods, because you cannot deploy mirrored services in parallel.

The diagram below shows the architecture of the Genesys Info Mart services. Each service is in its own namespace. 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 Info Mart as a service in the network. In the [[{{FULLPAGENAME}}#Connections_table|Connections table]] that follows the diagram, Egress means the Genesys Info Mart service is the source, and Ingress means the Genesys Info Mart service is the destination.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level {{SuiteLevelLink|architecture}} page.
|Image=pe_gim_architecture_diagram.png
|PEConnections={{PEConnections
|Connection=1
|SourceType=Included Service
|SourceIncluded=c39fe496-c79e-4846-b451-1bc8bedb126b
|DestinationType=Third Party
|DestinationThirdParty=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
|Protocol=16adca31-3f73-4a2d-a261-f79c05be6cf2
|Port=443
|Purpose=GSP state information, checkpoints, and other data used during processing
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=2
|SourceType=Included Service
|SourceIncluded=f05492f5-52ed-490a-b0d5-c318a4a7272b
|DestinationType=Third Party
|DestinationThirdParty=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
|Protocol=16adca31-3f73-4a2d-a261-f79c05be6cf2
|Port=443
|Purpose=Configuration data stored as a GCA snapshot used during processing
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=3
|SourceType=Included Service
|SourceIncluded=f05492f5-52ed-490a-b0d5-c318a4a7272b
|DestinationType=Other
|DestinationOther=Configuration Database
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=5432
|Purpose=Contact center configuration data, which GCA uses to construct the GCA snapshot used during processing
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=4
|SourceType=Included Service
|SourceIncluded=f05492f5-52ed-490a-b0d5-c318a4a7272b
|DestinationType=Other
|DestinationOther=Info Mart database
|Protocol=3b578234-1188-4f2b-a43f-f793fc3a4095
|Port=5432
|Purpose=Configuration data to synchronize the GCA snapshot with configuration data stored in the Info Mart database
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=5
|SourceType=Included Service
|SourceIncluded=e65e00cb-c1c8-4fb8-9614-80ac07c3a4e3
|DestinationType=Other
|DestinationOther=Info Mart database
|Protocol=2e762f22-72ad-4655-95f5-0784fa89f9ba
|Port=5432
|Purpose=Transformed reporting data to be stored in the Info Mart database. GIM also uses this connection to perform database maintenance.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=6
|SourceType=Included Service
|SourceIncluded=e65e00cb-c1c8-4fb8-9614-80ac07c3a4e3
|DestinationType=Third Party
|DestinationThirdParty=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=443
|Purpose=Reporting data exported from the Info Mart database
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=7
|SourceType=Other
|SourceOther=Prometheus
|DestinationType=Included Service
|DestinationIncludedService=c39fe496-c79e-4846-b451-1bc8bedb126b
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=9249
|Purpose=Metrics for monitoring and alerting
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=8
|SourceType=Other
|SourceOther=Prometheus
|DestinationType=Included Service
|DestinationIncludedService=e65e00cb-c1c8-4fb8-9614-80ac07c3a4e3
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=8249
|Purpose=Metrics for monitoring and alerting
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=9
|SourceType=Included Service
|SourceIncluded=c39fe496-c79e-4846-b451-1bc8bedb126b
|DestinationType=Third Party
|DestinationThirdParty=2f69518e-33af-4c0f-adcc-a98e5427e5e0
|Protocol=504f7c1a-2ee9-4dec-8ba2-40b80b623307
|Port=9092
|Purpose=Message bus for receiving and sending reporting data
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=10
|SourceType=Included Service
|SourceIncluded=f05492f5-52ed-490a-b0d5-c318a4a7272b
|DestinationType=Third Party
|DestinationThirdParty=2f69518e-33af-4c0f-adcc-a98e5427e5e0
|Protocol=504f7c1a-2ee9-4dec-8ba2-40b80b623307
|Port=9092
|Purpose=Message bus for sending configuration data
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}{{PEConnections
|Connection=11
|SourceType=Included Service
|SourceIncluded=e65e00cb-c1c8-4fb8-9614-80ac07c3a4e3
|DestinationType=Third Party
|DestinationThirdParty=2f69518e-33af-4c0f-adcc-a98e5427e5e0
|Protocol=504f7c1a-2ee9-4dec-8ba2-40b80b623307
|Port=9092
|Purpose=Message bus for receiving transformed reporting data
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}
}}

@@ Line 9: / Line 9: @@
 All the Genesys Info Mart services are stateful. This has implications for high availability (HA) and disaster recovery (DR) (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=HADR}}) as well as for upgrade methods, because you cannot deploy mirrored services in parallel.
 |DataFlowImage=pe_gim_dataflow_architecture_diagram.png
 |DataFlowAltText=Architecture diagram showing the direction of data flow between the individual Genesys Info Mart services and Kafka, S3-compatible storage, Prometheus, and, for GCA, the Configuration Server database.
@@ Line 128: / Line 127: @@
 ==Ports used for internal purposes==
 GSP uses the following ports for internal connections with Flink.
 {{{!}}
 ! '''Port'''

@@ Line 128: / Line 128: @@
 ==Ports used for internal purposes==
 GSP uses the following ports for internal connections with Flink.
 {{{!}}
 ! '''Port'''

@@ Line 128: / Line 128: @@
 ==Ports used for internal purposes==
 GSP uses the following ports for internal connections with Flink.
 {{{!}}
 ! '''Port'''

← Older revision		Revision as of 13:00, June 13, 2022
Line 126:		Line 126:
	}}		}}
	}}		}}
		+	==Ports used for internal purposes==
		+	GSP uses the following ports for internal connections with Flink.
		+	{{{!}}
		+	! '''Port'''
		+	! '''Protocol'''
		+	{{!}}-
		+	{{!}} colspan="2" {{!}} '''Task manager'''
		+	{{!}}-
		+	{{!}} 6122
		+	{{!}} RPC
		+	{{!}}-
		+	{{!}} colspan="2" {{!}} '''Job manager'''
		+	{{!}}-
		+	{{!}} 6123
		+	{{!}} RPC
		+	{{!}}-
		+	{{!}} 6124
		+	{{!}} Blob
		+	{{!}}-
		+	{{!}} 8081
		+	{{!}} REST
		+	{{!}}}

@@ Line 10: / Line 10: @@
 Unless you are using a single namespace for an OpenShift deployment, each Genesys Info Mart service is in its own namespace.
-|DataFlowImage=pe-gim-dataflow_architecture_diagram.png
+|DataFlowImage=pe_gim_dataflow_architecture_diagram.png
 |DataFlowAltText=Architecture diagram showing the direction of data flow between the individual Genesys Info Mart services and Kafka, S3-compatible storage, Prometheus, and, for GCA, the Configuration Server database.
 |Image=pe_gim_architecture_diagram.png

@@ Line 5: / Line 5: @@
 *GIM Config Adapter (GCA) — Reads configuration data from the contact center Configuration Server database and stores the data into Kafka topics for consumption during transformation processing. There is a separate GCA service for each tenant.
 *GIM Stream Processor (GSP) — Processes GCA-sourced configuration data as well as raw event data streamed to Kafka from upstream services handling interaction and agent activity on Voice and Digital channels. GSP transforms the data into data structures suitable for a data mart for contact center historical reporting.
-*GIM —  Pulls the transformed data from Kafka and loads the transformed data into the Info Mart database. The GIM service also performs other database-related tasks, such as a regular maintenance job and an export job to export Info Mart data. There is a separate GIM service and Info Mart database for each tenant.
+*GIM —  Pulls the transformed data from Kafka and loads this data into the Info Mart database. The GIM service also performs other database-related tasks, such as a regular maintenance job and an export job to export Info Mart data. There is a separate GIM service and Info Mart database for each tenant.
 All the Genesys Info Mart services are stateful. This has implications for high availability (HA) and disaster recovery (DR) (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=HADR}}) as well as for upgrade methods, because you cannot deploy mirrored services in parallel.
 Unless you are using a single namespace for an OpenShift deployment, each Genesys Info Mart service is in its own namespace.
-|DataFlowImage=pe_gim_architecture_dataflow_diagram.png
+|DataFlowImage=pe-gim-dataflow_architecture_diagram.png
 |Image=pe_gim_architecture_diagram.png
 |PEConnections={{PEConnections
 |Connection=1