Versions Compared

Old Version 2

changes.mady.by.user Alexandra Aldea

Saved on

compared with

New Version 3

changes.mady.by.user Felix Janssen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Runtime. The Runtime receives the tenant via the X-TENANT-ID HTTP header and places it on the Blueriq context (System attributes) which can be used in the model. Additionally, it will listen to a separate RabbitMQ for each tenant, if the dcm-lists-client profile in enabled.
  2. Customerdata client. This component sends the tenant via the X-TENANT-ID HTTP header to the customerdata service.
  3. Customerdata service. This component receives the X-TENANT-ID header and determines which datasource to use.
  4. Process engine.This component uses the Blueriq context to retrieve the tenant and determines which datasource to use.
  5. Scheduler. This component ruses component uses the Blueriq context to retrieve the tenant and uses the tenant when registering jobs in the Quartz database.
  6. Trace engine. This component uses the Blueriq context to retrieve the tenant and determines which datasource to use.
  7. Comments. This component uses the Blueriq context to retrieve the tenant and determines which datasource to use.
  8. DCM Lists Client. This component sends the tenant via the X-TENANT-ID HTTP header to the DCM Lists Service. Additionally, it publishes events to a separate RabbitMQ for each tenant.
  9. DCM Lists Service. This component receives the X-TENANT-ID header and determines which datasource to use. Additionally, it listens to a separate RabbitMQ for each tenant.
  10. DCM Intake (DCM_CaseCreate). This component publishes events to a separate RabbitMQ for each tenant.
  11. DCM Case Engine. This component listens to a separate RabbitMQ for each tenant.

...