Before you begin
Find out what to do before deploying Interaction Server.
Limitations and assumptions
The current version of IXN Server:
- supports single-region model of deployment only
- does not support scaling or HA
- requires dedicated PostgreSQL deployment per customer
Download the Helm charts
Available IXN containers can be found by the following names in registry:
Available helm charts can be found by the name ixn-<version>
For information about downloading Genesys containers and Helm charts from JFrog Edge, see the suite-level documentation: Downloading your Genesys Multicloud CX containers.
The following are the minimum versions supported by IXN Server:
- Kubernetes 1.17+
- Helm 3.0
|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.|
|Kafka||2.x||Message bus.||Kafka is required to deliver IXN reporting events to Genesys Info Mart (GIM). It is the same Kafka for GIM and IXN Server.|
|Consul||1.8||Service discovery, service mesh, and key/value store.|
|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.||Redis is required for communication between Orchestration Server (ORS) and IXN Server. It is the same Redis for ORS and IXN Server.|
In case logging into files is configured for IXN Server, it requires a volume storage mounted to IXN Server container. The storage must be capable to write up to 100 MB/min and 10 MB/s for 2 minutes in peak. The storage size depends on logging configuration.
Regarding storage characteristics for IXN Server database, refer to PostgreSQL documentation.
Contact your account representative if you need assistance with sizing calculations.
Tenant service. For more information, refer to the Tenant Service Private Edition Guide.