Environment Configurations
Chat solution comprises the following docker services.
| A mandatory component of the chat solution that must be setup. No change in these service parameters is required. This service is used by |
---|---|
| By default, the MySQL root user password is ‘root’. You can change it under the environment variable MYSQL_ROOT_PASSWORD. See more information about this standard docker container in the official MySQL documentation for docker-compose. This service is used by |
| This service is used by See (3.15 ) UMM Environment Variables for configuring Once all configuration is done, UMM service can be accessed with the URL https://<fqdn>/umm where FQDN is the hostname or IP of the host machine. |
| This service is used by Once all configurations are done, Mongo service can be accessed with URL mongo:port or mongo. If mongo service is configured on the default See MongoDB on Docker hub for modifying default environment parameters. |
| Used by the chat service for storing chat messages. See Database Connector Environment Variables for configuration parameters. These ports are exposed for the customer gadget and 3rd party applications to query chat solution via REST APIs. |
| Used to manage outbound SMS campaigns. See ECM environment variables for configuration parameter details. |
ccm | Customer Channel Manager (CCM) is the component for connecting customer channels such as Facebook and Viber. See (3.15 ) .Media Channels v3.12.1 for all supported channels and channel capabilities. |
ccmservices | See ccm environment variables for configuration parameter details. |
| See ecmservices environment variables for configuration parameter details. |
ecm-frontend | See ecm-frontend environment variables for configuration parameter details. |
| This service is required only for reporting with an external SQL server. Remove/comment out this service section if not needed. See CS Reporting Connector for modifying default environment configurations. |
| Chat Server is the main messaging core. See Chat environment variables for modifying default environment configurations. |
| Communication Server maintains the agent state for voice and non-voice MRDs. See Comm Server environment variables for modifying default environment configurations. |
| Agent gadget can be accessed with URL https://<fqdn>/agent-gadget/. See Agent gadget environment variables for modifying defaults. |
| The web widget to be embedded in the customer website is loaded from this service. See Customer Gadget and Web Callback environment variables for modifying defaults. Translations: customer-gadget/translations folders are created
|
| The bot connector connects the solution with rasa bot or articulate. See Bot Connector environment variables for modifying default configurations. This service is only required if Chat service BOT parameter value set to |
| This the knowledge-base UI application. See Knowledge Base UI environment variables for modifying defaults. |
| The Rasa NLU is used along with Articulate. It exposes HTTP port 5000 on the internal HTTP 5000 port. There is no environment variable settings. Just need to mount volumes |
| This is the Articulate dialogue manager API for Rasa NLU. It can be accessed via https://<fqdn>/articulate-hybrid-api. There is no environment variable to set. Only volumes need to be mounted |
| Duckling is a Haskell library that parses text into structured data. This is used with articulate and rasa NLU. It exposes HTTP 8000 port on internal 8500 port. There is no environment variable to set. Only volumes need to be mounted |
| Redis is NoSQL Cache DB which Articulate uses to cache some data. It exposes the 6379 port on the internal 6379 port. There is no environment variable to set only volumes need to be set. |
minio | MinIO is a cloud storage server released under Apache License v2, compatible with Amazon S3. For deployment related information, check Minio Environment Variables guide. |
file-engine | File Engine is a file stream API that is compatible with MinIO server. It entertains stream upload and download features. For deployment related information, consult File Engine Environment Variables guide. |
eabc | EABC is originally a microservice-based upon Supervisor Tools solution. Deployment variables can be found here. |