The plugin blueriq-plugin-dossier-sql-store
used to be a part of the Blueriq Runtime but since the release of Blueriq 11, the support of this plugin is discontinued.
Blueriq released the sources of this plugin with the intention of enabling customers to migrate to Aggregates at their own pace but without support from Blueriq. No rights reserved.
To compile and build war use:
mvn clean verify -DskipTests
To test the war, please add the Blueriq license.aql
to src\test\resources
and use:
mvn clean verify
Deploy Runtime.war
to Tomcat container. Create a configuration folder and add Blueriq license.aql
or package Blueriq license.aql
by adding it to src\main\resources
.
Start Tomcat container with the following parameters:
-Dspring.config.additional-location=file://path_to_conf/ # URI of the configuration folder which contains the Blueriq license.
-Dspring.profiles.active=native,development-tools (embedded H2 database) or
-Dspring.profiles.active=native,development-tools,externaldatasources (direct connection) or
-Dspring.profiles.active=native,development-tools,jndidatasources (JNDI)
Configure the datasource for the Dossier plugin via either the externaldatasources profile or the jndidatasources profile.
application-externaldatasources.properties
blueriq.datasource.dossier.url=jdbc:sqlserver://<database_url>:<port>;databaseName=<databaseName>;instance=SQL_EXPRESS
blueriq.datasource.dossier.username=<username>
blueriq.datasource.dossier.password=<password>
blueriq.datasource.dossier.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
blueriq.hibernate.dossier.hbm2ddl.auto=validate
blueriq.hibernate.dossier.dialect=org.hibernate.dialect.SQLServer2012Dialect
application-jndidatasources.properties
blueriq.datasource.dossier.jndiName=java:/comp/env/jdbc/main
blueriq.hibernate.dossier.hbm2ddl.auto=validate
blueriq.hibernate.dossier.dialect=org.hibernate.dialect.SQLServer2012Dialect
- 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)
- none
- validate
Database scripts can be found in dbscripts
.