You are viewing the documentation for Blueriq 16. 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 . You can only enable one type by providing the type in the property spring.profiles.active. externaldatasources
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.
| Subject | Property | Default | Explanation | Property file spring.profiles.active= | Property file spring.profiles.active=
|
|---|---|---|---|---|---|
| Datasources | blueriq.datasource.[name].url | The url of the datasource which should be connected to. |
| Only available when you have | |
| blueriq.datasource.[name].username | The username to login to the datasource |
| Only available when you have | ||
| blueriq.datasource.[name].password | The password to login to the datasource |
| Only available when you have | ||
| blueriq.datasource.[name].driverClassName | The driver that needs to be used to connect to the datasource |
| Only available when you have | ||
| blueriq.datasource.[name].jndiName | The name of the jndi datasource connection. | Only available when you have |
| ||
| blueriq.hibernate.[name].hbm2ddl.auto | validate | When starting server (SessionFactory) Supported values: create/update/create-drop are not supported ways to create a schema. Use the dbscripts that are provided with the release instead. |
|
| |
| blueriq.hibernate.[name].dialect | The dialect that hibernate should use. |
|
| ||
blueriq.hibernate.[name].use_nationalized_character_data | true | Enable 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. |
|
| |
blueriq.hibernate.[name].globally_quoted_identifiers | false | Quotes all database identifiers.  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). |
| ||
blueriq.hibernate.[name].globally_quoted_identifiers_skip_column_definitions | false | When blueriq.hibernate.[name].globally_quoted_identifiers is set to true, column names will be skipped. Like the previous property, Blueriq requires this property to be false (which is the default). |
| ||
| blueriq.datasource.h2.enabled | false | This property is required to be set to 'true' when any data source configures a H2 database. | Can be placed in any file. |
Overview
Content Tools