Difference between revisions of "GWS/Current/GWSPEGuide/Planning"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
(Published)
Line 66: Line 66:
 
|StorageStatus=No
 
|StorageStatus=No
 
|StorageText=There are no specific storage requirements.
 
|StorageText=There are no specific storage requirements.
−
|NetworkStatus=Yes
+
|NetworkStatus=No
−
|NetworkText='''This section will not be published for the initial release on June 30.'''
+
|NetworkText={{Notices|Notice=PEComingSoon}}
−
 
 
−
JIRA https://jira.genesys.com/browse/GAPI-28157 (and 28154) will be provided later
 
−
 
 
−
<div style="background-color: aliceblue; font-style: italic;">Describe network requirements, including:
 
−
 
 
−
*Required properties for ingress, such as:
 
−
**Cookies usage
 
−
**Header requirements (client IP and redirect, passthrough)
 
−
**Session stickiness
 
−
**Allowlisting (optional)
 
−
**TLS (optional)
 
−
*Cross-region bandwidth
 
−
*External connections from the Kubernetes cluster to other systems. This includes connecting to Genesys Cloud for hybrid services (such as AI, WEM) as well as "mixed" environments where some components are still deployed as VMs. Note that mixed environments are mainly for transition periods when customers migrate from a classic premise environment to Genesys Engage cloud private edition.
 
−
*WAF Rules (specific only for services handling internet traffic)
 
−
*Pod Security Policy
 
−
*TLS/SSL Certificate configurations
 
−
</div>
 
−
 
 
−
Dev Input:
 
−
 
 
−
*Step 4 here: https://intranet.genesys.com/pages/viewpage.action?pageId=176430803
 
−
*https://jira.genesys.com/browse/GAPI-28154 'All required properties for ingress need to be documented'
 
−
*https://jira.genesys.com/browse/GAPI-28155 'Subnet sizing needs to be documented'
 
−
*https://jira.genesys.com/browse/GAPI-28157 'External connections need to be documented'
 
 
|BrowserStatus=No
 
|BrowserStatus=No
 
|BrowserText=You can use any of the following browsers for UIs:
 
|BrowserText=You can use any of the following browsers for UIs:
Line 103: Line 79:
  
 
See also {{SuiteLevelLink|deployorder}}.
 
See also {{SuiteLevelLink|deployorder}}.
−
|GDPRStatus=Yes
+
|GDPRStatus=No
−
|GDPRText='''This section will not be published for the initial release on June 30.'''<div style="background-color: aliceblue; font-style: italic;">Provide information about GDPR support. Include a link to the "suite-level" documentation. {{SuiteLevelLink|gdpr}}</div><br />
+
|GDPRText={{Notices|Notice=PEComingSoon}}
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 
}}
 
}}

Revision as of 19:28, June 29, 2021

This topic is part of the manual Genesys Web Services and Applications Private Edition Guide for version Current of Genesys Web Services and Applications.

Find out what to do before deploying Web Services and Applications.

Limitations and assumptions

The common Authentication Service must be deployed prior to the Web Services and Applications deployment.

Download the Helm charts

You can download your GWS Helm charts from JFrog using your credentials.

For information about downloading Genesys Helm charts from JFrog Edge, see the suite-level documentation: Downloading your Genesys Multicloud CX containers.

Third-party prerequisites

Name Version Purpose Shared/Dedicated
Elasticsearch 7.x Text Searching & Indexing Shared is Ok
Redis 6.x Caching and Streaming service Shared is Ok
Consul 1.8 Service Discovery Shared Consul instance must be used to support tenant discovery
Postgres 11.x Relational DB Shared is Ok

All services are part of the platform list, and can be either dedicated or shared depending on deployment.

Additional options:

  1. Redis server must run in cluster mode. Standalone mode is not supported.
  2. Elasticsearch server requires additional options configured on each node for proper work of the "GWS Datacollector Service" component:
    action.auto_create_index: false
    thread_pool.write.queue_size: -1

Sizing

All third party servers can be shared with other Genesys solutions.

However, Postges, Redis, and Elasticsearch can also be installed as dedicated for GWS. In that case, the minimal requirements are:

  • Postgres:
    • 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
  • Elasticsearch (4 data nodes):
    • CPU: 4
    • RAM: 16 GB
    • HDD: 20 GB

Storage requirements

There are no specific storage requirements.

Network requirements

Content coming soon

Browser requirements

You can use any of the following browsers for UIs:

  • Chrome 75+
  • Firefox 68+
  • Firefox ESR 60.9
  • Microsoft Edge

Genesys dependencies

Genesys Web Services and Applications (GWS) must be deployed along with Agent Setup and after Genesys Authentication is deployed.

See also Order of services deployment.

GDPR support

Content coming soon
Retrieved from "https://all.docs.genesys.com/GWS/Current/GWSPEGuide/Planning (2025-06-19 05:05:24)"
Comments or questions about this documentation? Contact us for support!