Page History

Table of contents 

...

This Timeline SQL Store Component contains a Timeline DAO implementation that can be used by the trace engine to store timeline messages in a database.

The configuration options are found below in this documentBlueriq 14.8 introduced the possibility to consume timeline events that are pushed on a queue by the Timeline Event Publisher Component and then store them in a database in an asynchronous way. See consume timeline events.

Requirements

This component persists data in a database, that must be provided. See platform support for the supported databases.

...

In order to use this component, the trace-sql-store orthe timeline-sql-store profile the

Add the artifact with groupId com.blueriq and artifactId blueriq-component-timeline-sql-store as a dependency to your Blueriq runtime POM file if you want to depend on it.

Configuration

Database

Scripts to create the required database content are provided for the following databases:

• SQL Server
• Oracle
• H2 (we do not recommend using a H2 database in production environments)

Use the following steps to configure the datasource:

...

1. Using JDBC datasource: this can be configured in the  application-externaldatasources.properties file. When configuring external datasources, the externaldatasources profile should be enabled.

   Code Block
   language powershell title Example application-externaldatasources.properties
   blueriq.datasource.timeline-sql-store.url=jdbc:sqlserver://<database_url>:<port>;databaseName=bq_timeline;instance=SQL_EXPRESS blueriq.datasource.timeline-sql-store.username=<username> blueriq.datasource.timeline-sql-store.password=<password> blueriq.datasource.timeline-sql-store.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver blueriq.hibernate.timeline-sql-store.hbm2ddl.auto=validate blueriq.hibernate.timeline-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect

2. Using JNDI datasource: this can be configured in the  application-jndidatasources.properties file When configuring JNDI datasources the jndidatasources profile should be enabled.

   Code Block
   language powershell title Example application-jndidatasources.properties
   blueriq.datasource.timeline-sql-store.jndiName=java:/comp/env/jdbc/blueriqTimeline blueriq.hibernate.timeline-sql-store.hbm2ddl.auto=validate blueriq.hibernate.timeline-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect

...

The datasource name is timeline-sql-store.

Include Page
_DatasourceConfiguration _DatasourceConfiguration

Consume timeline events

The Timeline SQL Store component can store timeline messages directly in the database, but it is also possible to decouple the storage of timeline messages using the Timeline Event Publisher Component to publish timeline events to a queue and then consume them using this component.

To be able to consume event messages, the event channel needs to be configured in the

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 timeline events queue has a default, and can be overruled by configuration when needed.

# RabbitMQ configuration

blueriq.timeline.event.listener.amqp.rabbitmq.host=localhost
blueriq.timeline.event.listener.amqp.rabbitmq.port=5672
blueriq.timeline.event.listener.amqp.rabbitmq.virtualHost=/
blueriq.timeline.event.listener.amqp.rabbitmq.username=guest
blueriq.timeline.event.listener.amqp.rabbitmq.password=guest
blueriq.timeline.event.listener.amqp.rabbitmq.queueNames=TimelineEvents

blueriq.timeline.event.listener.amqp.concurrency.max-concurrent-consumers=1
blueriq.timeline.event.listener.amqp.concurrency.concurrent-consumers=1

# Enable consumer functionality
blueriq.timeline.event.listener.amqp.enabled=true

For more information on concurrent consumers see Configuring RabbitMQ.

Enable TLS connection

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

Supported dialects:

• org.hibernate.dialect.SQLServer2012Dialect (for SQL Server)
• org.hibernate.dialect.Oracle12cDialect (for Oracle)
• org.hibernate.dialect.H2Dialect (for H2) (we do not recommend using a H2 database in production environments)

Supported hbm2ddl.auto values:

...

Performance

The performance impact of the Timeline SQL Store is minimal when used normally: to write timeline messages to the database and retrieve these messages for one given Case ID.