Exchange Listener synchronization service
Glossary Item Box
The Exchange Listener synchronization service synchronizes Creatio with MS Exchange and IMAP/SMTP mail services using a subscription mechanism.
Exchange Listener synchronization service workflow
The service consists of two required components:
- The Exchange Listener primary module.
- NoSQL Redis DBMS.
Exchange Listener module
The Exchange listener module uses the mailbox credentials and creates a subscription to “new message” events. The open subscription remains in the component memory to ensure fast response time when new emails arrive. When a corresponding event is received, the email instance loads. Using an in-memory repository will be enough for deploying the service.
NoSQL Redis DBMS
Redis DBMS enables creating a scalable and fault-tolerant system of processing nodes. The Redis repository contains information about the mailboxes that are served. This lets any container process Creatio queries for adding a new subscription or check the status of a specific subscription regardless of the subscription node.
Requirements to Redis:
- Anonymous access allowed.
- Separate database available for the Exchange Listener service operation.
Exchange Listener synchronization service scalability
By default, separate nodes of the StatefulSet type process the requests based on 1 processor replica per 50 active mailboxes. The number of replicas depends on the replicaCount parameter. You can increase the number of processors by specifying the needed value. You can configure automatic scaling depending on the number of active subscriptions. To learn more, contact the Creatio technical support service.
Exchange Listener synchronization service compatibility with Creatio products
The Exchange Listener synchronization service version 1.0 (MS Exchange support) is compatible with all Creatio products of version 7.15.2 and up.
The Exchange Listener synchronization service version 2.0 (IMAP/SMTP support) is compatible with all Creatio products of version 7.16 and up.
Exchange Listener synchronization service deployment options
We recommend using the Kubernetes orchestrator and Helm package manager to deploy the service and ensure the operation of the application in the production environment. Learn more about deploying the synchronization service via Kubernetes in the “Deploying the synchronization service via Kubernetes” article.
You can also use Docker to speed up the deployment in the development environment. Learn more about deploying a containerized version of the synchronization service in the “Deploying the synchronization service in Docker” article.
See Also
