Before you begin GIM deployment
Find out what to do before deploying GIM.
Limitations and assumptions
Instructions are provided for a single-tenant deployment.
Download the Helm charts
GIM and GIM monitoring are the only services that run in the GIM Docker container. The Helm charts included with the GIM release provision GIM and any Kubernetes infrastructure necessary for GIM to run.
See Helm charts and containers for Genesys Info Mart for the Helm chart version you must download for your release.
For information about how to download the Helm charts, see Downloading your Genesys Multicloud CX containers.
For information about setting up your Genesys Multicloud CX private edition platform, see Software requirements.
The following table lists the third-party prerequisites for GIM.
|PostgreSQL||11.x||Relational database.||You must create the Info Mart database (see below).|
|Kafka||2.x||Message bus.||The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see Kafka configuration.|
|Object storage||Persistent or shared data storage, such as Amazon S3, Azure Blob Storage, or Google Cloud Storage.||(Optional) For the Data Export feature, GIM uses object storage to store the exported data. Alternatively, you can elect to store the exported data in a directory on a local machine.|
|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.|
GIM uses PostgreSQL for the Info Mart database and, optionally, uses object storage to store exported Info Mart data.
PostgreSQL — the Info Mart database
The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and other services usage in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
A sizing calculator for Genesys Multicloud CX private edition is under development. In the meantime, the interactive tool available for on-premises deployments might help you estimate the size of your Info Mart database, see Genesys Info Mart 8.5 Database Size Estimator.
Genesys recommends a minimum 3 IOPS per GB.
For information about creating the Info Mart database, see Create the Info Mart database.
Create the Info Mart database
Use any database management tool to create the Info Mart ETL database and user.
- Create the database.
- Create a user for the Genesys Info Mart services to use, and grant full permissions to the user for that database.
- This user’s account is used by Genesys Info Mart jobs to access the Info Mart database schema.
- The Info Mart schema name is public.
- ImportantMake a note of the database and user details, which you use to populate database-related Helm chart override values for GIM and GCA.
Object storage — Data Export packages
The GIM Data Export feature enables you to export data from your Info Mart database. Unless you elect to store your exported data in a local directory, your Info Mart data is exported to an object store. GIM supports export to Azure Blob Storage or S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
If you want to use S3-compatible storage, follow the Create object storage instructions for GSP to create the S3-compatible storage for GIM.
As another alternative, you can configure GIM to store your exported data in a local directory. In this case, you do not need to create the object storage.
No special network requirements.
- You must 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, GCA might try to access the Info Mart database to synchronize configuration data; if GIM has not yet been deployed, the Info Mart database will be empty.
For detailed information about the correct order of services deployment, see Order of services deployment.
GIM does not yet support GDPR compliance. For details about the Info Mart database tables and columns that potentially contain personally identifiable information (PII), see the description of the CTL_GDPR_HISTORY table in the Genesys Info Mart on-premises documentation.