You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

Description

The Trace Event Publisher component is introduced to publish all trace events on a queue for other software to be able to consume those messages in some way. Trace events messages can typically be used for process mining.

Requirements

The trace event publisher component needs to be able to access a queue. Currently only RabbitMQ is supported. For setting this up see Configuration of RabbitMQ for Customerdata service and Trace Event Publisher.

Installation

In order to use this component, the trace-event-publisher-amqp profile must be active. More information on how to configure the application using Spring Profiles can be found here: Component configuration with Spring Profiles.

The trace-event-publisher-amqp profile activates trace events being published to the configured RabbitMQ channel. If, besides that, you want trace events to be also stored in a database you need to activate the trace-sql-store profile and externaldatasources profile as well. Please consult the relevant documentation on how to configure the trace-sql-store component and the externaldatasources.

Configuration

To be able to publish event messages, the event channel needs to be configured in application-trace-event-publisher-amqp.properties This file can be found, or otherwise should be placed in <Blueriq installation folder>\Runtime\conf.
application-trace-event-publisher-amqp.properties

The queue configuration can be configured using a default queue (using blueriq.default.rabbitmq.* in the application.properties). When it is needed, it can be overruled using the configuration below.

Also the trace events exchange has a default, and can be overruled by configuration when needed.

# RabbitMQ configuration
blueriq.trace.event.publisher.channel.amqp.rabbitmq.host=localhost
blueriq.trace.event.publisher.channel.amqp.rabbitmq.port=5672
blueriq.trace.event.publisher.channel.amqp.rabbitmq.virtualHost=/
blueriq.trace.event.publisher.channel.amqp.rabbitmq.username=guest
blueriq.trace.event.publisher.channel.amqp.rabbitmq.password=guest
blueriq.trace.event.publisher.channel.amqp.rabbitmq.ssl.enabled=true

 
# Trace events channel configuration
blueriq.trace.event.publisher.channel.amqp.rabbitmq.exchangeName=tracingEvents

Enable TLS connection

To enable a secure (TLS) AMQP connection to the queue, set the property "blueriq.trace.event.publisher.channel.amqp.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.


Didn't find the answer you were looking for? Try the advanced search!