GWS/Current/GWSPEGuide/Planning - Revision history

WikiSysop at 13:01, February 28, 2023

2023-02-28T13:01:45Z

WikiSysop at 16:16, August 9, 2022

2022-08-09T16:16:01Z

Jumunn at 18:34, May 4, 2022

2022-05-04T18:34:36Z

WikiSysop at 12:16, May 4, 2022

2022-05-04T12:16:04Z

Jumunn: Published

2022-03-15T16:27:11Z

Published

Julie.munn@genesys.com: Undo revision 113630 by Julie.munn@genesys.com (talk)

2021-12-15T13:22:14Z

Undo revision 113630 by Julie.munn@genesys.com (talk)

Julie.munn@genesys.com: Published

2021-12-15T13:21:58Z

Published

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

2021-11-09T20:29:02Z

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

Julie.munn@genesys.com at 20:58, October 29, 2021

2021-10-29T20:58:33Z

Julie.munn@genesys.com: Published

2021-10-29T20:39:30Z

Published

Show changes

@@ Line 18: / Line 18: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
 |Notes='''GWS requires Elasticsearch 7.17+'''. You must configure additional options for Elasticsearch to support the Data Collector Service.<syntaxhighlight>
 action.auto_create_index: false
@@ Line 27: / Line 28: @@
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd
 |Notes=The Redis server must run in cluster mode. You can set up Redis as a shared or dedicated service.
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
 |Notes='''GWS supports PostgreSQL 12.x.''' You can set up PostgreSQL as a shared or dedicated service.

@@ Line 1: / Line 1: @@
 {{PEPrerequisites
 |DisplayName=Before you begin
-|Context=Find out what to do before deploying Web Services and Applications.
+|Context=Find out what to do before deploying Genesys Web Services and Applications.
 |LimitationsStatus=Yes
 |HelmStatus=No
-|HelmText=Web Services and Applications (GWS) in Genesys Multicloud CX private edition is made up of multiple containers and Helm charts. The pages in this "Configure and deploy" chapter walk you through how to deploy the following Helm charts:
+|HelmText=Genesys Web Services and Applications (GWS) in Genesys Multicloud CX private edition is made up of multiple containers and Helm charts. The pages in this "Configure and deploy" chapter walk you through how to deploy the following Helm charts:
 *GWS services (gws-services) - all the GWS components.
-*GWS ingress (gws-ingress) - provides internal and external access to GWS services. Internal ingress is used for cross-component communication inside the GWS deployment. It also can be used by other clients located inside the same Kubernetes cluster. External ingress provides access to GWS services to clients located outside the Kubernetes cluster. If you are deploying Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.
+*GWS ingress (gws-ingress) - provides internal and external access to GWS services. Internal ingress is used for cross-component communication inside the GWS deployment. It also can be used by other clients located inside the same Kubernetes cluster. External ingress provides access to GWS services to clients located outside the Kubernetes cluster. If you are deploying Genesys Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.
 GWS also includes a Helm chart for Nginx (wwe-nginx) for Workspace Web Edition - see the {{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide}} for details about how to deploy this chart.
@@ Line 15: / Line 15: @@
 For information about downloading Helm charts from JFrog Edge, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
-|ThirdPartyText=Install the prerequisite dependencies listed in the '''Third-party services''' table before you deploy Web Services and Applications. See {{SuiteLevelLink|softwarereq}} for a full list of prerequisites and third-party services required by all Genesys Multicloud CX private edition services.
+|ThirdPartyText=Install the prerequisite dependencies listed in the '''Third-party services''' table before you deploy Genesys Web Services and Applications. See {{SuiteLevelLink|softwarereq}} for a full list of prerequisites and third-party services required by all Genesys Multicloud CX private edition services.
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
-|Notes=You must configure additional options for Elasticsearch to support the Data Collector Service.<syntaxhighlight>
+|Notes='''GWS requires Elasticsearch 7.17+'''. You must configure additional options for Elasticsearch to support the Data Collector Service.<syntaxhighlight>
 action.auto_create_index: false
    thread_pool.write.queue_size: -1
@@ Line 30: / Line 30: @@
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
-|Notes=You can set up PostgreSQL as a shared or dedicated service.
+|Notes='''GWS supports PostgreSQL 12.x.''' You can set up PostgreSQL as a shared or dedicated service.
 <br />
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
 |Notes='''GWS supports Consul 1.8'''. Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent.
 }}{{SectionThirdPartyItem
@@ Line 44: / Line 45: @@
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=f1d380bf-42b1-4b67-9d27-d574bad90c86
 }}
 |StorageStatus=No
