You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This feature is part of the ongoing effort to support more DCM features natively in the Blueriq Runtime (working title "DCM 2.0").

Introduction

For DCM 2.0, Blueriq uses asynchronous messaging. Message handling could sometimes fail for different reasons. The DCM Maintenance Application gives the functional administrator the insight and control needed to maintain a DCM system of applications and ways to restore from errors.

The DCM maintenance application:

  • Retries a message for which the handling failed automatically
  • Gives insight and control over messages that failed more than a configured number of retries
  • Gives insight and control over crashed (stale) locks
  • Gives insight into overdue scheduler tasks
  • Gives insight into the state of a case

The DCM Maintenance Application consists of a Spring Boot service that performs the work and comes with an Angular based user interface.


Search cases and error situations

Failed events

Delayed events

Case locks

Cases

Case details

Maintenance actions

Retry message

Retry all messages

Unlock case

Reopen Task

  • No labels