For the DCM setup, we use several queues and exchanges. We use dead letter queues to store messages that could not be processed, because an error occurred when processing. The error should be visible in the log file. Messages on these dead letter queues will be automatically retried by the DCM Maintenance Application. If it exceeds the configured amount of retries it should be reviewed manually by a system administrator instead. There is no notification mechanism for dead letter messages, so Blueriq advises to check the dead letter queues periodically.

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.

...

Manual configuration

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 and replaced by "..." in the configuration below. 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:

...

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

Runtime

Add the following exchanges and queues to the Runtime properties:

...

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

DCM Lists Service

Add the following queue to the DCM Lists Service properties:

blueriq:
  dcm:
    lists:
      event:
        consumer:
          rabbitmq:
            queueNames: dcmListsServiceEventsQueue
			...

DCM Maintenance App

Add the following to the DCM Maintenance App properties:

...