@@ Line 67: / Line 74: @@
 **RAM: 8 GB
 **HDD: 20 GB
-*4 "data" nodes)
+*4 "data" nodes
 **CPU: 4
 **RAM: 16 GB
@@ Line 84: / Line 91: @@
 In the example above:
-*'''secretName''' is the name of the Kubernetes secret that contains the certificate. The secret is a prerequisite and must be created before you deploy GWS Ingress.
+*'''secretName''' is the name of the Kubernetes secret that contains the certificate. The secret is a prerequisite and must be created before you deploy GWS ingress.
 *'''hosts''' is a list of the fully qualified domain names that should use the certificate. The list must be the same as the value configured for the '''entryPoints.external.ingress.hosts''' parameter.
@@ Line 122: / Line 129: @@
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}
 |Status=No
 }}
 |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 }}

@@ Line 72: / Line 72: @@
 **HDD: 20 GB
 |NetworkStatus=No
-|NetworkText=GWS Ingress objects support TLS mode if you require a secure connection between Kubernetes cluster ingress and GWS ingress. TLS is disabled by default, but you can configure it for internal and external ingress by overriding the '''entryPoints.internal.ingress.tls''' and '''entryPoints.external.ingress.tls''' sections of the {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress|anchor=override|display text=GWS Ingress Helm chart}}.
+|NetworkText=GWS ingress objects support Transport Layer Security (TLS) version 1.2 for a secure connection between Kubernetes cluster ingress and GWS ingress. TLS is disabled by default, but you can configure it for internal and external ingress by overriding the '''entryPoints.internal.ingress.tls''' and '''entryPoints.external.ingress.tls''' sections of the {{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress|anchor=override|display text=GWS ingress Helm chart}}.
 For example:

@@ Line 122: / Line 122: @@
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}
-*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ProvisionAS}}
+*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}
 |Status=No
 }}
 |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 }}

@@ Line 7: / Line 7: @@
 *GWS services (gws-services) - all the GWS components.
-*GWS ingress (gws-ingress) - provides internal and external access to GWS services. Internal ingress is used for cross-component communication inside the GWS deployment. It also can be used by other clients located inside the same Kubernetes cluster. External ingress provides access to GWS services to clients located outside the Kubernetes cluster.
+*GWS ingress (gws-ingress) - provides internal and external access to GWS services. Internal ingress is used for cross-component communication inside the GWS deployment. It also can be used by other clients located inside the same Kubernetes cluster. External ingress provides access to GWS services to clients located outside the Kubernetes cluster. If you are deploying Web Services and Applications in a single namespace with other private edition services, then you do not need to deploy GWS ingress.
 GWS also includes a Helm chart for Nginx (wwe-nginx) for Workspace Web Edition - see the {{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide}} for details about how to deploy this chart.
@@ Line 13: / Line 13: @@
 See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GWSHelm}} for the Helm chart versions you must download for your release.
-For information about downloading Helm charts from JFrog Edge, see {{SuiteLevelLink|helmchart}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.
+For information about downloading Helm charts from JFrog Edge, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
-|ThirdPartyText=Install the prerequisite dependencies listed in the '''Third-party services''' table before you deploy Web Services and Applications.
+|ThirdPartyText=Install the prerequisite dependencies listed in the '''Third-party services''' table before you deploy Web Services and Applications. See {{SuiteLevelLink|softwarereq}} for a full list of prerequisites and third-party services required by all Genesys Multicloud CX private edition services.
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
@@ Line 34: / Line 34: @@
 <br />
 }}{{SectionThirdPartyItem
-|ThirdPartyItem=2936260e-26af-4170-a54f-30ce99564b4b
+|ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
-|Notes=Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent.
+|Notes='''GWS supports Consul 1.8'''. Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent.
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=bc90a902-fc45-4546-b05b-bba8f567dba2
@@ Line 119: / Line 119: @@
 |alignment=Vertical
 |structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure}}
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}
 *{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}