Before you begin

Find out what to do before deploying Universal Contact Service (UCS).

Related documentation:

• Suite-level guide
• All services
• Universal Contact Service Release Notes

RSS:

• For private edition

Limitations and assumptions

Currently, UCS:

• supports a single-region model of deployment only
• does not support SSL communication with ElasticSearch.
• requires dedicated PostgreSQL deployment per customer.

Download the Helm charts

The UCS Helm Chart is available at:

• Jfrog: https://pureengage.jfrog.io/artifactory/helm-staging/ucsx-xxx.x.xx.tgz

For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: Downloading your Genesys Multicloud CX containers.

Third-party prerequisites

• Kubernetes 1.17+
• Helm 3.0
• Postgres Database v10+
• ElasticSearch v7.8+

Third-party services

Name	Version	Purpose	Notes
Elasticsearch	7.x	Used for text searching and indexing. Deployed per service that needs Elasticsearch during runtime.	ElasticSearch: dedicated (one for UCS-X cluster) as all indices for all tenants are stored in it.
PostgreSQL	11.x	Relational database.	Dedicated for master DB and for each tenant DB due to high load.

Storage requirements

All data are stored in the PostgreSQL, ElasticSearch and Nexus Upload Service which are external to the UCS.

Genesys dependencies

UCS requires the following Genesys components:

• Genesys Authentication Service
• GWS Environment Service

GDPR support

Content coming soon