You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.

For the Blueriq Runtime there are two types of datasources that you can define in your properties: jndidatasources or externaldatasources. You can only enable one type by providing the type in the property spring.profiles.active.

Datasource configuration for the Customerdata Service can be found here: Customerdata service

SubjectPropertyDefaultExplanation

Property file

spring.profiles.active= externaldatasources

Property file

spring.profiles.active=

jndidatasources

Datasources







blueriq.datasource.[name].url
The url of the datasource which should be connected to.

application-externaldatasources.properties

Only available when you have  externaldatasources enables instead of jndidatasources.

blueriq.datasource.[name].username
The username to login to the datasource

application-externaldatasources.properties

Only available when you have  externaldatasources enables instead of jndidatasources.

blueriq.datasource.[name].password
The password to login to the datasource

application-externaldatasources.properties

Only available when you have  externaldatasources enables instead of jndidatasources.

blueriq.datasource.[name].driverClassName
The driver that needs to be used to connect to the datasource

application-externaldatasources.properties

Only available when you have  externaldatasources enables instead of jndidatasources.

blueriq.datasource.[name].jndiName
The name of the jndi datasource connection.

Only available when you have jndidatasourcesinstead of externaldatasources.

application-jndidatasources.properties

blueriq.hibernate.[name].hbm2ddl.autovalidate

When starting server (SessionFactory)

Supported values: none / validate 

create/update/create-drop are not supported ways to create a schema. Use the dbscripts that are provided  with the release instead.

application-externaldatasources.properties

application-jndidatasources.properties

blueriq.hibernate.[name].dialect
The dialect that hibernate should use.

application-externaldatasources.properties

application-jndidatasources.properties

blueriq.hibernate.[name].use_nationalized_character_data

trueEnable nationalized character support on all string / clob based attributes ( string, char, clob, text etc ). Note that this property by defaults to true because 'hibernate.use_nationalized_character_data' is set in application.properties that is packaged in the default runtime WAR. When using H2 this property should be set to 'false' because H2 does not have specific nationalized data types. For more information about it's usage see: UTF8 support.

application-externaldatasources.properties

application-jndidatasources.properties

blueriq.hibernate.[name].globally_quoted_identifiers

falseThis property is required to be set to 'true' when a h2 datasource is used

application-externaldatasources.properties


blueriq.datasource.h2.enabledfalseThis property is required to be set to 'true' when any data source configures a H2 database.Can be placed in any file.