Page History

Table of contents 

...

This component persists data in a database, that must be provided. See platform support for the supported databases.

Installation

...

...

 In order to use this component, the process-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-process-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)

...

Use the following steps to configure the datasource:

...

The name of the datasource is process-sql-store

...

.

...

1. Using JDBC datasource : this can be configured in the  application-externaldatasources.properties file. When configuring external datasources, the externaldatasources profile should be enabled.

   Code Block
   language powershell title application-externaldatasources.properties
   blueriq.datasource.process-sql-store.url=jdbc:sqlserver://<database_url>:<port>;databaseName=bq_comments;instance=SQL_EXPRESS blueriq.datasource.process-sql-store.username=<username> blueriq.datasource.process-sql-store.password=<password> blueriq.datasource.process-sql-store.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver blueriq.hibernate.process-sql-store.hbm2ddl.auto=validate blueriq.hibernate.process-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect

2. Using JNDI datasource : this can be configured in the  application-jndidatasources.properties file When configuring JNDI datasources the jndidatasources profile should be enabled.

   Code Block
   language powershell title application-jndidatasources.properties
   blueriq.datasource.process-sql-store.jndiName=java:/comp/env/jdbc/main blueriq.hibernate.process-sql-store.hbm2ddl.auto=validate blueriq.hibernate.process-sql-store.dialect=org.hibernate.dialect.SQLServer2012Dialect

...

Supported dialects:

• org.hibernate.dialect.SQLServer2012Dialect (for SQL Server)
• org.hibernate.dialect.Oracle10gDialect (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

...

...

<hibernate-configuration>
  <session-factories>
    <session-factory name="ProcessCaseDao">
      <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="Server=HOST\SQLEXPRESS;Database=test;User Id=USERNAME;Password=PASSWORD;" />
        <property name="show_sql" value="false" />
        <property name="current_session_context_class" value="Aquima.WebApplication.WebPersistenceUtility.Session.CurrentHibernateSessionContext, WebPersistenceUtility" />
      </properties>
    </session-factory>
  </session-factories>
</hibernate-configuration>

Supported dialects:

• NHibernate.Dialect.MsSql2012Dialect

For more information about configuring database connections, see Configuring database connections in .NET webapp.

Case insensitive searching

SQL Server is case insensitive by default. This makes it possible to search Case Data in a case insensitive way in this database. By default Oracle and PostgreSQL are case sensitive, wich means searching in Case Data is also case sensitive in these databases.

We created the possibility to enable case insensitive searching on case sensitive databases. For more information on how to enable it see: How to enable case insensitive search on case data for Oracle & PostgreSQL

...

.