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. For backwards compatibility, the 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
Table of Contents
...
In order to use this component, the trace-sql-store orthe 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.
...
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:
- If necessary, create a new datasource. See Configuring JDBC database drivers for information on how to do this.
- Trace Timeline SQL Store component is using the tracetimeline-sql-store datasource to store data. The tracetimeline-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, theexternaldatasources
profile should be enabled.Code Block language powershell title application-externaldatasources.properties blueriq.datasource.tracetimeline-sql-store.url=jdbc:sqlserver://<database_url>:<port>;databaseName=bq_comments;instance=SQL_EXPRESS blueriq.datasource.tracetimeline-sql-store.username=<username> blueriq.datasource.tracetimeline-sql-store.password=<password> blueriq.datasource.tracetimeline-sql-store.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver blueriq.hibernate.tracetimeline-sql-store.hbm2ddl.auto=validate blueriq.hibernate.tracetimeline-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect
Using JNDI datasource: this 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.tracetimeline-sql-store.jndiName=java:/comp/env/jdbc/blueriqTraceblueriqTimeline blueriq.hibernate.tracetimeline-sql-store.hbm2ddl.auto=validate blueriq.hibernate.tracetimeline-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect
- Configuring the datasource from the Development Dashboard
Go to Settings Widget → Datasources tab → On the left side menu : selecttrace-sql-store
datasource. The same properties are available for configuration as from the properties file. Make sure the corresponding profile is enabled (externaldatasources or jndidatasources) - 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 Trace Timeline SQL Store is minimal when used normally: to write trace timeline messages to the database .It is also possible to use the Trace SQL Store to query the trace engine database, like the timeline container does. The Trace SQL Store offers good performance as long as the result set is limited. For large scale analysis, when summaries or aggregates are desired, the Trace SQL Store is not recommended because it is primarily designed to return a list of trace entries. For these scenarios it is recommended to use SQL (or HQL) to query the databaseand retrieve these messages for one given Case ID.