Difference between revisions of "PEC-REP/Current/GIMPEGuide/PlanningGCA"
From Genesys Documentation
| Line 5: | Line 5: | ||
|LimitationsStatus=No | |LimitationsStatus=No | ||
|LimitationsText=Instructions are provided for a single-tenant deployment. | |LimitationsText=Instructions are provided for a single-tenant deployment. | ||
| − | |||
| − | |||
|HelmStatus=No | |HelmStatus=No | ||
| − | |HelmText=GIM Config Adapter (GCA) | + | |HelmText=To configure and deploy the GIM Config Adapter (GCA), you must obtain the Helm charts included with the GCA release. These Helm charts provision GCA plus any Kubernetes infrastructure needed for GCA to run. |
| − | + | GCA and GCA monitoring are the only services that run in the GCA container. | |
| − | For information | + | For information on downloading from the Genesys JFrog image repository, see {{SuiteLevelLink|helmchart}}. To find the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}. |
|ThirdPartyStatus=No | |ThirdPartyStatus=No | ||
|ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}. | |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}. | ||
| Line 19: | Line 17: | ||
|SectionThirdPartyItem={{SectionThirdPartyItem | |SectionThirdPartyItem={{SectionThirdPartyItem | ||
|ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0 | |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0 | ||
| − | |Notes=GCA publishes configuration data to the < | + | |Notes=GCA publishes configuration data to the <code>gca-cfg</code> topic, which GSP consumes. The topic must exist in your Kafka configuration. |
<!--<br/>{{Editgrn_open}}<font color=red>'''Writer's note: Borys/Alexey,''' in GSP the topic name is customizable (in the values.yaml), but I don't see where customers could customize it in the GCA values.yaml. ??</font>{{Editgrn_close}}--> | <!--<br/>{{Editgrn_open}}<font color=red>'''Writer's note: Borys/Alexey,''' in GSP the topic name is customizable (in the values.yaml), but I don't see where customers could customize it in the GCA values.yaml. ??</font>{{Editgrn_close}}--> | ||
}}{{SectionThirdPartyItem | }}{{SectionThirdPartyItem | ||
| Line 31: | Line 29: | ||
}} | }} | ||
|StorageStatus=No | |StorageStatus=No | ||
| − | |StorageText=GCA uses | + | |StorageText=GCA uses S3-compatible storage to store the GCA snapshot during processing. You must provision this S3-compatible storage in your environment. By default, GCA is configured to use Azure Blob storage, but you can also use S3-compatible storage provided by other cloud platforms. |
| + | |||
| + | Genesys expects you to use the same storage account for GSP and GCA. If you want to provision separate storage for GCA, follow the {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_Plan_CreateS3Storage|display text=Create S3-compatible storage}} instructions for GSP to create similar S3-compatible storage for GCA. | ||
|NetworkStatus=No | |NetworkStatus=No | ||
|NetworkText=No special network requirements. | |NetworkText=No special network requirements. | ||
Revision as of 16:16, September 2, 2022
This topic is part of the manual Genesys Info Mart Private Edition Guide for version Current of Reporting.
Contents
Find out what to do before deploying GIM Config Adapter (GCA).
Related documentation:
RSS:
Limitations and assumptions
Instructions are provided for a single-tenant deployment.
Download the Helm charts
To configure and deploy the GIM Config Adapter (GCA), you must obtain the Helm charts included with the GCA release. These Helm charts provision GCA plus any Kubernetes infrastructure needed for GCA to run.
GCA and GCA monitoring are the only services that run in the GCA container.
For information on downloading from the Genesys JFrog image repository, see Downloading your Genesys Multicloud CX containers. To find the correct Helm chart version for your release, see Helm charts and containers for Genesys Info Mart.
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 |
|---|---|---|---|
| Kafka | 2.x | Message bus. | GCA publishes configuration data to the gca-cfg topic, which GSP consumes. The topic must exist in your Kafka configuration. |
| Object storage | Persistent or shared data storage, such as Amazon S3, Azure Blob Storage, or Google Cloud Storage. | Both GCA and GSP require object storage to store data during processing. You can use the same storage account for both services. | |
| A container image registry and Helm chart repository | Used for downloading Genesys containers and Helm charts into the customer's repository to support a CI/CD pipeline. You can use any Docker OCI compliant registry. | ||
| Command Line Interface | The command line interface tools to log in and work with the Kubernetes clusters. |
Storage requirements
GCA uses S3-compatible storage to store the GCA snapshot during processing. You must provision this S3-compatible storage in your environment. By default, GCA is configured to use Azure Blob storage, but you can also use S3-compatible storage provided by other cloud platforms.
Genesys expects you to use the same storage account for GSP and GCA. If you want to provision separate storage for GCA, follow the Create S3-compatible storage instructions for GSP to create similar S3-compatible storage for GCA.
Network requirements
No special network requirements.
Browser requirements
Not applicable
Genesys dependencies
- Voice Tenant Service, which enables GCA to access the Configuration Server database. You must deploy the Voice Tenant Service before you deploy GCA.
- Ensure that an appropriate user account is available for GCA to use to access the Configuration Database. The GCA user account requires at least read permissions.
- You must also have your Tenant ID information available.
- There are no strict dependencies between the Genesys Info Mart services, but the logic of your particular pipeline might require Genesys Info Mart services to be deployed in a particular order. Depending on the order of deployment, there might be temporary data inconsistencies until all the Genesys Info Mart services are operational. For example, GSP looks for the GCA snapshot when it starts; if GCA has not yet been deployed, GSP will encounter unknown configuration objects and resources until the snapshot becomes available.
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.
Comments or questions about this documentation? Contact us for support!