Skip to main content
Skip table of contents

CX Upgrade Guide CX-4.4.8 to CX-4.5.1

The upgrade must be done while the system is inactive. Active state of the system is removed as the application's Object model is changed.

There are significant changes to the Object Model. It is highly recommended to take a backup of existing databases (Mongo, PostgreSQL) before proceeding with the upgrade.

Remove Active State

  1. Open the redis shell

    CODE
    kubectl exec -n ef-external -it redis-master-0 -- redis-cli -a Expertflow123
  2. Run the following command inside the redis shell

    CODE
    flushall
  3. Verify if redis is flushed. Run the following command in the redis shell, it should return (empty array) response

    CODE
    keys *
  4. Enter ctrl + c to get out of the redis shell

Stop all core components

CODE
# Navigate to the following folder of the existing release i.e. CX-4.4.8
cd cim-solution/kubernetes
kubectl delete -f cim/Deployments

kubectl delete -f cim/StatefulSet/ef-amq-statefulset.yaml

kubectl delete -f pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml -n expertflow

kubectl -n expertflow delete configmap ef-reporting-connector-conf

Download New Release

  1. Clone the new CX-4.5.1 release

    CODE
    git clone -b CX-4.5.1 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git
  2. Navigate to the cim-solution/kubernetes folder in the newly cloned release

    CODE
    cd cim-solution/kubernetes

Update MongoDB Application Data

  1. Copy the upgrade script to the Mongo container

    CODE
    kubectl -n ef-external cp scripts/mongo/4.4-4.5_upgrade.js mongo-mongodb-0:/tmp/4.4-4.5_upgrade.js
  2. Execute the script

    CODE
    kubectl -n ef-external exec -ti mongo-mongodb-0 -- mongosh --file /tmp/4.4-4.5_upgrade.js

Update Reporting Connector

  1. Run the MySQL database update script in pre-deployment/reportingConnector/dbScripts/sqlupdate directory to get the latest database schema.
    Execute the scripts in the following sequence :

    1. mysql update 4.4.8 to 4.5.1.sql

  2. Update Reporting connector conf file

    CODE
    # Update following value in, cim-solution/kubernetes/pre-deployment/reportingConnector/reporting-connector.conf
      1) # This represents the maximum boundary for looped ETL jobs and is strongly recommended not to be altered.
          upper_limit=100
          
    # Create configmap
    kubectl -n expertflow create configmap ef-reporting-connector-conf --from-file=pre-deployment/reportingConnector/reporting-connector.conf
          
    # kubectl apply -f pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml -n expertflow

Update Grafana

  1. open kubernetes/external/bitnami/grafana/values.yaml

CODE
add the following lines under "dashboardsConfigMaps" section

  - configMapName: <configmap-map-name-supervisor-dashboard>
    folderName: default
    fileName: <file-name-supervisor-dashboard>

  - configMapName: <configmap-map-name-agent-dashboard>
    folderName: default
    fileName: <file-name-agent-dashboard>
    
    Step 1: above
    Step 2: Copy files both
    Step 3: Delete configMap (only supervisor)
    Step 4: Create configMaps (both)
    Step 5: Sed cmds
    Step 6: Uninstall and Install
    
  1. copy the Agent_Dashboard_CIM-mssql.json and Agent_Dashboard_CIM-mysql.json files from the following path kubernetes/post-deployment/config/grafana/supervisor-dashboards.

  2. Completely uninstall grafana using the commands in the grafana section. Link to uninstallation guide.

For MySQL

Apply configmap for the MySQL supervisor and agent dashboard files using the steps below.

  1. supervisor dashboard MySQL

CODE
kubectl create configmap ef-grafana-supervisor-dashboard-mysql -n ef-external --from-file=post-deployment/config/grafana/supervisor-dashboards/Supervisor_Dashboard_CIM-mysql.json

agent dashboard MySQL

CODE
kubectl create configmap ef-grafana-agent-dashboard-mysql -n ef-external --from-file=post-deployment/config/grafana/supervisor-dashboards/Agent_Dashboard_CIM-mysql.json

