Introduction

In the new DCM architecture, the Runtime component is responsible for task execution. This could either be automatic, without user interaction or manually by a user using the user interface. It communicates with the Case Engine when a task starts and when a task is completed or canceled. Aside from task execution, the Runtime contains the dashboard overview of multiple cases, the intake to create a case and the case dashboard to view and interact with a single case. It's also possible to trigger communication to the Case Engine through the UI, like triggering a message event or starting a task using the DCM Lists Service containers.

In the previous versions of DCM, the Runtime also contained the Process Engine. This is not the case anymore, the Process Engine is now part of the Case Engine. The Runtime communicates with the Case Engine through asynchronous messages and a REST API.

In a minimal DCM setup, the following components are required:

• Case Engine client component
• Customerdata client component

Optionally, the following components can be enabled:

• Development-tools component (development only)
• Document Renderer client component
• External flow component
• Timeline Publisher/Timeline SQL Store components
• Trace Publisher/Trace SQL Store components
• Comments SQL Store component
• DCM Lists Service client component
• Dashboard component

This page explains how the Runtime is installed and configured for DCM.

Runtime installation

The Runtime can be downloaded using the artifactory or installed using the installer.

If the installer is used, the Runtime will install and run automatically.

In case of using the Runtime as a standalone application it could started directly in Java using the command line:

$ java -Dserver.port=18080 -Dspring.config.additional-location=file:///config/DCM2/Runtime/config -jar blueriq-runtime-{{version}}.jar

If it is needed to serve the Runtime in an application server, the Installing Runtime page explains how to do that.

Runtime Configuration