PrivateEdition/Current/PEGuide/ContDepOrder - Revision history

WikiSysop at 13:32, April 3, 2023

2023-04-03T13:32:05Z

Ed.jamer@genesys.com: Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

2021-11-09T21:14:46Z

Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

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

2021-11-09T21:11:43Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Uma.jayakumar@genesys.com: Published

2021-06-30T18:50:41Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Order of services deployment
|Context=Learn about the order you must follow to deploy Genesys Engage services.
|ComingSoon=No
|Section={{Section
|sectionHeading=Deployment order of Genesys Engage services
|alignment=Vertical
|structuredtext=There are many dependencies between Genesys Engage services. Therefore, certain services must be deployed in a specific sequence. And some services can be deployed in parallel with other services or concurrently with other services. For example, Genesys Web Services (GWS) and its components depends on Genesys Authentication services (GAuth) for authentication purposes. Hence, GAuth service must be deployed before GWS service.

Genesys Engage services must be deployed in the following order:

#Deploy Consul and Kafka. Note that Consul and Kafka must deployed as part of the cloud private edition infrastructure.
#Genesys authentication service (GAuth).
#Microservices pertaining to Voice service.
#Tenant service.
#Agent Setup, Genesys Web Services (GWS), Workspace Web Edition (WWE), and WebRTC.
#Genesys Voice Platform (GVP) service.
#GIM Stream Processor (GSP), GIM Config Adapter (GCA), Genesys Info Mart (GIM), Designer, Universal Contact Service (UCS), Intelligent Workload Distribution (IWD), Telemetry, Nexus, CX Contact, Genesys Engagement Service (GES), and Pulse.
#Billing Data Service (BDS), Interaction Server, and IWD Datamart (IWDDM).
#Genesys Customer Experience Insights (GCXI), and Gplus Adapter for Workforce Management (Gplus WFM).


<br />
|Status=No
}}
}}

@@ Line 18: / Line 18: @@
 #Genesys Voice Platform (GVP) service.
 #GIM Stream Processor (GSP), GIM Config Adapter (GCA), Genesys Info Mart (GIM), Designer, Universal Contact Service (UCS), Intelligent Workload Distribution (IWD), Telemetry, Nexus, CX Contact, Genesys Engagement Service (GES), and Pulse.
-#Billing Data Service (BDS), Interaction Server, and IWD Datamart (IWDDM).
+#Interaction Server and IWD Datamart (IWDDM).
 #Genesys Customer Experience Insights (GCXI), and Gplus Adapter for Workforce Management (Gplus WFM).

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Order of services deployment
-|Context=Learn about the order you must follow to deploy Genesys Engage services.
+|Context=Learn about the order you must follow to deploy Genesys Multicloud CX services.
 |ComingSoon=No
 |Section={{Section
-|sectionHeading=Deployment order of Genesys Engage services
+|sectionHeading=Deployment order of Genesys Multicloud CX services
 |alignment=Vertical
-|structuredtext=There are many dependencies between Genesys Engage services. Therefore, certain services must be deployed in a specific sequence. And some services can be deployed in parallel with other services or concurrently with other services. For example, Genesys Web Services (GWS) and its components depends on Genesys Authentication services (GAuth) for authentication purposes. Hence, GAuth service must be deployed before GWS service.
+|structuredtext=There are many dependencies between Genesys Multicloud CX services. Therefore, certain services must be deployed in a specific sequence. And some services can be deployed in parallel with other services or concurrently with other services. For example, Genesys Web Services (GWS) and its components depends on Genesys Authentication services (GAuth) for authentication purposes. Hence, GAuth service must be deployed before GWS service.
-Genesys Engage services must be deployed in the following order:
+Genesys Multicloud CX services must be deployed in the following order:
 #Deploy Consul and Kafka. Note that Consul and Kafka must deployed as part of the cloud private edition infrastructure.
@@ Line 17: / Line 17: @@
 #Agent Setup, Genesys Web Services (GWS), Workspace Web Edition (WWE), and WebRTC.
 #Genesys Voice Platform (GVP) service.
-#GIM Stream Processor (GSP), GIM Config Adapter (GCA), Genesys Info Mart (GIM), Designer, Universal Contact Service (UCS), Intelligent Workload Distribution (IWD), Telemetry, Nexus, CX Contact, Genesys Engagement Service (GES), and Pulse.
+#GIM Stream Processor (GSP), GIM Config Adapter (GCA), Genesys Info Mart (GIM), Designer, Universal Contact Service (UCS), Intelligent Workload Distribution (IWD), Telemetry, Nexus, CX Contact, Genesys Multicloud CXment Service (GES), and Pulse.
 #Billing Data Service (BDS), Interaction Server, and IWD Datamart (IWDDM).
 #Genesys Customer Experience Insights (GCXI), and Gplus Adapter for Workforce Management (Gplus WFM).