You are viewing the documentation for Blueriq 17. 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

It is possible to set the same property with a hibernate. (global) prefix and a blueriq.datasource.[name].hibernate. (datasource specific) prefix. When the same property is set with both prefixes, the property with the datasource specific prefix will have precedence over the global prefix. 


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].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. For more information about it's usage see: UTF8 support.

application-externaldatasources.properties

application-jndidatasources.properties

blueriq.hibernate.[name].globally_quoted_identifiers

false

Quotes all database identifiers. (warning) Note that some databases treat column names as case sensitive when they are quoted, which may break the application. Blueriq requires this property to be false (which is the default).

application-externaldatasources.properties


blueriq.hibernate.[name].globally_quoted_identifiers_skip_column_definitions

falseWhen blueriq.hibernate.[name].globally_quoted_identifiers is set to true, column names will be skipped. (warning) Like the previous property, Blueriq requires this property to be false (which is the default).

application-externaldatasources.properties