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

« Previous Version 2 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

The Maintenance user can perform different actions to restore cases when some error has occurred.

Retry message

Messages that failed to be processed can be republished to the original exchange. The Retry message endpoint can be triggered by the button, either in the overview screen, of in the details screen. When the message has been republished successfully, a confirmation will be visible in the UI.

Retry all messages

Unlock case

Reopen Task

  • No labels

Didn't find the answer you were looking for? Try the advanced search!