Timeline SQL Store component [editor]

This component was introduced in Blueriq 14.6. Before Blueriq 14.6, this component was a part of the trace-sql-store component.

For backwards compatibility, the timeline-sql-store is also enabled when you enable the trace-sql-store profile.

If no datasource is configured for the timeline, Blueriq will use the same datasource as for the trace-sql-store. We intend to remove these backwards compatibilities in Blueriq 15.

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 messages in a database.

The configuration options are found below in this document.

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 must be active. More information on how to configure the application using Spring Profiles can be found here: Component configuration with Spring Profiles.

Add the artifact with groupId com.blueriq and artifactId blueriq-component-trace-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)

For customers that are upgrading an existing version of Blueriq, database upgrade scripts are provided in the Upgrade instructions when applicable.

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:

If necessary, create a new datasource. See Configuring JDBC database drivers for information on how to do this.

Timeline SQL Store component is using the timeline-sql-store datasource to store data. The timeline-sql-store datasource can be configured using JDBC or JNDI.

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

application-externaldatasources.properties

blueriq.datasource.timeline-sql-store.url=jdbc:sqlserver://<database_url>:<port>;databaseName=bq_comments;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

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

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

Hibernate settings
These settings are done for each datasource type in the corresponding properties file, as in the examples above.

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

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.

Space shortcuts

Page tree