For release CX-4.1 onwards

  1. Use following the config map name and file name parameter for grafana

    CODE
    ###### supervisor dashboard ######
    sed -i -e 's@configMapName: <configmap-map-name-supervisor-dashboard>@configMapName: ef-grafana-supervisor-dashboard-mysql@' external/bitnami/grafana/values.yaml
    sed -i -e 's@fileName: <file-name-supervisor-dashboard>@fileName: Supervisor_Dashboard_CIM-mysql.json@' external/bitnami/grafana/values.yaml
    
    ###### agent dashboard ######
    sed -i -e 's@configMapName: <configmap-map-name-agent-dashboard>@configMapName: ef-grafana-agent-dashboard-mysql@' external/bitnami/grafana/values.yaml
    sed -i -e 's@fileName: <file-name-agent-dashboard>@fileName: Agent_Dashboard_CIM-mysql.json@' external/bitnami/grafana/values.yaml

For MSSQL Server

  1. Apply configmap for the MSSQL supervisor dashboard files using the steps below.
    supervisor dashboard MSSQL

    CODE
    kubectl create configmap ef-grafana-supervisor-dashboard-mssql -n ef-external --from-file=post-deployment/config/grafana/supervisor-dashboards/Supervisor_Dashboard_CIM-mssql.json

agent dashboard MSSQL

CODE
kubectl create configmap ef-grafana-agent-dashboard-mssql -n ef-external --from-file=post-deployment/config/grafana/supervisor-dashboards/Agent_Dashboard_CIM-mssql.json

For release CX-4.1 onwards

  1. Use following the config map name and file name parameter for Grafana

CODE
###### supervisor dashboard ######
sed -i -e 's@configMapName: <configmap-map-name>@configMapName: ef-grafana-supervisor-dashboard-mssql@' external/bitnami/grafana/values.yaml
sed -i -e 's@fileName: <file-name>@fileName: Supervisor_Dashboard_CIM-mssql.json@' external/bitnami/grafana/values.yaml

###### agent dashboard #######
sed -i -e 's@configMapName: <configmap-map-name-agent-dashboard>@configMapName: ef-grafana-agent-dashboard-mssql@' external/bitnami/grafana/values.yaml
sed -i -e 's@fileName: <file-name-agent-dashboard>@fileName: Agent_Dashboard_CIM-mssql.json@' external/bitnami/grafana/values.yaml
  1. Use the following Helm command to deploy grafana:

CODE
helm upgrade --install=true --wait=true --timeout=10m0s --debug --namespace=ef-external --values=external/bitnami/grafana/values.yaml grafana  external/bitnami/grafana

Delete Scheduler Database

  1. Open the database shell

    1. Run the following command

      CODE
      helm -n ef-external status ef-postgresql
    2. Follow these steps to connect to the database shell

      CODE
      # The above command will return some steps to connect to postgresql client.
      
      # Step 1
      # Execute the command returned after the text "To get the password for "postgres" run:"
      # It should be starting with keyword "export"
      
      # Step 2
      # Execute the next command returned after the text "To get the password for "sa" run:"
      # It should be starting with keyword "export"
      
      # Step 3
      # Execute the next command returned after the text "To connect to your database run the following command:"
      # It would be in 3 lines, copy and paste all of it and press enter to execute it. 
  2. In the database shell execute the following command to delete the scheduler database

    CODE
    DROP DATABASE IF EXISTS scheduler;
  3. Verify if database is deleted; schedular database should not appear after running the following command in the database shell

    CODE
    \l+
  4. Enter \q to get out of the database shell

Update Active MQ Deployment

CODE
# Navigate to the following folder of the existing release i.e. CX-4.4.8
cd cim-solution/kubernetes

1) open StatefulSet/ef-amq-statefulset.yaml
Add the following ConfigMaps variable under env section

           name: ACTIVEMQ_OPTS_MEMORY
           value: "-Xms512M -Xmx4G"
             
2) Change the image tag            
image: gitimages.expertflow.com/general/activemq-k8s:5.17.1-alpine-zulu-K8s-4.5.1-4.5.1             

Update following ConfigMaps

CODE
# Update Common enviroment Configmap
  Open cim/ConfigMaps/ef-common-environment.yaml add the following variables
    DEFAULT_ROOM_NAME: CC
    DEFAULT_ROOM_DESCRIPTION: Contact Center Room
    DEFAULT_ROOM_LABEL: CC
    ROOM_IS_USER_ID: "false"
    TZ: UTC

# Update Agent Manager Configmap
  Open cim/ConfigMaps/ef-agent-manager-configmap.yaml add the following variable.
    FINESSE_URL: https://uccx12-5p.ucce.ipcc:8445
 
# Update Conversation manager Configmap 
  Open cim/ConfigMaps/ef-conversation-manager-configmap.yaml add the following variables
    UNIFIED_ADMIN_URL: http://ef-unified-admin-svc:3000

