Draft:PEC-REP/Current/GIMPEGuide/Architecture - Revision history

WikiSysop: Redirected page to Draft:PEC-REP/Current/GIMPEGuide/ArchitectureMain

2022-03-30T13:45:51Z

Redirected page to Draft:PEC-REP/Current/GIMPEGuide/ArchitectureMain

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:32:51Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Jose.druker@genesys.com at 21:15, July 8, 2021

2021-07-08T21:15:31Z

Jose.druker@genesys.com at 21:06, July 8, 2021

2021-07-08T21:06:21Z

Jose.druker@genesys.com at 20:52, July 8, 2021

2021-07-08T20:52:04Z

Jose.druker@genesys.com at 17:52, June 30, 2021

2021-06-30T17:52:59Z

Julie.munn@genesys.com: Copied manual

2021-06-08T14:17:26Z

Copied manual

New page

{{PEArchitecture
|DisplayName=Architecture
|Context=Learn about <service_name's> architecture.
|IntroductionText=<div style="background-color: aliceblue; font-style: italic;">Explain the architecture of all services in the container. Note whether the service supports autoscaling. Link to "suite-level" Architecture page: {{SuiteLevelLink|architecture}}

Include a logical architecture diagram. You'll need to work with the diagram team so that all Genesys Engage cloud private edition architecture diagrams are consistent.
</div>
|Standalone=No
|ComingSoon=No
|PEPageType=e38fb4a6-02d6-48d0-a6f1-32635fb394bc
}}

← Older revision		Revision as of 13:45, March 30, 2022
Line 1:		Line 1:
−	~~{{PEArchitecture~~	+	#REDIRECT [[Draft:PEC-REP/Current/GIMPEGuide/ArchitectureMain]]
−	~~\|DisplayName=Architecture~~
−	~~\|Context=Learn about Genesys Info Mart architecture.~~
−	\|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. For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level {{SuiteLevelLink\|architecture}} page.
−
−	~~'''<span style="color:blueviolet;">(Placeholder graphic)<~~/~~span>'''~~
−	~~\|Image=GIM-PE-architecture.png~~
−	~~\|AltText=An architecture diagram shows how Genesys Info Mart is organized and how it relates to other services.~~
−	~~\|Standalone=No~~
−	~~\|ComingSoon=No~~
−	~~\|PEPageType=e38fb4a6-02d6-48d0-a6f1-32635fb394bc~~
−	}}

@@ 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.
-The diagram below shows the architecture of the Genesys Info Mart services. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level {{SuiteLevelLink|architecture}} page.
+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 {{SuiteLevelLink|architecture}} page.
 '''<span style="color:blueviolet;">(Placeholder graphic)</span>'''

@@ Line 10: / Line 10: @@
 The diagram below shows the architecture of the Genesys Info Mart services. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level {{SuiteLevelLink|architecture}} page.
 |Image=GIM-PE-architecture.png
 |AltText=An architecture diagram shows how Genesys Info Mart is organized and how it relates to other services.

@@ Line 3: / Line 3: @@
 |Context=Learn about Genesys Info Mart architecture.
 |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.
+* 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.
+* 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.
 The diagram below shows the architecture of the Genesys Info Mart services. For information about the overall architecture of Genesys Engage cloud private edition, see the high-level {{SuiteLevelLink|architecture}} page.

@@ Line 2: / Line 2: @@
 |DisplayName=Architecture
 |Context=Learn about Genesys Info Mart architecture.
-|IntroductionText={{Notices|Notice=PEComingSoon}}
+|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:
 |Standalone=No
 |ComingSoon=No
 |PEPageType=e38fb4a6-02d6-48d0-a6f1-32635fb394bc
 }}