Page History
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:
...
Queuing supports asynchronous communication between the different components. The overview on the Blueriq DCM architecture overview page shows the different components that communicate to with each other using a queue.
...
| Warning |
|---|
The following steps will overwrite any existing configuration. If you are using an existing RabbitMQ installation please refer to Manual queueing Queueing configuration. |
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 in the file called "definitions. json". This file 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 , to add a new user so you can remove the guest user. please see: https://www.rabbitmq.com/access-control.html
...
For manual configuration and property configuration see Manual queueing Queueing configuration.
Overview
Content Tools