DCM 2.0 consists of multiple components that are linked to the Blueriq Runtime. Because these components are separated from each other, they need a way to communicate with each other. To do that, aside from using HTTP protocol, the AMQP (Advanced Message Queueing Protocol) is used. This technology enables multiple components to send messages to each other via multiple so-called queues. Queues are essential components for the new DCM architecture. This page describes the following topic:

• How to install RabbitMQ
• How to configure RabbitMQ using the default configuration
• How to override the default configuration

Queuing supports asynchronous communication between the different components. The overview on the Blueriq DCM architecture overview page shows the different components that communicate with each other using a queue.

RabbitMQ

To use the asynchronous communication with queues, we need software that manages these queues. This software is called a message broker. The message broker is where queues are defined together with the corresponding exchanges.

Blueriq supports RabbitMQ as the message broker. The following page describes how to install RabbitMQ: Installing RabbitMQ

Automatic configuration

After RabbitMQ has been installed, we can configure the queues, exchanges and the bindings between the exchanges and queues. A default configuration has been attached below. This is a JSON file which contains all queues, exchanges and bindings necessary for the DCM setup. It can be imported in the RabbitMQ dashboard in the "Overview" tab, under "Import definitions". 

After importing the file it might be necessary to reconfigure the users, to add a new user so you can remove the guest user. please see: https://www.rabbitmq.com/access-control.html

Manual configuration

For manual configuration and property configuration see Queueing configuration.