Jump to: navigation, search

Upgrading Genesys CX Insights

This page describes how to upgrade your Genesys CX Insights deployment to a later release. For information about compatible releases, see the Product Alert.


Disclaimer
Genesys is committed to diversity, equality, and inclusivity, including for terms used in our software and documentation. As such, Genesys is removing non-inclusive terms. For third-party products, leveraged by Genesys, and that use these terms, Genesys uses the following as replacements.
  • For the master/slave server and database convention, Genesys uses “primary” and “secondary” or “primary” and “replica,” with the exception of their use in third-party commands.
  • For the blacklist/whitelist terms, Genesys uses blocklist/allowlist.
  • For the master term, when possible, Genesys uses main.

Standard Deployment Procedure for Migrating From 9.0.x to a later 9.0.x release

Deploying Genesys CX Insights 9.0.0



Deployment Steps

  1. Obtain the latest GCXI image (for example, gcxi:9.0.014.03)
  2. Execute the following command to retag the image:
    docker tag <repository name>/<image>:<release> <image>:<release>
    where
    <repository name> is the identifier for the repository from which you downloaded the files,
    <image> is the name of the image file, and <release> is the release number.
    For example:
    docker tag pureengage-docker-production.jfrog.io/gcxi:9.0.014.03 gcxi:9.0.014.03
  3. Execute the following command to back up the GCXI meta db:
    kubectl apply -f <destination path>/gcxi-backup.yaml
    where <destination path> is the folder in which the Genesys Installation Package (IP) is stored.
  4. Execute the following commands to stop the containers:
    kubectl scale deploy/gcxi-slave --replicas=0
    kubectl scale deploy/gcxi-master --replicas=0
  5. Open the gcxi.properties file for editing, and change the value of GCXI_VERSION to match the release you are installing. For example:
    GCXI_VERSION=9.0.014.03
  6. Execute the following commands to load gcxi.properties into Kubernetes:
    kubectl delete configmap gcxi-config
    kubectl create configmap gcxi-config --from-env-file=<destination path>/gcxi.properties --namespace genesys
    where <destination path> is the folder in which the Genesys Installation Package (IP) is stored.
  7. Execute the following commands to update GCXI images in Kubernetes:
    kubectl set image deployment/gcxi-<primary|secondary> gcxi=gcxi:<release>
    Where:
    • <primary|secondary> is either master or slave.
    • <release> is the same string as you entered for the GCXI_VERSION.
    For example:
    kubectl set image deployment/gcxi-master gcxi=gcxi:9.0.014.03
    kubectl set image deployment/gcxi-slave gcxi=gcxi:9.0.014.03
  8. Execute the following command to start the PRIMARY container:
    kubectl scale deploy/gcxi-master --replicas=1
    Wait until PRIMARY container has started (Tomcat is up, and MicroStrategyWeb page is available).
  9. Execute the following command to start the SECONDARY container:
    kubectl scale deploy/gcxi-slave --replicas=1


This page was last edited on April 5, 2019, at 19:24.

Feedback

Comment on this article:

blog comments powered by Disqus