Page History
Info |
---|
This component was introduced in Blueriq 14.6. Before Blueriq 14.6, this component was a part of the Trace SQL Store component. |
Table of contents
Table of Contents
Description
This Timeline SQL Store Component contains a Timeline DAO implementation that can be used by the trace engine to store trace 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.
Installation
In order to use this component, the trace-sql-store or the timeline-sql-store profile the
profile must be active. More information on how to configure the application using Spring Profiles can be found here: Component configuration with Spring Profiles. Include Page _ProfileTimeline _ProfileTimeline
Add the artifact with groupId com.blueriq
and artifactId blueriq-component-tracetimeline-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)
Info |
---|
For customers that are upgrading an existing version of Blueriq, database upgrade scripts are provided in the Upgrade instructions when applicable. |
UI Text Box | ||
---|---|---|
| ||
Please make sure the trace-sql-store has a separate datasource. Using the same datasource for other components is known to cause errors. |
Use the following steps to configure the datasource:
...
Using JDBC datasource : this can be configured in the
application-externaldatasources.properties
file. When configuring external datasources, theexternaldatasources
profile should be enabled.Code Block language powershell title application-externaldatasources.properties blueriq.datasource.trace-sql-store.url=jdbc:sqlserver://<database_url>:<port>;databaseName=bq_comments;instance=SQL_EXPRESS blueriq.datasource.trace-sql-store.username=<username> blueriq.datasource.trace-sql-store.password=<password> blueriq.datasource.trace-sql-store.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver blueriq.hibernate.trace-sql-store.hbm2ddl.auto=validate blueriq.hibernate.trace-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect
Using JNDI datasource : this can be configured in the
application-jndidatasources.properties
file When configuring JNDI datasources thejndidatasources
profile should be enabled.Code Block language powershell title application-jndidatasources.properties blueriq.datasource.trace-sql-store.jndiName=java:/comp/env/jdbc/blueriqTrace blueriq.hibernate.trace-sql-store.hbm2ddl.auto=validate blueriq.hibernate.trace-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect
...
The datasource name is timeline-sql-store.
Include Page | ||||
---|---|---|---|---|
|
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
Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Note |
---|
The Timeline SQL Store either stores timeline messages in the database, or consumes timeline events from the queue. When the configuration below is enabled, only timeline events are consumed, no timeline messages are saved to the database directly. So if you enable this configuration, be sure to also enable the Timeline Event Publisher Component, otherwise no timeline information is saved anywhere. |
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.concurrency.max-concurrent-consumers=1 # Enable consumer functionality |
Note |
---|
In certain circumstances it is possible that an error happens while consuming the timeline event. Because of the workings of RabbitMQ, this will result in an endless loop where it tries to re-send the timeline event until it is correctly consumed. To prevent this, a republish mechanism is added with Blueriq 15.7. This mechanism sends timeline events to a dead-letter-queue when an error occurs. This will prevent the creation of the endless loop. For information see Configuring RabbitMQ |
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.
Performance
The performance impact of the Timeline
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:
- none
- validate
Performance
...
SQL Store is minimal when used normally: to write
...
timeline messages to the database
...
and retrieve these messages for one given Case ID.