Architecture

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Workspace Web Edition Private Edition Guide for version Current of Agent Desktop.

Learn about Workspace Web Edition architecture.

Introduction

The static Workspace Web Edition (WWE) code is bundled in a dedicated NGINX Docker image at build time, ensuring the immutability of the WWE web application content in a Private Edition Kubernetes cluster environment.

WWE is shipped as a Docker image to take advantage of the Multicloud standards such as:

  • Pipeline (including Security)
  • Repositories
  • Shipping logistics

WWE is deployed as part of the Genesys Web Services Kubernetes Services. Client users (agents) use a web browser running the Workspace Agent Desktop to access Workspace Web Edition (WWE), Genesys Web Services (GWS), Genesys Authentication Service (Gauth), and WebRTC containers through the inbound gateway.

In the architecture diagram, the dotted lines from the browser, going through External Ingress and Ingress Controller, to the non-wwe namespace resources represents the connectivity to the back-end services that expose the APIs used by the WWE web application running in the browser. These services are required for WWE to operate. Refer to the following documentation for details about their respective connectivity:

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

See also High availability and disaster recovery for information about high availability/disaster recovery architecture.

Architecture diagram — Connections

The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. 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 Workspace Web Edition as a service in the network.

Pe wwe architecture diagram.png

Connections table

The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of Workspace Web Edition as a service in the network. Egress means the Workspace Web Edition service is the source, and Ingress means the Workspace Web Edition service is the destination. Intra-cluster means the connection is between services in the cluster.

ConnectionSourceDestinationProtocolPortConnection ClassificationData that travels on this connection
1 Browser Inbound Gateway HTTPS 443 Ingress Inbound web traffic
2 Ingress proxy Ingress controller HTTPS 443 Intra-cluster Inbound web traffic
3 Ingress controller Workspace Web Edition HTTPS 8080 Intra-cluster Ingress controller connects to WWE pod