### Update Customer widget ConfigMap
    Open cim/ConfigMaps/ef-customer widget-configmap.yaml add the following variables
      AUTHENTICATOR_URL: https://cim.expertflow.com/secure-link
      ENABLE_LOGO: "false"
      ADDITIONAL_PANEL: "true"
  
### Update Scheduled Activities Configmap
    Open  cim/ConfigMaps/ef-scheduled-activities-configmap.yaml
    Remove following varibales
      DB_DIALECT: org.hibernate.dialect.PostgreSQLDialect
      DB_PASSWORD: Expertflow123
      DB_URL: jdbc:postgresql://ef-postgresql.ef-external.svc.cluster.local:5432/scheduler
      DB_USERNAME: sa

    Add following varibales 
      CACHED_OUTBOUND_MESSAGE_EXPIRY_IN_SECONDS: "86400"
      COUNT_OF_WEBHOOK_NOTIFICATION_RETRY_ATTEMPTS: "5"
      WEBHOOK_NOTIFICATION_RETRY_TIMEOUT_IN_SECONDS: "1800"

# Update State event logger Configmap
  Open ef-state-events-logger-configmap.yaml and change the value of following variable
    TOPIC_NAME: VirtualTopic.STATE_CHANNEL

# Update Unified agent Configmap
  Open cim/ConfigMaps/ef-unified-agent-configmap.yaml and add the following variables
    isCrmEventsEnabled: "false"
    SECURE_LINK_URL: https://devops.ef.com/secure-link
    finesseURLForAgent: https://122.129.75.138:8445
    ENABLE_SECURE_LINK: "false"
    Enable_Voice_Events_For_CRM: "false"
    IS_FINESSE_HA_ENABLED: "false"
    SECONDARY_FINESSE_URL: https://finesse12-5.ucce.ipcc:8445
    CISCO_SERVICE_IDENTIFIER: "0000"

Update following Deployment

CODE
# Update 360 Connector Deployment

1)Open cim/Deployments/ef-360-connector-deployment.yaml

             - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
                  
2)Change the image tag
   image: gitimages.expertflow.com/cim/360-connector:4.5

# Update Agent Manager Deployment

1) Open cim/Deployments/ef-agent-manager-deployment.yaml Add following parameters under evn section.
            - name: FINESSE_URL
              valueFrom:
                configMapKeyRef:
                  key: FINESSE_URL
                  name: ef-agent-manager-cm
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm                  

3) Change the image 
   tag : gitimages.expertflow.com/cim/agent-manager:4.5_f-CIM-14086


# Update Bot framework Deployment
1)Open cim/Deployments/ef-bot-framework-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
                  
2)Change the image tag
   image: gitimages.expertflow.com/cim/bot-framework:4.5.1_f-CIM-14085                  

# Update CCM Deployment
1)Open cim/Deployments/ef-ccm-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
                  
2)Change the image tag
   image: gitimages.expertflow.com/cim/customer-channel-manager:4.5.1_f-CIM-14085

# Update CIM CUSTOMER Deployment
1)Open cim/Deployments/ef-cim-customer-configmap.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
2)Change the image tag

image: gitimages.expertflow.com/cim/cim-backend:4.4

# Update Conversation manager Deployment

1)Open cim/Deployments/ef-conversation-manager-deployment.yaml

#add this line name: variables-common-env-cm  under "wait-for" initcontainer             
      initContainers:      
      containers:
        - envFrom:
            - configMapRef:
                 name: variables-common-env-cm
2)Change the image tag of initcontainer
   image: gitimages.expertflow.com/cim/conversation-controller:4.5.1-CIM-14085
   
3)Change the image tag of Main container
image: gitimages.expertflow.com/cim/conversation-manager/build:4.5.1_b-CIM-15064-ff0e8e06704c7a1c51dac8f81eb5d072b568c059



# Update Customer widget Deployment

1)Open cim/Deployments/ef-customer-widget-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
            - name: AUTHENTICATOR_URL
              valueFrom:
                configMapKeyRef:
                  key: AUTHENTICATOR_URL
                  name: ef-customer-widget-cm
            - name: ENABLE_LOGO
              valueFrom:
                configMapKeyRef:
                  key: ENABLE_LOGO
                  name: ef-customer-widget-cm
            - name: ADDITIONAL_PANEL
              valueFrom:
                configMapKeyRef:
                  key: ADDITIONAL_PANEL
                  name: ef-customer-widget-cm                  
                  
