You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
System requirements
Minimal
2 CPU cores
256 MB Heap
Recommended
2 CPU cores
512 MB Heap
Third party tools
RabbitMQ
The DCM Lists Service receives events from the Blueriq Runtime application via the RabbitMQ Messaging system (see DCM queueing RabbitMQ). The DCM Lists Service should be able to connect to the RabbitMQ instance.
MongoDB
The DCM Lists Service stores its data in MongoDB (see Document database MongoDB). The DCM Lists Service should be able to read and write data into a MongoDB instance.
Ideally, both tools run on their own dedicated server, with sufficient resources. We refer to the websites of MongoDB and RabbitMQ for advice on hardware requirements for these components.
Configuration
Note
For Blueriq 12.5 to 12.7.1, the RabbitMQ properties were directly under the spring.data
key.
The DCM Lists Service requires a blueriq-dcm-lists.yml
file in the spring.config.additional-location
you configured for it. Here, you can specify the location of RabbitMQ, MongoDB and configure some additional settings:
spring: data: mongodb: host: mongodb.yourdomain.local port: 27017 database: DcmListsService username: youruser password: yourpass security: # Security configuration for the dcm list service. Here you can override the default username/password user: name: <username> password: '{noop}<password>' blueriq: dcm: lists: event: consumer: rabbitmq: host: rabbitmq.yourdomain.local port: 5672 virtualHost: / username: youruser password: yourpass ssl: enabled: false queueNames: yourQueueName