Before you begin

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Pulse Private Edition Guide for version Current of Reporting.

Find out what to do before deploying Genesys Pulse.

Limitations and assumptions

There are no known limitations.

Tools

  • Install Helm CLI
  • Install Openchift CLI


Download the Helm charts

For information about how to download the Helm charts in Jfrog Edge, see the suite-level documentation: Downloading your Genesys Engage containers

To learn what Helm chart version you must download for your release, see Helm charts and containers for Genesys Pulse

Genesys Pulse Containers

Container Description Docker Path
collector Genesys Pulse Collector <docker>/pulse/collector:<image-version>
cs_proxy Configuration Server Proxy <docker>/pulse/cs_proxy:<image-version>
init Init container, used for DB initialization <docker>/pulse/init:<image-version>
lds Load Distribution Server (LDS) <docker>/pulse/lds:<image-version>
monitor_dcu_push_agent Provides monitoring data from Stat Server and Genesys Pulse Collector <docker>/pulse/monitor_dcu_push_agent:<image-version>
monitor_lds_push_agent Provides monitoring data from LDS <docker>/pulse/monitor_lds_push_agent:<image-version>
pulse Genesys Pulse Backend <docker>/pulse/pulse:<image-version>
ss Stat Server <docker>/pulse/ss:<image-version>
userpermissions User Permissions service <docker>/pulse/userpermissions:<image-version>

Genesys Pulse Helm Charts

Helm Chart Containers Shared Helm Path
Init init yes <helm>/init-<chart-version>.tgz
Pulse pulse yes <helm>/pulse-<chart-version>.tgz
LDS cs_proxy, lds, monitor_lds_push_agent <helm>/lds-<chart-version>.tgz
DCU cs_proxy, ss, collector, monitor_dcu_push_agent <helm>/dcu-<chart-version>.tgz
Permissions cs_proxy, userpermissions <helm>/permissions-<chart-version>.tgz
Init Tenant init <helm>/init-tenant-<chart-version>.tgz
Monitor - yes <helm>/monitor-<chart-version>.tgz

Third-party prerequisites

  • Install Postgres 11
  • Install Redis 6 or later (Note: Redis Cluster is not supported at this time)
  • Install Tenant Service:
    • Tenant UUID (v4) should be provisioned, example: "9350e2fc-a1dd-4c65-8d40-1f75a2e080dd"
    • Tenant service should be exposed as host: "tenant-<tenant-uuid>.voice.svc.cluster.local." port: 8888
  • Install Voice MicroService:
    • Voice service should be exposed as host: "tenant-<tenant-uuid>.voice.svc.cluster.local." port: 8000
  • Install GWS/Auth/Agent Setup
Important
All services listed above should be accessible from the same OpenShift cluster where Genesys Pulse will be deployed.

Storage requirements

Logs Volume

Persistent Volume Size Type IOPS POD Containers Critical Backup needed
pulse-dcu-logs 10Gi RW high DCU csproxy, collector, statserver Y Y
pulse-lds-logs 10Gi RW high lds csproxy, lds Y Y
pulse-permissions-logs 10Gi RW high permissions csproxy, permissions Y Y
pulse-logs 10Gi RW high pulse pulse Y Y

The logs volume is used to store log files. If the log.volumeType is set to the pvc, the persistent volume is used. If the log.volumeType is set to the hostpath, the local storage is used.

Genesys Pulse Collector Health Volume

Local Volume POD Containers
collector-health dcu collector, monitor-sidecar

Genesys Pulse Collector health volume is a non-persistent storage for collector health data used to store Genesys Pulse Collector health state files for monitoring.

Stat Server Backup Volume

Persistent Volume Size Type IOPS POD Containers Critical Backup needed
statserver-backup 1Gi RWO medium dcu statserver N N

Stat Server backup volume is a storage for Stat Server's state backup. It stores the server's state between restarts of the container.

Network requirements

No special requirements.

Genesys dependencies

The following services must be deployed and running before deploying Genesys Pulse:

  • Genesys Authentication
  • Genesys Web Services and Applications
  • Agent Setup
  • Tenant Service
  • Voice MicroService

See also Order of services deployment.

GDPR support

Genesys Pulse supports the General Data Protection Regulation (GDPR). See Genesys Pulse Support for GDPR for details.

Comments or questions about this documentation? Contact us for support!