Component Architecture
Hybrid Chat Solution Components
|
Component Name |
Description |
Profile name |
|---|---|---|
|
Customer-Channel-Manager |
Customer Channel Manager (CCM) is the component for connecting customer channels such as Facebook and Viber. See Customer Channels for all supported channels and channel capabilities. The docker-compose file for Customer Channel Manager is located at <install-dir>/sds/docker-compose-ccm.yml and for HA deployment, docker-compose file is located at <install-dir>/sds/docker-compose-ha-ccm.yml. APIs exposed and consumed by Channel Manager are documented on CCM 3.x APIs. See Channel Manager for component configurations. |
|
|
Routing Engine |
Media Routing Engine (MRE) queues and routes requests to available agents. This component contains following Docker services:
|
|
|
HC-Server |
Hybrid-Chat primary components including bot-connector, chat-server, and file-engine. |
|
|
Database-Connector |
This component exposes APIs for database access. It also consumes AMQ queues for storing events in the underlying database. |
|
|
Customer-Gadget |
It's the web-chat gadget component. |
|
|
Agent-Gadget |
Deploys an interface for Support Staff's interaction interface |
|
|
ActiveMQ |
Active MQ Publisher/subscriber-based Messaging platform used for Hybrid-Chat components communication and services |
|
|
Campaigns |
Campaigns Management |
|
|
KnowledgeBase |
Articulate Bot for an automated action/response, assisting the Support Staff |
|
|
EABC |
Defines business calendar and holidays |
|
|
User Management Module |
Basic User Management Module with a web-based interface to do user/group manipulation. |
|
|
Service-Gateway |
Nginx based Application layer routing, also responsible for failover routing in case of High Availability deployments. This only applies to the application level. |
|
|
Rasa |
To install local rasa bot with rasa x. |
|
|
MySQL |
Backend database service for the User Management Module. |
|
|
Mongo |
primary database component for storing and retrieval of Hybrid-Chat-related historical data includes chat histories and other information. |
|
|
Load Balancer |
HAProxy based Layer4 load-balancer. Primarily runs on a separate node in a High Availability deployment model. |
|