Jump to: navigation, search

Prerequisites

The prerequisites below are broken down by type of deployment: Docker Compose and Kubernetes.

Docker Compose Prerequisites

The table below outlines all prerequisites for a CX Contact deployment using Docker Compose.

Component Description Mandatory or Optional
VM

Single VM running RHEL 7.0 64-bit 8 CPU cores; 16 GB RAM minimum, 32 GB RAM recommended; at least 100 GB HDD

Mandatory
Configuration Objects The following objects must be added to the Configuration Server:

Cloud (Genesys Generic Client) and CloudCluster (Genesys Generic Server).
Configure these two objects as follows:

  • Cloud (Genesys Generic Client)
    Connections: CloudCluster
    CloudCluster” (Genesys Generic Server)
  • Tenants: Environment
    Connections: confserv, SIPS, StatServer, OCS
Mandatory
Docker Docker 17.03.2-ce or newer stable Mandatory
Chrome The latest version of Chrome must be used as the UI browser. Mandatory
Container orchestration Docker Compose and Portainer Mandatory
Network/DNS All VMs running CX Contact components should belong to the same local network segment and be interconnected so that all components can communicate over the network. DNS must be present in the network and allow for names resolution. CX Contact components always use FQDNs (not IP addresses) to establish communication to each other. Mandatory
PostgreSQL PostgreSQL 9.5+ Recommended (Docker Compose)
SFTP Server Use when automation capabilities are required Optional
Genesys Web Services (GWS) v.9.0. GWS9 is an integral part of the CX Contact Docker Compose deployment. For this reason, you do not need to deploy GWS9 separately. Mandatory
Genesys core components v.8.5 or v.8.1

CX Contact components operate with Genesys core services on the back end. It's expected that all voice-processing components (Voice VM and shared services such as GVP) are deployed and running. In GCloud, Cloud Contact can operate with multiple voice tenants and comprises a shared service.

Mandatory

Kubernetes Prerequisites

The table below outlines all prerequisites for a CX Contact deployment using Kubernetes.

Component Description Mandatory or Optional
VMs

Set of VMs running RHEL 7.0 64-bit

Each machine should run Red Hat Enterprise Linux 7.0 64-bit as a guest OS and have at least 8 CPU cores and 16 GB RAM minimum (32 GB RAM recommended), 100 GB HDD minimum.

Mandatory
Docker Docker 17.03.2-ce, with CX Contact Docker images stored in the Docker registry. Mandatory
Chrome The latest version of Chrome must be used as the UI browser. Mandatory
Container orchestration Google Kubernetes Engine Mandatory
Network/DNS All VMs running CX Contact components should belong to the same local network segment and be interconnected so that all components can communicate over the network. DNS must be present in the network and allow for names resolution. CX Contact components always use FQDNs (not IP addresses) to establish communication to each other. Mandatory
Load Balancers F5 or functionally comparable hardware or software load balancer.

Note: Load balancer must be configured to ensure that internal CX Contact components cannot be accessed via load balancer. Only API Aggregator should be accessible.

Mandatory
Shared file system (NFS) NFS Mandatory
PostgreSQL PostgreSQL 9.5+ Mandatory
Redis Redis 5.x cluster, Enterprise Redis with persistence is recommended Mandatory
Elasticsearch ES Cluster 6.3x Mandatory
SFTP Server Use when automation capabilities are required Optional
Genesys Web Services (GWS) v.9.0 Mandatory (Deployed using Docker Compose)
Genesys core components v.8.5 or v.8.1

CX Contact components operate with Genesys core services on the back end. It's expected that all voice-processing components (Voice VM and shared services such as GVP) are deployed and running. In GCloud, Cloud Contact can operate with multiple voice tenants and comprises a shared service.

Mandatory
This page was last modified on June 24, 2019, at 05:57.

Feedback

Comment on this article:

blog comments powered by Disqus