Page History
...
All names below can be changed if needed however, the 'dlx.' prefix for dead letter exchanges is mandatory and the dead letter exchange name should be the same as its corresponding exchange.
Producing Component(s) | Exchange | Queue | Consuming Component(s) | Dead letter exchange | Dead letter queue |
Case Engine, Runtime | dcmEvents | dcmEventsQueue | Case Engine | dlx.dcmEvents | dcmEventsDlq |
Case Engine | dcmListsEvents | dcmListsServiceEventsQueue | DCM Lists Service | dlx.dcmListsEvents | dcmListsServiceEventsDlq |
Case Engine | dcmMaintenanceEvents | dcmMaintenanceEventsQueue | DCM Maintenance App | dlx.dcmMaintenanceEvents | dcmMaintenanceEventsDlq |
Case Engine | dcmScheduledEvents* | dcmEventsQueue | Case Engine | dlx.dcmScheduledEvents | dcmScheduledEventsDlq |
Case Engine | dcmTasksEvents | dcmTasksEventsQueue | Runtime | dlx.dcmTasksEvents | dcmTasksEventsDlq |
Case Engine, Runtime | timelineEvents | timelineQueue | Case Engine OR Runtime | dlx.timelineEvents | timelineDlq |
Case Engine, Runtime | traceEvents | traceQueue | Case Engine OR Runtime | dlx.traceEvents | traceDlq |
| Audit Consumer | auditEvents | auditEventsQueue | Case Engine or Runtime | dlx.auditEvents | auditEventsDlq |
* This exchange publishes to the same queue as the dcmEvents exchange.
...
We have implemented the concurrentConsumers and maxConcurrentConsumers properties, which will affect the concurrent consuming of messages from the queue. More on these properties can be found here: Listener concurrency.
The property page of each component will show the properties to use. Please note the considerations on the following page: Deployment considerations DCM.
Overview
Content Tools