Difference between revisions of "UCS/Current/UCSPEGuide/Planning"
From Genesys Documentation
(Published) |
(Published) |
||
| Line 2: | Line 2: | ||
|DisplayName=Before you begin | |DisplayName=Before you begin | ||
|Context=Find out what to do before deploying Universal Contact Service (UCS). | |Context=Find out what to do before deploying Universal Contact Service (UCS). | ||
| + | |ServiceId=9c5d5ebb-573a-4272-a662-fcb8e8238261 | ||
| + | |IncludedServiceId=3fdcc389-c8a5-4c38-8ee7-d6ab8d1e5dd8 | ||
|LimitationsStatus=No | |LimitationsStatus=No | ||
|LimitationsText=Currently, UCS: | |LimitationsText=Currently, UCS: | ||
| Line 19: | Line 21: | ||
|ThirdPartyText=*Kubernetes 1.17+ | |ThirdPartyText=*Kubernetes 1.17+ | ||
*Helm 3.0 | *Helm 3.0 | ||
| − | *Postgres Database | + | *Postgres Database v11+ |
| − | *ElasticSearch v7.8+ | + | **Dedicated for master DB and for each tenant DB due to high load. |
| + | **DB users must have super user privileges or the following PostgreSQL extensions must be installed before deploying UCS-X service: | ||
| + | ***pg_prewarm | ||
| + | ***intarray | ||
| + | *ElasticSearch v7.8+ | ||
| + | **Dedicated (one for UCS cluster) as all indices for all tenants are stored in it. | ||
|StorageStatus=No | |StorageStatus=No | ||
|StorageText=All data are stored in the PostgreSQL, ElasticSearch and Nexus Upload Service which are external to the UCS. | |StorageText=All data are stored in the PostgreSQL, ElasticSearch and Nexus Upload Service which are external to the UCS. | ||
Revision as of 03:35, December 23, 2021
This topic is part of the manual Universal Contact Service Private Edition Guide for version Current of Universal Contact Service.
Contents
Find out what to do before deploying Universal Contact Service (UCS).
Related documentation:
RSS:
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:
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 v11+
- Dedicated for master DB and for each tenant DB due to high load.
- DB users must have super user privileges or the following PostgreSQL extensions must be installed before deploying UCS-X service:
- pg_prewarm
- intarray
- ElasticSearch v7.8+
- Dedicated (one for UCS cluster) as all indices for all tenants are stored in it.
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
As a part of GDPR compliance procedure, the customer would send a request to Care providing the information about the end user. Care would then open a ticket for Engineering team to follow up on the request.
The engineering team would process the request:
GDPR request: Export Data
- Request to UCS to get contact by ID: identify contact (if there is email address or phone number), or
getContact(if there is a direct contact ID). - Request to UCS-X to get list of interactions for contact found.
- Perform CSV export and attach resulting file to the ticket.
GDPR request: Forget me
- Request to UCS-X to get contact by ID: identify contact (if there is email address or phone number), or
getContact(if there is a direct contact ID). - Request to UCS-X to get list of interactions for contact found.
- Delete all found interactions.
- Re-check that all interactions for contact were removed.
- Delete contact.
- Re-check that contact was removed.
- Update the ticket.
Comments or questions about this documentation? Contact us for support!