You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Blueriq uses Spring Boot's Externalised Configuration feature to allow you to externalize configuration which allows to use the same Blueriq code in different environments. Further, all Blueriq application configuration is divided into Spring Profile's to be able to selectively make code available. Each profile makes use of it's own proprtyfile, using the naming convention application-<PROFILENAME>.properties
Currently, the following profiles exist in Blueriq:
| profile name | corresponding property file | |
|---|---|---|
| "dev" | application-dev.properties | |
| "externaldatasources" | application-externaldatasources.properties | |
| "jndidatasources" | application-jndidatasources.properties | |
| "publisherclient" | application-publlsherclient.properties | |
| "capture-http-session" | application-capture-http-session.properties | |
| "single-session" | application-single-session.properties | |
| "web-it" | application-web-it.properties | |
| "widget-override" | application-widget-override.properties | |
| "customer_a" | application-customer_a.properties | |
| "customer_b" | application-customer_b.properties | |
| "html-container" | application-html-container.properties | |
| "vaadin-widget-engine" | application-vaadin-widget-engine.properties | |
bootstrap.properties
Spring provides a couple of ways to externalize application configuration. Blueriq makes use of the possibility to pick up application configuration from the classpath. To tell Spring to pick up configuration from the classpath we need to configure the bootstrap.properties as follows:
spring.cloud.config.server.bootstrap=true
spring.profiles.active=native,dev
spring.cloud.config.server.native.searchLocations=file:${spring.config.location:.}
Overview
Content Tools