Versions Compared

Key

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

...

The components need the DCM Lists Service. See configuring the DCM Lists Service to install it. Additionally, these components needs a connection with the RabbitMQ message broker.

Installation DCM

...

Lists Client

 In order to use this component, the dcm-lists-client profile must be active. More information on how to configure the application using Spring Profiles can be found here : External application configuration with Spring Profiles.

...

The reactive version of the list (DCM_Tasklist) TaskList depends on eventstreams event streams to communicate with the active browser. Make sure the reverse proxy server (when used) is configured correctly: Using a reverse proxy server.

...

Code Block
languagetext
titleapplication-dcm-lists-publisher.properties
blueriq.dcm.lists-publisher.rabbitmq.host = yourrabbithost.local
blueriq.dcm.lists-publisher.rabbitmq.port = 5672
blueriq.dcm.lists-publisher.rabbitmq.username = yourRabbitUsername
blueriq.dcm.lists-publisher.rabbitmq.password = yourRabbitPassword
blueriq.dcm.lists-publisher.rabbitmq.virtualHost = /
blueriq.dcm.lists-publisher.rabbitmq.exchangeName = processEvents

DCM 2.0

For The split op the DCM Lists Client Component into separate components was done to better accommodate a DCM 2.0 the Process Engine resides in the Case Engine and the lists reside in the Runtime. Please make sure that the DCM List Publisher Component properties and profile are configured in the Case Engine configuration location and the DCM List Client Component properties and profile are configured in the Runtime configuration location setup. The DCM Lists Publisher component should only be enabled for the runtime that takes the role of Case Engine, while the DCM Lists Client component should only enabled for the runtime that provides flows that use DCM_TaskList, DCM_WorkList and/or DCM_CaseList containers.