PEC-AD/Current/WWEPEGuide/Architecture - Revision history

WikiSysop at 18:49, July 28, 2022

2022-07-28T18:49:15Z

WikiSysop at 14:15, June 27, 2022

2022-06-27T14:15:44Z

WikiSysop at 13:31, June 1, 2022

2022-06-01T13:31:10Z

WikiSysop at 20:48, April 21, 2022

2022-04-21T20:48:14Z

WikiSysop at 13:15, March 31, 2022

2022-03-31T13:15:58Z

Matthew.west@genesys.com: Published

2021-11-08T16:43:33Z

Published

Julie.munn@genesys.com: Published

2021-06-29T14:24:55Z

Published

New page

{{PEArchitecture
|DisplayName=Architecture
|TocName=Architecture
|Context=Learn about Workspace Web Edition architecture.
|IntroductionText=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, Genesys Web Services (GWS), Genesys Authentication Service (Gauth), and WebRTC containers through the application gateway.

The suite-level architecture diagram is on the suite-level {{SuiteLevelLink|architecture}} page.
|Image=WWE MultiCloud Private Edition HLA.png
|AltText=How WWE relates to Genesys Web Services, Genesys Authentication, WebRTC, and how it is accessed by a browser.
|Standalone=No
|ComingSoon=No
|PEPageType=e38fb4a6-02d6-48d0-a6f1-32635fb394bc
}}

@@ Line 9: / Line 9: @@
 *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.
+WWE is deployed as part of the Genesys Web Services Kubernetes Services. Client users (agents) use a web browser running the Agent Workspace to access Workspace Web Edition (WWE), Genesys Web Services (GWS), Genesys Authentication Service (Gauth), and WebRTC containers through the inbound gateway.
 The suite-level architecture diagram is on the suite-level {{SuiteLevelLink|architecture}} page.

@@ Line 19: / Line 19: @@
 *{{Link-AnywhereElse|product=WebRTC|version=Current|manual=WebRTCPEGuide}}
 *{{Link-AnywhereElse|product=TLM|version=Current|manual=TLMPEGuide}}
 |Image=pe_wwe_architecture_diagram.png
-|AltText=How WWE relates to Genesys Web Services, Genesys Authentication, WebRTC, and how it is accessed by a browser.
+|AltText=How WWE relates to Genesys Web Services, Genesys Authentication, WebRTC, Digital Channels, and how it is accessed by a browser.
 |PEConnections={{PEConnections
 |Connection=1
 |SourceType=Other
 |SourceOther=Browser
@@ Line 29: / Line 99: @@
 |Protocol=16adca31-3f73-4a2d-a261-f79c05be6cf2
 |Port=443
-|Purpose=Inbound web traffic
+|Purpose=HTML 5 content required to render WWE in the browser.
 |Classification=b2dff270-19d6-4258-a380-da06305a143c
 }}{{PEConnections
-|Connection=2
+|Connection=8
 |SourceType=Other
 |SourceOther=Ingress proxy
@@ Line 39: / Line 109: @@
 |Protocol=16adca31-3f73-4a2d-a261-f79c05be6cf2
 |Port=443
-|Purpose=Inbound web traffic
+|Purpose=HTML 5 content required to render WWE in the browser.
 |Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 }}{{PEConnections
-|Connection=3
+|Connection=9
 |SourceType=Other
 |SourceOther=Ingress controller
@@ Line 49: / Line 119: @@
 |Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
 |Port=8080
-|Purpose=Ingress controller connects to WWE pod
+|Purpose=HTML 5 content required to render WWE in the browser.
 |Classification=f12b7433-c91c-4da4-bd6e-445684e38560
 }}
 }}

@@ Line 10: / Line 10: @@
 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:
@@ Line 45: / Line 47: @@
 |DestinationType=Service
 |DestinationService=9cbd9a42-4bdc-4205-948a-8c130eb304a2
-|Protocol=16adca31-3f73-4a2d-a261-f79c05be6cf2
+|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
 |Port=8080
 |Purpose=Ingress controller connects to WWE pod

← Older revision		Revision as of 20:48, April 21, 2022
Line 10:		Line 10:

	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.		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.
−
−	~~The suite-level architecture diagram is on the suite-level {{SuiteLevelLink\|architecture}} page.~~

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

@@ Line 1: / Line 1: @@
-{{PEArchitecture
+{{ArticlePEServiceArchitecture
-|DisplayName=Architecture
+|ServiceId=9cbd9a42-4bdc-4205-948a-8c130eb304a2
 |IntroductionText=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.
@@ Line 11: / Line 9: @@
 *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 application gateway.
+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.
 The suite-level architecture diagram is on the suite-level {{SuiteLevelLink|architecture}} page.
-|Image=WWE MultiCloud Private Edition HLA.png
 |AltText=How WWE relates to Genesys Web Services, Genesys Authentication, WebRTC, and how it is accessed by a browser.
-|Standalone=No
+|PEConnections={{PEConnections
-|ComingSoon=No
+|Connection=1
-|PEPageType=e38fb4a6-02d6-48d0-a6f1-32635fb394bc
+|SourceType=Other
 }}