Page History
...
- Create ten exchanges where events will be published on:
- Create an exchange where the Case Engine and Runtime will publish DCM events to named
dcmEvents.
The type of this exchange should be 'fanout'. - 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'. - Create an exchange where the Case Engine will publish DCM Lists Service events to named
dcmListsEvents
. The type of this exchange should be 'fanout'. - Create an exchange where the Case Engine will publish DCM Maintenance events to named
dcmMaintenanceEvents
. The type of this exchange should be 'fanout'. - Create an exchange where the Case Engine will publish scheduled events to named
dcmScheduledEvents
. The type of this exchange should be 'fanout'. - 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'. - Create an exchange where the Case Engine will publish task events to named
dcmTasksEvents
. The type of this exchange should be 'fanout'. - 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'. - Create an exchange where the Case Engine and Runtime will publish timeline events to named
timelineEvents
. The type of this exchange should be 'fanout'. - Create an exchange where the Case Engine and Runtime will publish trace events to named
traceEvents
. The type of this exchange should be 'fanout'.
- Create an exchange where the Case Engine and Runtime will publish DCM events to named
- Create nine queues where events will be published on:
- Create a queue where RabbitMQ will publish failed DCM events to, e.g.
dcmEventsDlq
. - 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. - Create a queue for the DCM List Service events, e.g.
dcmListsServiceEventsQueue
. - Create a queue for the DCM Maintenance events, e.g.
dcmMaintenanceEventsQueue.
- 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. - 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. - Create a queue for the task events, e.g.
dcmTasksEventsQueue.
- Create a queue for the timeline events, e.g.
timelineQueue.
- Create a queue for the trace events, e.g.
traceQueue.
- Create a queue where RabbitMQ will publish failed DCM events to, e.g.
- Bind the queues to their respective exchanges
- Bind the queue created in step 2b to the exchange created in step 1a.
- Bind the queue created in step 2c to the exchange created in step 1c and the exchange created in step 1e.
- Bind the queue created in step 2d to the exchange created in step 1d.
- Bind the queue created in step 2d to the exchange created in step 1a.
- Bind the queue created in step 2g to the exchange created in step 1h.
- Bind the queue created in step 2h to the exchange created in step 1i.
- Bind the queue created in step 2j to the exchange created in step 1h.
- Configure the properties to include the queues and exchanges. Note that only the queues and exchanges are shown. For other properties please reference the corresponding property pages.
Case Engine
- Add the following exchanges and queues to the Case Engine properties Case Engine Configuration (application-case-engine.properties):
- blueriq.case.engine.maintenance.rabbitmq.exchangeName=dcmMaintenanceEvents
- blueriq.case.engine.rabbitmq.queueNames=dcmEventsQueue
- blueriq.case.engine.rabbitmq.exchangeName=dcmEvents
- blueriq.case.engine.scheduler.rabbitmq.exchangeName=dcmScheduledEvents
- blueriq.process.engine.v2.automatic-task.rabbitmq.exchangeName=dcmTasksEvents
- If tracing is enabled add the the following to the Case Engine properties (application-trace-event-publisher-amqp.properties):
- blueriq.trace.event.publisher.channel.amqp.rabbitmq.exchangeName=traceEvents
- If the timeline is enabled add the following to the Case Engine properties (application-timeline-event-publisher-amqp.properties):
- blueriq.timeline.event.publisher.amqp.rabbitmq.exchangeName=timelineEvents
- For the Case Engine to communicate to the DCM Lists Service add the following to the Case Engine properties (application-dcm-lists-publisher.properties):
- blueriq.dcm.lists-publisher.rabbitmq.exchangeName=dcmListsEvents
Overview
Content Tools