Description

The There are two DCM Lists Publisher Component provides the ability to publish task and case events to the DCM Lists Service (via a message queue)components: the DCM Lists Client and the DCM Lists Publisher, which is part of the case engine. The DCM List Client Component component provides the ability to query the DCM Lists Service for Case, Task List Rows and Work List Rowsand Work lists. The DCM Lists Publisher is a module in the case engine which publishes case state events to the DCM Lists Service (via a message queue). A schematic overview can be found below.

Image RemovedImage Added

Requirements

The components need the DCM Lists Service. See configuring the DCM Lists Service to install it. Additionally, these components the publisher module 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.

Add the artifact with groupId com.blueriq and artifactId blueriq-component-dcm-lists-client as a dependency to your Blueriq runtime POM file if you want to depend on it.

Configuration

Define the location of the DCM Lists Service

You should configure the location of the DCM Lists Service

blueriq.dcm.lists-client.url = http://yourhost:yourport/
blueriq.dcm.lists-client.username = yourusername
blueriq.dcm.lists-client.password = yourpassword

Using a reverse proxy server

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

Installation DCM List Publisher

DCM List Publisher (part of the case engine)

The DCM Lists Publisher is part of the case engine. It is enabled when the

Configuration

RabbitMQ connection

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

...

architecture

The split op the DCM Lists Client Component into separate components was done to better accommodate a DCM 2.0 setup. components are part of the Getting started with Case Modelling. The DCM Lists Publisher Client 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, uses DCM_WorkList and/or DCM_CaseList containers.

...