View source for GWS/Current/GWSPEGuide/Planning

{{PEPrerequisites
|DisplayName=Before you begin
|Context=Find out what to do before deploying 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:

*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 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. 

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}}.
|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.
|SectionThirdPartyItem={{SectionThirdPartyItem
|ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
|Notes=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
</syntaxhighlight>
You can set up Elasticsearch as a shared or dedicated service.  

<br />
}}{{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=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
|ThirdPartyItem=bc90a902-fc45-4546-b05b-bba8f567dba2
}}{{SectionThirdPartyItem
|ThirdPartyItem=0ce020f7-57d0-430e-bd82-27bef7d7834c
}}{{SectionThirdPartyItem
|ThirdPartyItem=17ed8d61-7149-43bb-8f0e-199f7d206ec8
}}{{SectionThirdPartyItem
|ThirdPartyItem=f1d380bf-42b1-4b67-9d27-d574bad90c86
}}
|StorageStatus=No
|StorageText=GWS uses PostgreSQL to store tenant information, Redis to cache session data, and Elasticsearch to store monitored statistics for fast access. If you set up any of these services as dedicated services for GWS, they have the following minimal requirements:

===PostgreSQL===

*CPU: 2
*RAM: 8 GB
*HDD: 50 GB

===Redis===

*2 nodes:
**CPU: 2
**RAM: 8 GB
**HDD: 20 GB

===Elasticsearch===

*3 "master" nodes:
**CPU: 2
**RAM: 8 GB
**HDD: 20 GB
*4 "data" nodes)
**CPU: 4
**RAM: 16 GB
**HDD: 20 GB
|NetworkStatus=No
|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:
 entryPoints:
   external:
     ingress:
     tls:
       - secretName: gws-secret-ext
         hosts:
           - gws.genesys.com
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.
*'''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.

===Cookies===
GWS components use cookies for following purposes:

*identify HTTP/HTTPS user sessions
*identify CometD user sessions
*support session stickiness
|BrowserStatus=Yes
|BrowserText={{Editgrn open}}JM: Are these browsers are supported for Agent Setup? Browser support for WWE is documented in the WWE guid for private edition: {{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide|topic=Planning}}. Also, can we align with the versions that are supposed to be supported for cloud/private edition in all products? Those versions are:{{Editgrn close}}

*{{Editgrn open}}Chrome: Current release or one version previous
*{{Editgrn open}}Firefox: Current release or one version previous
*{{Editgrn open}}Microsoft Edge: Current release
*{{Editgrn open}}Microsoft Edge Chromium: Current release 


You can use any of the following browsers for UIs:

*Chrome 75+
*Firefox 68+
*Firefox ESR 60.9
*Microsoft Edge
|DependenciesStatus=No
|DependenciesText=Genesys Web Services and Applications must be deployed after Genesys Authentication. 

For a look at the high-level deployment order, see {{SuiteLevelLink|deployorder}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.
|GDPRStatus=Yes
|GDPRText={{Notices}}
|Section={{Section
|sectionHeading=Next steps
|anchor=next
|alignment=Vertical
|structuredtext=*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Configure}}
*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Deploy}}
*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=ConfigureIngress}}
*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=DeployIngress}}
*{{Link-SomewhereInThisVersion|manual=GWSPEGuide|topic=Provision}}
|Status=No
}}
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
}}