Reporting SQL Store component

Table of contents 

Description 

The Reporting SQL Store component provides the ability to store (parts of) a profile as XML by means of a service call.

The configuration options are found below in this document.

Requirements

This component persists data in a database, that must be configured as a connection. See Platform Support for the supported databases.

Installation

In order to use this component, the reporting-sql-store profile must be active. More information on how to configure the application using Spring Profiles can be found here : External application configuration with Spring Profiles.

Add the artifact with groupId com.blueriq and artifactId blueriq-component-reporting-sql-store as a dependency to your Blueriq runtime POM file.

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)
  
  

See Configuring database connection for information on how to create new connections for the different datasources.Use the following steps to configure the database connection:

1. Using JDBC datasource:

   • If necessary, create a new connection. The connection needs to be configured in the application.properties file.

     application.properties (SQL Server example)

     blueriq.connection.reporting_local_sql.sql.url=jdbc:sqlserver://<database_url>:<port_number>;databaseName=<database_name>;instance=<instance_name>
     blueriq.connection.reporting_local_sql.sql.username=<username>
     blueriq.connection.reporting_local_sql.sql.password=<password>
     blueriq.connection.reporting_local_sql.sql.type=jdbc
     blueriq.connection.reporting_local_sql.sql.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
     blueriq.connection.reporting_local_sql.sql.poolInitialSize=0
     blueriq.connection.reporting_local_sql.sql.poolMaxIdle=8
     blueriq.connection.reporting_local_sql.sql.poolMaxTotal=8
     blueriq.connection.reporting_local_sql.sql.poolMaxWait=-1L
     blueriq.connection.reporting_local_sql.sql.poolMinIdle=0
     blueriq.connection.reporting_local_sql.sql.minEvictableIdleTimeMillis=1800000
     blueriq.connection.reporting_local_sql.sql.numTestsPerEvictionRun=3
     blueriq.connection.reporting_local_sql.sql.testOnBorrow=true
     blueriq.connection.reporting_local_sql.sql.testOnReturn=false
     blueriq.connection.reporting_local_sql.sql.testWhileIdle=false
     blueriq.connection.reporting_local_sql.sql.timeBetweenEvictionRunsMillis=-1
     blueriq.connection.reporting_local_sql.sql.validationQuery="SELECT 1"
     blueriq.connection.reporting_local_sql.sql.validationQueryTimeout=-1
     

   
   

2. Using JNDI datasource:

• • If necessary, create a new connection. The connection needs to be configured in the application.properties file.
  • application.properties

    blueriq.connection.reporting_local_sql.sql.jndi=java:/comp/env/jdbc/reporting
    blueriq.connection.reporting_local_sql.sql.type=jndi
    

    
    

    
    

• In Studio the previously configured connection name needs to be used as the Connection parameter of the AQ_Report service.

  Example configuration: In the previous example the name of the connection is reporting_local_sql .

• Configuring the database connection from the Development Dashboard
  Go to Settings Widget → Connections tab → On the left side menu : select SQL connection. The same properties are available for configuration as from the properties file.  You can perform CRUD operations on connections from here