2)Change the image tag
   image: gitimages.expertflow.com/efpublic/customer-widget:4.5
   
# Update Facebook Connector Deployment
1)Open cim/Deployments/ef-facebook-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
   image: gitimages.expertflow.com/cim/facebook-connector:4.5.1-SR1  
   
# Update file engine Deployment

1)Open cim/Deployments/ef-file-engine-deployment.yaml
    Change the image tag
   image: gitimages.expertflow.com/chat-solution/file-engine:4.5

# Update Historical reports Deployment
1)Open cim/Deployments/ef-historical-reports-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/historical-reports-manager:4.5.1-SR2

# Update Instagram Connector Deployment
1)Open cim/Deployments/ef-instagram-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/instagram-connector:4.5

# Update Licence Manager Deployment
1)Open cim/Deployments/ef-licence-manager-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/license-mangement/license-manager:4.5

# Update Realtime reports Deployment
1)Open cim/Deployments/ef-realtime-reports-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/realtime-reports-manager:4.5.1_f-CIM-14085

# Update Routing engine Deployment
1)Open cim/Deployments/ef-routing-engine-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/media-routing-engine:4.5.1_f-CIM-14085

# Update Scheduled Activities

1)Open cim/Deployments/ef-scheduled-activities-deployment.yaml

Remove following varibales 
            - name: DB_PASSWORD
              valueFrom:
                configMapKeyRef:
                  key: DB_PASSWORD
                  name: ef-scheduled-activities-cm
            - name: DB_URL
              valueFrom:
                configMapKeyRef:
                  key: DB_URL
                  name: ef-scheduled-activities-cm
            - name: DB_USERNAME
              valueFrom:
                configMapKeyRef:
                  key: DB_USERNAME
                  name: ef-scheduled-activities-cm
            - name: DB_DIALECT
              valueFrom:
                configMapKeyRef:
                  key: DB_DIALECT
                  
                  
Add following varibales
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
            - name: REDIS_HOST
              valueFrom:
                configMapKeyRef:
                  key: REDIS_HOST
                  name: ef-connection-env-cm
            - name: REDIS_MAX_ACTIVE
              valueFrom:
                configMapKeyRef:
                  key: REDIS_MAX_ACTIVE
                  name: ef-connection-env-cm
            - name: REDIS_MAX_IDLE
              valueFrom:
                configMapKeyRef:
                  key: REDIS_MAX_IDLE
                  name: ef-connection-env-cm
            - name: REDIS_MAX_WAIT
              valueFrom:
                configMapKeyRef:
                  key: REDIS_MAX_WAIT
                  name: ef-connection-env-cm
            - name: REDIS_MIN_IDLE
              valueFrom:
                configMapKeyRef:
                  key: REDIS_MIN_IDLE
                  name: ef-connection-env-cm
            - name: REDIS_PASSWORD
              valueFrom:
                configMapKeyRef:
                  key: REDIS_PASSWORD
                  name: ef-connection-env-cm
            - name: REDIS_PORT
              valueFrom:
                configMapKeyRef:
                  key: REDIS_PORT
                  name: ef-connection-env-cm
            - name: REDIS_SSL_ENABLED
              valueFrom:
                configMapKeyRef:
                  key: REDIS_SSL_ENABLED
                  name: ef-connection-env-cm
            - name: REDIS_TIMEOUT
              valueFrom:
                configMapKeyRef:
                  key: REDIS_TIMEOUT
                  name: ef-connection-env-cm
            - name: REDIS_SENTINEL_ENABLE
              valueFrom:
                configMapKeyRef:
                  key: REDIS_SENTINEL_ENABLE
                  name: ef-connection-env-cm
            - name: REDIS_SENTINEL_MASTER
              valueFrom:
                configMapKeyRef:
                  key: REDIS_SENTINEL_MASTER
                  name: ef-connection-env-cm
            - name: REDIS_SENTINEL_NODES
              valueFrom:
                configMapKeyRef:
                  key: REDIS_SENTINEL_NODES
                  name: ef-connection-env-cm
            - name: REDIS_SENTINEL_PASSWORD
              valueFrom:
                configMapKeyRef:
                  key: REDIS_SENTINEL_PASSWORD
                  name: ef-connection-env-cm                  
            - name: CACHED_OUTBOUND_MESSAGE_EXPIRY_IN_SECONDS
              valueFrom:
                configMapKeyRef:
                  key: CACHED_OUTBOUND_MESSAGE_EXPIRY_IN_SECONDS
                  name: ef-scheduled-activities-cm
            - name: COUNT_OF_WEBHOOK_NOTIFICATION_RETRY_ATTEMPTS
              valueFrom:
                configMapKeyRef:
                  key: COUNT_OF_WEBHOOK_NOTIFICATION_RETRY_ATTEMPTS
                  name: ef-scheduled-activities-cm
            - name: WEBHOOK_NOTIFICATION_RETRY_TIMEOUT_IN_SECONDS
              valueFrom:
                configMapKeyRef:
                  key: WEBHOOK_NOTIFICATION_RETRY_TIMEOUT_IN_SECONDS
                  name: ef-scheduled-activities-cm                        
                  
