User:Jdruker/GIMPEGuide-Architecture - Revision history

WikiSysop at 22:15, April 6, 2022

2022-04-06T22:15:32Z

WikiSysop at 17:15, March 31, 2022

2022-03-31T17:15:46Z

WikiSysop at 15:00, March 31, 2022

2022-03-31T15:00:57Z

WikiSysop at 14:47, March 31, 2022

2022-03-31T14:47:08Z

WikiSysop at 14:31, March 31, 2022

2022-03-31T14:31:12Z

WikiSysop: Created page with "==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..."

2022-03-31T14:16:05Z

Created page with "==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..."

New page

==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:

*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 [https://all.docs-qa.genesys.com/Draft:PEC-REP/Current/GIMPEGuide/HADR High availability and disaster recovery]) 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. For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level [https://all.docs-qa.genesys.com/Draft:PrivateEdition/Current/PEGuide/Architecture Architecture] page.

==Architecture diagram==
[[File:Pe-gim-architecture.png]]

{{#cargo_query:tables=PEConnections
|fields=Connection,SourceType,Source,DestinationType,Destination,Protocol,Port,Purpose,Classification
|intro=<h2>Connections table</h2><table class="sortable"><tr><th>Connection</th><th>Source</th><th>Destination</th><th>Protocol</th><th>Port</th><th>Classification</th><th>Data that travels on this connection</th></tr>
|outro=</table>
|named args=yes
|default=
|format=template
|template=PEConnectionsPrint
|where=PEConnections._pageName="Draft:PEC-REP/Current/GIMPEGuide/ArchitectureMain" AND Connection IS NOT NULL
|order by=Connection ASC
}}

@@ Line 18: / Line 18: @@
 {{AnchorDiv|Connections}}
 ==Architecture diagram {{Editgrn_open}}— Connections{{Editgrn_close}}==
-{{Editgrn_open}}The direction of the arrows indicates where the connection is initiated (the source) and where it connects to (the destination). The focus is <service>. In the Connections table that follows the diagram [link], ''Egress'' means the focused service is the source, and ''Ingress'' means the focused service is the destination.{{Editgrn_close}}
+{{Editgrn_open}}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.{{Editgrn_close}}
 [[File:Pe-gim-architecture.png]]

@@ Line 1: / Line 1: @@
 <font color=red>'''Writer's note:''' Lavender font = service-specific info entered by the writer. Highlight = suggested new template content.</font>
@@ Line 31: / Line 32: @@
 |order by=Connection ASC
 }}
-==Architecture diagram {{Editgrn_open}}— Data flows{{Editgrn_close}}==
+=={{Editgrn_open}}Architecture diagram — Data flows{{Editgrn_close}}==
 {{Editgrn_open}}The direction of the arrows indicates the direction of data flows.{{Editgrn_close}}
 <font color="#B24DE7">[Same as connections diagram except for the arrows.]</font>

@@ Line 1: / Line 1: @@
 ==Introduction==
 <font color="#B24DE7">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:
@@ Line 33: / Line 35: @@
 {{Editgrn_open}}The direction of the arrows indicates the direction of data flows.{{Editgrn_close}}
-[Same as connections diagram except for the arrows.]
+<font color="#B24DE7">[Same as connections diagram except for the arrows.]</font>

@@ Line 8: / Line 8: @@
 {{Editgrn_open}}For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level [https://all.docs-qa.genesys.com/Draft:PrivateEdition/Current/PEGuide/Architecture Architecture] page.{{Editgrn_close}}
-{{Editgrn_open}}The following diagrams show the <service> architecture. The first diagram is from the point of view of network connections. The second shows data flows. See also [link to HA page] for high availability/disaster recovery architecture.{{Editgrn_close}}
+{{Editgrn_open}}The following diagrams show the <service> architecture. {{Editgrn_close}}
 ==Architecture diagram {{Editgrn_open}}— Connections{{Editgrn_close}}==
 {{Editgrn_open}}The direction of the arrows indicates where the connection is initiated (the source) and where it connects to (the destination). The focus is <service>. In the Connections table that follows the diagram [link], ''Egress'' means the focused service is the source, and ''Ingress'' means the focused service is the destination.{{Editgrn_close}}
@@ Line 25: / Line 29: @@
 |order by=Connection ASC
 }}