Page History
Automatic configuration
| Warning |
|---|
The following steps will overwrite any existing configuration. |
After RabbitMQ has been installed, we can configure the queues, exchanges and the bindings between the exchanges and queues. A default configuration is available below (definitions.json). 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".
| Warning |
|---|
The following steps will overwrite any existing configuration. So make sure any other relevant configuration is backed up before trying the automatic configuration step. |
| View file | ||||
|---|---|---|---|---|
|
...
Producing Component(s) | Exchange | Queue | Consuming Component(s) | Dead letter exchange | Dead letter queue |
Case Engine, Runtime | dcmEvents | dcmEventsQueue | Case Engine | dlx.dcmEvents | dcmEventsDlq |
Case Engine | dcmListsEvents | dcmListsServiceEventsQueue | DCM Lists Service |
|
|
Case Engine | dcmMaintenanceEvents | dcmMaintenanceEventsQueue | DCM Maintenance App |
| |
Case Engine | dcmScheduledEvents* | dcmEventsQueue | Case Engine | dlx.dcmScheduledEvents | dcmScheduledEventsDlq |
Case Engine | dcmTasksEvents | dcmTasksEventsQueue | Case Engine, Runtime | dlx.dcmTaskEvents | dcmTasksEventsDlq |
Case Engine, Runtime | timelineEvents | timelineQueue | Case Engine , OR Runtime |
|
|
Case Engine, Runtime | traceEvents | traceQueue | Case Engine , OR Runtime |
|
|
* This exchange publishes to the same queue as the dcmEvents exchange.
...
Add these properties to the application.properties file of the component (i.e. Runtime, Case Engine etc.) to override common RabbitMQ properties for each queue/exchange. The queue and exchange names of the definitions.json file will still be used. Or for .yml (for example the Maintenance App or the DCM Lists Service):
| Code Block | ||||
|---|---|---|---|---|
| ||||
... blueriq default rabbitmq host:localhost port:30010 username:guest password:guest virtualHost:/ ssl: enabled:false |
If desired, it is possible to configure other exchanges/queues in each component individually. To do that, the following properties can be used.
...
Overview
Content Tools