2)Change the image tag
  image: gitimages.expertflow.com/campaign-manager/campaign-scheduler:4.5
  

# Update SMPP connector Deployment
1)Open cim/Deployments/ef-smpp-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
 image: gitimages.expertflow.com/cti/hc_smpp_connector:4.5

# Update State event logger Deployment

1)Open cim/Deployments/ef-state-events-logger-deployment.yam
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/state-events-logger/build:4.5.1_b-CIM-15144-82d8cf35759585eee519edaa6b4373134e5dea5f

# Update Team Announcement Deployment
1)Open cim/Deployments/ef-team-announcement-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm   

# Update Telegram connector Deployment
1)Open cim/Deployments/ef-telegram-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/telegram-connector/build:4.5.1_b-CIM-15144-15_07_2024-16_17_34

# Update twillio connector Deployment
1)Open cim/Deployments/ef-twilio-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/twilio-connector:4.5
  
# Update Unified admin Deployment
1)Open cim/Deployments/ef-unified-admin-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/unified-admin:4.5


# Update Unified agent Deployment

1)Open cim/Deployments/ef-unified-agent-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
            - name: isCrmEventsEnabled
              valueFrom:
                configMapKeyRef:
                  key: isCrmEventsEnabled
                  name: ef-unified-agent-cm
            - name: SECURE_LINK_URL
              valueFrom:
                configMapKeyRef:
                  key: SECURE_LINK_URL
                  name: ef-unified-agent-cm
            - name: finesseURLForAgent
              valueFrom:
                configMapKeyRef:
                  key: finesseURLForAgent
                  name: ef-unified-agent-cm
            - name: ENABLE_SECURE_LINK
              valueFrom:
                configMapKeyRef:
                  key: ENABLE_SECURE_LINK
                  name: ef-unified-agent-cm
            - name: Enable_Voice_Events_For_CRM
              valueFrom:
                configMapKeyRef:
                  key: Enable_Voice_Events_For_CRM
                  name: ef-unified-agent-cm
            - name: IS_FINESSE_HA_ENABLED
              valueFrom:
                configMapKeyRef:
                  key: IS_FINESSE_HA_ENABLED
                  name: ef-unified-agent-cm
            - name: SECONDARY_FINESSE_URL
              valueFrom:
                configMapKeyRef:
                  key: SECONDARY_FINESSE_URL
                  name: ef-unified-agent-cm
            - name: CISCO_SERVICE_IDENTIFIER
              valueFrom:
                configMapKeyRef:
                  key: CISCO_SERVICE_IDENTIFIER
                  name: ef-unified-agent-cm
                  
2) add volume following volume mount under volume mount section
         volumeMounts:
            - name: ef-crm-service
              mountPath: /usr/share/nginx/html/assets/cti/crm/
            - name: ef-canned-messages
              mountPath: /usr/share/nginx/html/assets/canned-messages/
      volumes:
         - name: ef-crm-service
           configMap:
             name: ef-crm-service-cm
         - name: ef-canned-messages
           configMap:
             name: ef-canned-messages-cm                                              
                  
3)Change the image tag
  image: gitimages.expertflow.com/cim/unified-agent:4.5.1_f-CIM-13418


# Update Viber connector Deployment
1)Open cim/Deployments/ef-viber-connector-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
Change the image tag
image: gitimages.expertflow.com/cim/viber-connector:4.5
  

# Update Web Channel Manager Deployment
1)Open cim/Deployments/ef-web-channel-manager-deployment.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm      
                  
2)Change the image tag
  image: gitimages.expertflow.com/cim/web-channel-manager:4.5

Update following Ingress

CODE
### Update Scheduled Activities Ingress

#for nginx
1) Open cim/Ingresses/nginx/ef-scheduled-activities-Ingress.yaml
                port:
                  number: 8894
