Skip to main content
Skip table of contents

Docker-based Deployment

Follow this guide to install Hybrid Chat on Linux in a simplex or redundant fashion. 

Deployment Planning

Please make sure that Solution Prerequisites are met for the desired deployment type. 

For High Availability deployment, see the architecture and components on High Availability with Redundant Deployment

Installation Instructions

  1. For installing 3.18.0 download script To upgrade from 3.10.2 & later versions to 3.18.0, follow Upgrade Guide
  2. Make the script executable.

    $ chmod a+x
  3. Start the execution of the script with the below-given command. 

    $ ./
  4. Deployment Option - Choose any of the following installation options.

    QuestionPossible Options

    If you do not already have a bot set up in your environment. It will setup:

    1. Rasa with Rasa X 
      1. After Rasa with RasaX is installed, open <install-dir>/sds/docker-compose-rasa-x.yml with any text editor and set the replicas value equal to the number of CPUs available in the host machine e.g.


            <<: *default-rasa-service
              <<: *rasa-credentials
              RASA_ENVIRONMENT: "production"
              DB_DATABASE: "tracker"
              RASA_MODEL_SERVER: "http://rasa-x:5002/api/projects/default/models/tags/production"
              mode: replicated
              replicas: 8
      2. Perform an Up operation for all the containers using efutils 
    2. Articulate 

    It's recommended to install the bot on a separate system because of its NLU component's resource utilization requirements.  

    2Hybrid-ChatIt will install the Hybrid Chat solution either in a simplex or redundant fashion. The script installs the solution either standalone or integrated with Cisco UCC. You can also specify external SQL Server credentials that may alter be integrated with Cisco CUIC for reporting. 
    3Integrate-botTo integrate the Bot with Hybrid Chat. This requires Hybrid Chat and the Bot already installed.
    4Customer gadgetTo install the Customer widget on a web-server. This is usually installed in a DMZ for exposing customer widget from a public website.
  5. Deployment Path

    Deployment PathDefault
    DEPLOYMENT_PATH/var/lib/expertflow – This is the default path unless otherwise changed.
  6. For HA deployment, consider the following: 

    1Load Balancer 

    Select this type of node when deploying the current system as a local load-balancer. The basic purpose of this machine is to provide a Layer4 routing between both sites ( master and slave).  Both Master and Slave nodes must be able to communicate with the Load-Balancer node to evolve application  and system load balancing

    2Master Select this type of node when deploying a master or active node in High availability mode. This system will be serving all the requests by default.
    3Slave Select this type of node when deploying a slave or passive node in High Availability mode. This system is configured for a takeover role when the Master system goes down.

    An optional node to be deployed at a neutral location 

    5ReplicaSet NameAutomatically setup during deployment
    6Mongo Replica Set Configuration

    No configuration required for MongoDB in 3.16.x. This process is now automated and doesn't require any additional steps.

  7. Apply licenses by following this document.

General Administration

Use the utility efutils to perform routine operations such as up/down/restart services and docker profiles. For complete details, see efutils


  • Separate deployment of Customer-Gadget via deployment script is not functional. 
  • In redundant deployment, component-level failover will not work. It means if any of the Hybrid Chat components is down you'll need to down the solution on the primary side and run from the secondary machine. 

    Down the solution on primary

    $ efutils all down
JavaScript errors detected

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

If this problem persists, please contact our support.