Before you begin GCA deployment
Contents
Find out what to do before deploying GIM Config Adapter (GCA).
Limitations and assumptions
- ARO uses OCS and S3. The S3 bucket is used to share data among the gsp, gca, and gim namespaces.
- Instructions are provided for a single-tenant deployment.
Download the Helm charts
GIM Config Adapter (GCA) and GCA monitoring are the only services that run in the GCA Docker container. The Helm charts included with the GCA release provision GCA and any Kubernetes infrastructure necessary for GCA to run.
See Helm charts and containers for Genesys Info Mart for the Helm chart versions you must download for your release.
For information about how to download the Helm charts, see Downloading your Genesys Multicloud CX containers.
Third-party prerequisites
For information about setting up your Genesys Multicloud CX private edition platform, see Software requirements.
The following table lists the third-party prerequisites for GCA.
| Name | Version | Purpose | Notes |
|---|---|---|---|
| PostgreSQL | 11.x | Relational database. | |
| Kafka | 2.x | Message bus. | |
| Consul | 1.13.x | Service discovery, service mesh, and key/value store. | |
| Elasticsearch | 7.x | Used for text searching and indexing. Deployed per service that needs Elasticsearch during runtime. | |
| Redis | 6.x | Used for caching. Only distributions of Redis that support Redis cluster mode are supported, however, some services may not support cluster mode. |
Storage requirements
Not applicable
Network requirements
Browser requirements
Not applicable
Genesys dependencies
The following Genesys Multicloud CX microservices must be deployed before you deploy GCA:
- Voice Tenant Service, which enables GCA to access the Configuration Server database
- GIM Stream Processor (GSP)
For detailed information about the correct order of services deployment, see Order of services deployment.
GDPR support
Not applicable. GCA does not store information beyond an ephemeral snapshot.