#for traefik
1) Ingresses/traefik/ef-scheduled-activities-Ingress.yaml
                port:
                  number: 8894

### Update twitter connector Ingress

#for nginx
1) open kubernetes/cim/Ingresses/nginx/ef-twitter-connector-Ingress.yaml  
  port:
    number: 8080     
#for traefik
2) open kubernetes/cim/Ingresses/traefik/ef-twitter-connector-Ingress.yaml                  

                port:
                  number: 8080                                                  

### Update RASA-X

CODE
Change the image tag under the app section
tag: "4.5"

Update Static Resources

Run the following commands to load the latest application icons and other media files

CODE
kubectl apply -f scripts/minio-helper.yaml
CODE
kubectl -n ef-external --timeout=90s wait --for=condition=ready pod minio-helper
CODE
kubectl -n ef-external cp post-deployment/data/minio/bucket/default minio-helper:/tmp/
CODE
kubectl -n ef-external cp scripts/icon-helper.sh minio-helper:/tmp/
CODE
kubectl -n ef-external exec -it minio-helper -- /bin/sh /tmp/icon-helper.sh
CODE
kubectl delete -f scripts/minio-helper.yaml

Copy the folder and replace in exact path of the current release

CODE
#Replace the AgentGadget.js 
Replace the file from following path new release 
kubernetes/post-deployment/3rdPartyResources/Finesse-gadget/AgentGadget.js

#Replace the "supervisor-dashboards" folder from following path
kubernetes/post-deployment/config/grafana/supervisor-dashboards

#Replace the "unified-agent" folder from following path
kubernetes/pre-deployment/app-translations/unified-agent

#Replace the "conversation-Controller" folder from following path
kubernetes/pre-deployment/conversation-Controller


#copy the folder "crm-service" from the following path
kubernetes/pre-deployment/crm-service

#Replace the "grafana" folder from following path
kubernetes/pre-deployment/grafana

Replace the  "licensemanager" folder from following path
kubernetes/pre-deployment/licensemanager

Replace the  "dbupdate" folder from following path
kubernetes/pre-deployment/reportingConnector/dbScripts/dbupdate

# Update reporting connector cron job
1)Open kubernetes/pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
Change the image tag
- image: gitimages.expertflow.com/cim/reporting-connector:4.5.1-SR2 



# Update reporting connector cron job
1)Open kubernetes/pre-deployment/team-announcement/ef-team-announcement-cronjob.yaml
            - name: TZ
              valueFrom:
                configMapKeyRef:
                  key: TZ
                  name: variables-common-env-cm
Change the image tag
- image: gitimages.expertflow.com/cim/reporting-connector:4.5.1-SR2


#Copy the "4.4-4.5_upgrade.js" folder from following path
kubernetes/scripts/mongo

create ConfigMap of PostgreSQL to create necessary databases and preload it with bootstrap configurations.

CODE
kubectl -n ef-external  create configmap ef-postgresql-license-manager-cm --from-file=./pre-deployment/licensemanager/licensemanager.sql

Apply the configuration defined in pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml file by the below command to run cron job for reporting-connector.

CODE
kubectl apply -f pre-deployment/reportingConnector/ef-reporting-connector-cron.yaml 

Setup default translation file for Agent Desk

CODE
kubectl -n expertflow  create configmap ef-app-translations-cm --from-file=pre-deployment/app-translations/unified-agent/i18n

Setup default canned messages translations file for Agent Desk

CODE
kubectl -n expertflow  create configmap ef-canned-messages-cm --from-file=pre-deployment/app-translations/unified-agent/canned-messages

Apply CRM ConfigMap for Agent Desk

CODE
kubectl -n expertflow create configmap ef-crm-service-cm --from-file=pre-deployment/crm-service/

Apply Conversation Controller ConfigMaps

CODE
# Delete the configmap

kubectl -n expertflow delete configmap ef-conversation-controller-actions-cm
kubectl -n expertflow delete configmap ef-conversation-controller-actions-utils-cm
# Apply the configmap

kubectl -n expertflow create configmap ef-conversation-controller-actions-cm --from-file=pre-deployment/conversation-Controller/actions
kubectl -n expertflow create configmap ef-conversation-controller-actions-utils-cm --from-file=pre-deployment/conversation-Controller/utils

Apply all configurations in the ConfigMaps folder using:

CODE
kubectl apply -f cim/ConfigMaps/

Apply all the Deployment manifests 

CODE
kubectl apply -f cim/Deployments/
JavaScript errors detected

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

If this problem persists, please contact our support.