You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.

This configuration is part of the ongoing effort to separate the Process Engine from the Runtime and to support more DCM features natively in Blueriq. It may change over time. Please check release notes and upgrade instructions when using it.

For the Case Engine, 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 not be processed by the Case Engine and 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.

If you are configuring RabbitMQ for the Case Engine, follow these steps:

  1. Create four exchanges where events will be published on:
    1. Create an exchange where RabbitMQ will publish failed intake events to, e.g. dcmIntakeEventDlx. The type of this exchange should be 'fanout'.
    2.  Create an exchange where the runtime will publish intake events to, e.g. dcmIntakeEvents. The type of this exchange should be 'fanout'.
    3.  Create an exchange where the Case Engine will publish timer events to, e.g. dcmScheduledEvents. The type of this exchange should be 'fanout'.
  2. Create two queues where events will be published on:
    1. Create a queue where the RabbitMQ will publish failed intake events to, e.g. dcmIntakeEventsQueueDlq. 
    2. Create a queue where the runtime will publish intake events on, e.g. dcmIntakeEventsQueue. 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. Bind the queues to their respective exchanges
    1. Open the exchange created in step 1a and add a binding to the queue created in step 2a.
    2. Open the exchange created in step 1b and add a binding to the queue created in step 2b.
    3. Open the exchange created in step 1c and add a binding to the queue created in step 2b.
  4. Configure the properties to include the queues and exchanges
    1. Configure the exchange name created in step 1b in the Service call type: DCM_CaseCreate configuration and the queue name, configured in step 2b, in the Case Engine Properties configuration.
    2. Configure the exchange name created in step 1c in the Case Engine Properties configuration.
  • No labels

Didn't find the answer you were looking for? Try the advanced search!