Page History

...

Its possible to configure RabbitMQ manually using the following steps:

...

1. Create an exchange where the Case Engine and Runtime will publish DCM events to named dcmEvents. The type of this exchange should be 'fanout'.
2. Create an exchange where the Case Engine and Runtime will publish dead letter DCM events to named dlx.dcmEvents The type of this exchange should be 'fanout'.
3. Create an exchange where the Case Engine will publish DCM Lists Service events to named dcmListsEvents. The type of this exchange should be 'fanout'.
4. Create an exchange where the Case Engine will publish DCM Maintenance events to named dcmMaintenanceEvents. The type of this exchange should be 'fanout'.
5. Create an exchange where the Case Engine will publish scheduled events to named dcmScheduledEvents. The type of this exchange should be 'fanout'.
6. Create an exchange where the Case Engine will publish dead letter scheduled events to named dlx.dcmScheduledEvents. The type of this exchange should be 'fanout'.
7. Create an exchange where the Case Engine will publish task events to named dcmTasksEvents. The type of this exchange should be 'fanout'.
8. Create an exchange where the Case Engine will publish dead letter task events to named dlx.dcmTasksEvents. The type of this exchange should be 'fanout'.
9. Create an exchange where the Case Engine and Runtime will publish timeline events to named timelineEvents. The type of this exchange should be 'fanout'.
10. Create an exchange where the Case Engine and Runtime will publish trace events to named traceEvents. The type of this exchange should be 'fanout'.

...

1. Create a queue where RabbitMQ will publish failed DCM events to, e.g. dcmEventsDlq. 
2. Create a queue for the DCM events on, e.g. dcmEventsQueue. Configure the exchange created in step 1a as the dead letter exchange for this queue. You can do so by setting a x-dead-letter-exchange argument with the exchange name as its value.
3. Create a queue for the DCM List Service events, e.g. dcmListsServiceEventsQueue.
4. Create a queue for the DCM Maintenance events, e.g. dcmMaintenanceEventsQueue.
5. Create a queue where RabbitMQ will publish failed scheduled events on, e.g. dcmScheduledEventsDlq. Configure the exchange created in step 1e as the dead letter exchange for this queue. You can do so by setting a x-dead-letter-exchange argument with the exchange name as its value.
6. Create a queue where RabbitMQ will publish failed task events on, e.g. dcmTasksEventsDlq. Configure the exchange created in step 1g as the dead letter exchange for this queue. You can do so by setting a x-dead-letter-exchange argument with the exchange name as its value.
7. Create a queue for the task events, e.g. dcmTasksEventsQueue.
8. Create a queue for the timeline events, e.g. timelineQueue.
9. Create a queue for the trace events, e.g. traceQueue.

...

All exchanges are of type "fanout". For each exchange, create a binding for the corresponding queue on the right.

* This exchange publishes to the same queue as the dcmEvents exchange

...

.

Application properties

Its necessary to configure the right exchanges and queues in the right application, the following properties can be used.

...