You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
Case-Modelling has been in beta stage in the Blueriq 15 major. At the latest minor, all Blueriq 16.0 changes have been merged back to Blueriq 15.13. From this point on Case-Modelling is out of beta and can be used.
Please make sure to upgrade to at least Blueriq 15.13 when using Case-Modelling, possibly in a production environment. Earlier minor versions are not supported.
The DCM Lists service supports multi-tenant data sources and message sources. Enabling multi-tenancy means that calling the service will require sending an additional HTTP header X-TENANT-ID with the tenant name. In the configuration of the DCM Lists Service, you can configure which tenants are allowed to access the service and configure a specific data source and message source for each allowed tenant. When the DCM Lists Service is not able to retrieve the tenant name or the given tenant name is not allowed to access a HTTP Status 400 (Bad request) is returned and the details are printed in the log.
Note
This feature is intended to work with a Blueriq Runtime that has Multi-tenancy enabled. See Multi-tenant setup and Runtime multi-tenancy for more information.
Example tenant configuration
blueriq-dcm-lists.yml
blueriq:
dcm:
lists:
multi-tenancy:
enabled: true
allowed-tenants:
- A
- B
tenants:
A:
mongodb:
host: localhost
port: 27017
database: A
rabbitmq:
host: localhost
port: 5672
virtualHost: A
username: A
password: A
ssl:
enabled: false
queueNames: A
B:
mongodb:
host: localhost
port: 27017
database: B
rabbitmq:
host: localhost
port: 5672
virtualHost: B
username: B
password: B
ssl:
enabled: false
queueNames: B
Overview
Content Tools