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 | _ProfileTimeline | _ProfileTimeline | profile is also enabled when you enable the||||
Include Page | _ProfileTrace | _ProfileTrace | profile.
Table of contents
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.
Blueriq 14.8 introduces 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.
...
In order to use this component, the trace-sql-store orthe 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
...
- 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
the
file. When configuring external datasources, theInclude Page _PropertiesExternalDatasources _PropertiesExternalDatasources Include Page _ProfileExternalDatasources _ProfileExternalDatasources 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
Using JNDI datasource: this can be configured in the
application-jndidatasources.properties
file
file. When configuring JNDI datasources theInclude Page _PropertiesJndiDatasources _PropertiesJndiDatasources
profile should be enabled.Include Page _ProfileJndiDatasources _ProfileJndiDatasources 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
- Hibernate settings
These settings are done for apply to each datasource type in the corresponding properties file, as in the examples above.
...
Supported hbm2ddl.auto values:
- none
- validate
Consume timeline events
...
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. |
# RabbitMQ configuration |
blueriq.timeline.event.listener.amqp.rabbitmq.host=localhost # Enable consumer functionality blueriq.timeline.event.listener.amqp.enabled=true |
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.
...