Skip to main content
Skip table of contents

Upgrade Guide CX-4.5 to CX-4.5.1

Before proceeding with the upgrade, make sure that the system is idle state i.e. all agents are logged-out from agent-desk.

  1. Clone the CX repository on target server

    CODE
    # Create CX-4.5.1 directory from root
    mkdir CX-4.5.1
    
    # Navigate to CX-4.5.1
    cd CX-4.5.1
    
    # Clone the CX-4.5.1 branch of cim-solution repository
    git clone -b CX-4.5.1 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git
    
    # Navigate to root(previous) directory
    cd ..
  2. Stop all core components.

    CODE
    # Navigate to the following folder of the existing release i.e. CX-4.5
    cd cim-solution/kubernetes
    
    kubectl delete -f cim/Deployments
    kubectl delete -f cim/StatefulSet/ef-amq-statefulset.yaml
    
    # Stop reporting connector
    kubectl delete -f pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml -n expertflow
    
    # delete configmap for reporting connector 
    kubectl -n expertflow delete configmap ef-reporting-connector-conf
    
    # Navigate to root directory 
    cd ../../
  3. Replace the following files from 4.5.1 directory to current deployment directory

    CODE
    # Copy Historical Reporting Manager deployment files
    cp CX-4.5.1/cim-solution/kubernetes/cim/ConfigMaps/ef-historical-reporting-configmap.yaml cim-solution/kubernetes/cim/ConfigMaps
    cp CX-4.5.1/cim-solution/kubernetes/cim/Deployments/ef-historical-reports-deployment.yaml cim-solution/kubernetes/cim/Deployments
    cp CX-4.5.1/cim-solution/kubernetes/cim/Services/ef-historical-reports-service.yaml cim-solution/kubernetes/cim/Services
    cp CX-4.5.1/cim-solution/kubernetes/cim/Ingresses/nginx/ef-historical-reports-Ingress.yaml cim-solution/kubernetes/cim/Ingresses/nginx
    
    # Copy Reporting connector conf file
    cp CX-4.5.1/cim-solution/kubernetes/pre-deployment/reportingConnector/reporting-connector.conf cim-solution/kubernetes/pre-deployment/reportingConnector/reporting-connector.conf
  4. Update the AMQ deployment.

    YAML
    1) Open cim-solution/kubernetes/cim/StatefulSet/ef-amq-statefulset.yaml file.
    2) Update AMQ Tag 
    gitimages.expertflow.com/general/activemq-k8s:5.17.1-alpine-zulu-K8s-4.5.1-4.5.1
    3) Add following parameters under evn section.
    
      - name : ACTIVEMQ_OPTS_MEMORY
        value : "-Xms512M -Xmx4G"
      - name: MAX_CONNECTIONS
        value: "50000"
    
    # Navigate to cim-solution/kubernetes directory
    cd cim-solution/kubernetes
    
    4) kubectl apply -f cim/StatefulSet/ef-amq-statefulset.yaml
  5. Update following core deployments.

    YAML
    # Update conversation-manager tag
    1) Open cim-solution/kubernetes/cim/Deployments/ef-conversation-manager-deployment.yaml file.
    2) Update tag gitimages.expertflow.com/cim/conversation-manager:4.5.1-SR4
    
    # Update agent-manager tag
    3) Open cim-solution/kubernetes/cim/Deployments/ef-agent-manager-deployment.yaml file.
    4) Update tag gitimages.expertflow.com/cim/agent-manager:4.5.1-SR3
    
    # Update routing-engine tag
    5) Open cim-solution/kubernetes/cim/Deployments/ef-routing-engine-deployment.yaml file.
    6) Update tag gitimages.expertflow.com/cim/media-routing-engine:4.5.1-SR1
    
    # Update channel-manager tag
    7) Open cim-solution/kubernetes/cim/Deployments/ef-ccm-deployment.yaml file.
    8) Update tag gitimages.expertflow.com/cim/customer-channel-manager:4.5.1-SR1
    
    # Update reporting-connector tag
    9) Open cim-solution/kubernetes/pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml file.
    10) Update tag gitimages.expertflow.com/cim/reporting-connector:4.5.1-SR2
  6. Run the following command to deploy historical-reporting-manager component.

    CODE
    # Update the FQDN in following files:
       1) cim/ConfigMaps/ef-historical-reporting-configmap.yaml
       2) cim/Services/ef-historical-reports-service.yaml
       3) cim/Ingresses/nginx/ef-historical-reports-Ingress.yaml
       
    # Apply the changes in folllwing files: 
    kubectl apply -f cim/ConfigMaps/ef-historical-reporting-configmap.yaml
    kubectl apply -f cim/Services/ef-historical-reports-service.yaml
    kubectl apply -f cim/Ingresses/nginx/ef-historical-reports-Ingress.yaml
  7. Run the MySQL update script on top of current historical database from CX-4.5.1/cim-solution/kubernetes/pre-deployment/reportingConnector/dbScripts/dbupdate/historical_reports_db_update_script_MYSQL.sql.sql

Make sure that you have already executed the MySQL update script for 4.5 before executing the update script for 4.5.1.

  1. Run the following command to create configMap for reporting-connector.

    CODE
    # Create configmap
    kubectl -n expertflow create configmap ef-reporting-connector-conf --from-file=pre-deployment/reportingConnector/reporting-connector.conf
  2. Start all core components.

    YAML
    # Apply all deployments
    kubectl apply -f cim/Deployments
    
    # Run reporting-connector cron job
    kubectl apply -f pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml -n expertflow

Setup WebRTC Secure Link Deployment

Before proceeding with the deployment, make sure that the Expertflow CX is minimum 4.5 version.

Description:

The WebRTC Video Call feature via secure link enhances the customer widget by allowing standalone video calls without relying on the chat features.

For Feature Deployment follow this document: https://expertflow-docs.atlassian.net/l/cp/cy700pqv

For Feature Guide Documentation follow : https://expertflow-docs.atlassian.net/l/cp/uDWvJoic

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.