You are viewing the documentation for Blueriq 13. 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#Configuration
| 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) create/update/create-drop/validate |
|
| |
| 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. |
|
|
Overview
Content Tools