Order of services deployment

From Genesys Documentation
Jump to: navigation, search

Learn about the order you must follow to deploy Genesys Engage services.

Early Adopter Program
Genesys Engage cloud private edition is being released to pre-approved customers as part of the Early Adopter Program. Please note that the documentation and the product are subject to change. For more details about the program, please contact your Genesys representative.

Deployment order of Genesys Engage services

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:

  1. Deploy Consul and Kafka. Note that Consul and Kafka must deployed as part of the cloud private edition infrastructure.
  2. Genesys authentication service (GAuth).
  3. Microservices pertaining to Voice service.
  4. Tenant service.
  5. Agent Setup, Genesys Web Services (GWS), Workspace Web Edition (WWE), and WebRTC.
  6. Genesys Voice Platform (GVP) service.
  7. 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.
  8. Billing Data Service (BDS), Interaction Server, and IWD Datamart (IWDDM).
  9. Genesys Customer Experience Insights (GCXI), and Gplus Adapter for Workforce Management (Gplus WFM).