You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
This will explain how the Customerdata service can be configured to publish aggregate event messages to a queue. Please see Introduction to Aggregate events for more information.
Only RabbitMQ is supported as queue.
Spring profile configuration
To enable message publishing, add the profile 'entity-event-publisher-amqp
' to CDS's bootstrap.yml in <Blueriq installation folder>\Services\blueriq-customerdata\conf
. Create bootstrap.yml if it does not exist.
spring: profiles: active: entity-event-publisher-amqp
Event publisher configuration
To be able to publish event messages, the event channel needs to be configured in blueriq-customerdata-odata-service-v1-entity-event-publisher-amqp.yml
. This file can be found at <Blueriq installation folder>\Services\blueriq-customerdata\conf
.
# Aggregate event channel rabbit configuration blueriq: customerdata: aggregate-event: channel: amqp: rabbitmq: host: localhost port: 5672 virtualHost: / username: guest password: guest ssl: enabled: false exchangeName: customerDataService
Enable TLS connection
To enable a secure (TLS) AMQP connection to the queue, set the property "spring.rabbitmq.ssl.enabled
" to "true
".
The default for AQMP port with TLS on RabbitMQ is '5671', it needs to be explicitly enabled though, see https://www.rabbitmq.com/ssl.html for more information.
Administration endpoints
Customerdata service administrative endpoints