Page History
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.
...
Optionally, the following components can be enabled and are used in the DCM Foundation:
- Development-tools component (development only)
- Document Renderer client component
- External flow component
- Timeline Event Publisher component
- /Timeline SQL Store componentsTrace Publisher/Trace SQL Store componentscomponent
- Comments SQL Store component
- Dashboard component
This page explains how the Runtime is installed and configured for DCMIn this setup, the Runtime should not have a dependency on the Process SQL Store component as this component is used in the Case Engine only.
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:
...
| language | powershell |
|---|
...
.
...
If it is needed If you want to serve the Runtime in an application server, the Installing Runtime page explains how to do that.
Runtime configuration
...
The Runtime should be configured with the profiles enabled corresponding to the components mentioned in the introduction.
For a guide how to enable, please visit: External application configuration with Spring Profiles - Blueriq Latest - Blueriq Community
For the configuration of the different components please visit their configuration pages:
Overview
Content Tools