You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
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 Multi-tenancy DCM Lists Service configuration
blueriq-dcm-lists.yml
blueriq:
dcm:
lists:
multi-tenancy:
enabled: true
allowed-tenants:
- google
- apple
mongodb:
tenants:
google:
host: localhost
port: 27017
database: google
apple:
host: localhost
port: 27017
database: apple
rabbitmq:
tenants:
google:
host: localhost
port: 5672
virtualHost: google
username: google
password: welcome
ssl:
enabled: false
queueNames: googleQueue
apple:
host: localhost
port: 5672
virtualHost: apple
username: apple
password: welcome
ssl:
enabled: false
queueNames: appleQueue
Overview
Content Tools