Reporting SQL Store component

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.

In order to use this component, make sure to have the BlueriqComponentReportingSqlStore.dll in the /bin directory of your .NET webapp installation.

Use the following steps to configure the database connection:

• If necessary, create a new connection. See Configuring database connection for information on how to do this. The connection needs to be configured in the application.properties file.

  Example configuration:

  application.properties

  blueriq.connection.reporting_local_sql.sql.url=jdbc:jtds: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=net.sourceforge.jtds.jdbc.Driver
  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=""
  blueriq.connection.reporting_local_sql.sql.validationQueryTimeout=-1

• 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.

Use the following steps to configure the database connection:

• Configuring the database connection for the Reporting SQL Store component in .Net is done by adding a connection configuration to the 

  Unable to render {include} The included page could not be found.
   file:

  Example configuration:

  .NET database configuration example

  <hibernate-configuration>
    <session-factories>
        <session-factory name="ReportingDao">
          <properties>
            <property name="connection.provider" value="NHibernate.Connection.DriverConnectionProvider" />
            <property name="dialect" value="NHibernate.Dialect.MsSql2012Dialect" />
            <property name="connection.driver_class" value="NHibernate.Driver.SqlClientDriver" />
            <property name="connection.connection_string" value="Data Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\LocalDB\ReportingDB.mdf;Integrated Security=True" />
            <property name="hbm2ddl.auto" value="update" />
            <property name="current_session_context_class" value="Aquima.WebApplication.WebPersistenceUtility.Session.CurrentHibernateSessionContext, WebPersistenceUtility" />
          </properties>
        </session-factory>
    </session-factories>
  </hibernate-configuration>

• 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 ReportingDao.

Supported dialects:

• NHibernate.Dialect.MsSql2012Dialect
  
  

All necessary DLL files the Reporting SQL Store component depends on can be found in the /bin directory of the .NET webapp ZIP file.