Genesys Generic Connector Deployment Guide

Genesys Generic Connector Deployment

Before you begin, verify that on the server, you have:

Installed Kubernetes. If not, see Deployment Planning
Setup storage. If not yet, see Storage Solution - Getting Started

Pulling The Genesys Generic Connector from Git

Create a directory with name as mkdir genesys-generic-connector. or according to your ease.
Navigate to newly created directory by cd genesys-generic-connector.
Pull the the code from the:

CODE

git clone --branch Tag-1.0.0 --depth 1 https://gitlab.expertflow.com/cti/genesys-generic-connector

Run cd genesys-generic-connector to change directories. This is where all the YAML files are stored.

Setting Up Environment

We use Kubernetes for our server deployment, on which the static files for the connector will be served, and where the Genesys Generic Connector will be running.

Namespace

Create a namespace “expertflow” if it doesn’t exist.

CODE

kubectl create namespace expertflow

Configure Ingress.yaml

Genesys Generic Connector should be accessible by a fully qualified domain name. Assign the FQDN.

Replace <FQDN> with your FQDN for Genesys Generic Connector (e.g. projectsdemo.expertflow.com) and run this command.

CODE

sed -i 's/devops[0-9]*.ef.com/<FQDN>/g' genesys-ingress.yaml

Create Self-Signed SSL/TLS Ingress Certificates (optional if already present)

Please modify the <FQDN> with your current FQDN before applying the following command.

Create IngressCerts directory (optional)
CODE
```
mkdir ingress-certs  
```
CODE
```
cd ingress-certs
```

set the Variable name to your FQDN (e.g. projectsdemo.expertflow.com).
The ${FQDN} variable in following commands will be replaced with the value you provided in this step
CODE
```
export FQDN=<enter FQDN here>
```

Now generate a secret with the following commands.

CODE

openssl req -x509 \ -newkey rsa:4096 \ -sha256 \ -days 3650 \ -nodes \ -keyout ${FQDN}.key \ -out ${FQDN}.crt \ -subj "/CN=${FQDN}" \ -addext "subjectAltName=DNS:www.${FQDN},DNS:${FQDN}"

Create a Kubernetes secret in your required namespace. In our case it’s expertflow

CODE

kubectl -n expertflow create secret tls hs-ef-ingress-tls-secret --key  ${FQDN}.key --cert ${FQDN}.crt

Configure genesys-deployment.yaml

Open the genesys-deployment.yaml file.
Replace the image with the updated build tag.

Updated build tag is

CODE

gitimages.expertflow.com/cti/genesys-generic-connector:1.0.1

Applying Kubernetes YAMLs

Apply the service with kubectl apply -f genesys-service.yaml
Apply the image-pull secret with kubectl apply -f genesys-imagePullSecret-expertflow.yaml
Apply the Ingress with kubectl apply -f genesys-ingress.yaml. (For RKE2-based Ingresses using Ingress-Nginx Controller)
Apply the deployment with kubectl apply -f genesys-deployment.yaml

Access Genesys URL

You can access the Genesys generic connector using below URL:

CODE

https://<FQDN>/genesys-connector/genesys-wrapper.js