CX Contact Deployment Guide

Welcome to the CX Contact 9.0 Deployment Guide!

Important

• CX Contact is being released to pre-approved customers as part of the Early Adopter Program. This means that both the product and the documentation are still under development. As a result, documentation sections might require revision as the product develops. We advise that you use this documentation with care. Before you make changes that could affect the success of your deployment, verify them with your Genesys representatives.
• Genesys does not deploy and operate databases in On-Premise deployments. It is always the responsibility of the end user. In a production deployment, data store components (PostgreSQL, Redis, Elasticsearch) must be deployed outside of the Kubernetes cluster and managed by the end user's DBA team. The end user's DBA team will also be responsible for ensuring that these data store components are configured with the appropriate scalability, resiliency and data protection (backups, and so on).

CX Contact contains a set of components that enable you to create, run, and manage outbound voice, SMS, and email campaigns. Some of its key principles and capabilities include the following:

• It includes a state-of-the-art user interface (UI) and middleware components.
• It is built as a set of microservices that run in Docker containers, each scalable in N+1 horizontal mode.
• It uses Genesys servers on the back end, such as Configuration Server, Outbound Contact Server (OCS), and Stat Server.
• Genesys Web Services (GWS) is a prerequisite.

You can deploy CX Contact on premises using one of two methods:

Docker Compose - Docker Compose is suitable for lab or demo environments only, where no product traffic exists. A Docker Compose deployment is easier than a Kubernetes deployment because all CX Contact and GWS components are deployed using a single docker-compose file on a single VM. There are also fewer prerequisites with a Docker Compose deployment because components such as External Load Balancer, Enterprise Redis, and Network File System are excluded from a Docker Compose deployment.

Kubernetes - Kubernetes is suitable for production environments but is considerably more complicated because it deploys CX Contact across multiple VMs and presumes availability of all third-party prerequisites, such as External Load Balancer, Enterprise Redis, and Elasticsearch cluster.

Before you Begin

• Determine the type of deployment (Docker Compose or Kubernetes)
• Prepare a single VM or set of VMs for the CX Contact deployment.
• Install Docker Engine CE on the VM(s) running RHEL 7.0.
• Pull CX Contact and GWS Docker images from an FTP directory and import them into an internal Docker registry. Your Genesys representative will provide you with access information to the FTP directory.
• For deployment using Docker Compose:
  • Install Docker Compose according to the instructions on the Docker documentation site.
  • Obtain Docker-compose files (available for CX Contact and GWS).
• For deployment using Kubernetes:
  • Install Kubernetes according to the installation instructions on the Kubernetes documentation site. You can also refer to the Genesys Docker Deployment Guide for information about Kubernetes and High Availability.
  • Install Helm according to the instructions outlined on the Helm documentation site.

Once you've completed these mandatory procedures, return to this manual to learn how to complete an on-premise deployment of CX Contact.