...

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.

RabbitMQ

Its possible to configure RabbitMQ manually using the following steps:

...

* 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.

Note that not all properties have been described. The host, port, virtualHost, username, password etc. are ommited for brevity. Examples of the property files can be viewed at the page of its corresponding component.  

Case Engine

Add the following exchanges and queues to the Case Engine properties Case Engine Configuration (application-case-engine.properties):

...

blueriq.dcm.lists-publisher.rabbitmq.exchangeName=dcmListsEvents
...

Runtime

Add the following exchanges and queues to the Runtime properties

...

:

...

blueriq.dcm.rabbitmq.exchangeName=dcmEvents

...

...
blueriq.dcm.rabbitmq.queueNames=dcmTasksEventsQueue

...

...
blueriq.process.engine.v2.automatic-task.rabbitmq.exchangeName=dcmTasksEvents
...

If the Trace publisher is enabled add the the following to

...

the Runtime properties:

...

blueriq.trace.event.publisher.channel.amqp.rabbitmq.exchangeName=traceEvents
...

If the Trace SQL Store is enabled add the the following to the Runtime properties

...

:

...

blueriq.trace.event.listener.amqp.rabbitmq.queueNames=traceQueue
...

If the Timeline publisher is enabled add the following to the Runtime properties

...

:

...

blueriq.timeline.event.publisher.amqp.rabbitmq.exchangeName=timelineEvents
...

If the Timeline SQL Store is enabled add the following to the Runtime properties

...

:

...

blueriq.timeline.event.listener.amqp.rabbitmq.queueNames=timelineQueue
...