Page History
...
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)
| 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:
...
The
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
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 |
...
| language | powershell |
|---|---|
| title | application-jndidatasources.properties |
...
datasource name is trace-sql-store.
...
| Include Page | ||
|---|---|---|
|
...
|
...
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:
...
Consume trace events
The Trace SQL Store component can store trace messages directly in the database, but it is also possible to decouple the storage of trace messages using the Trace Event Publisher Component to publish trace events to a queue and then consume them using this component.
...
| Note |
|---|
The Trace SQL Store either stores trace messages in the database, or consumes trace events from the queue. When the configuration below is enabled, only trace events are consumed, no trace messages are saved to the database directly. So if you enable this configuration, be sure to also enable the Trace Event Publisher Component, otherwise no trace 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 trace events exchange has a default, and can be overruled by configuration when needed.
| Code Block |
|---|
# RabbitMQ configuration blueriq.trace.event.listener.amqp.rabbitmq.host=localhost blueriq.trace.event.listener.amqp.rabbitmq.port=5672 blueriq.trace.event.listener.amqp.rabbitmq.virtualHost=/ blueriq.trace.event.listener.amqp.rabbitmq.username=guest blueriq.trace.event.listener.amqp.rabbitmq.password=guest blueriq.trace.event.listener.amqp.rabbitmq.queueNames=tracedcmTraceEvents blueriq.trace.event.listener.amqp.concurrency.max-concurrent-consumers=1 blueriq.trace.event.listener.amqp.concurrency.concurrent-consumers=1 # Enable consumer functionality blueriq.trace.event.listener.amqp.enabled=true |
...
Overview
Content Tools