Page History
...
Data | Component | Datasource |
---|---|---|
Comments | Runtime | comments-sql-store |
Reports | Runtime | reports-sql-store |
Timeline | Runtime/ Case Engine | timeline-sql-store |
Trace | Runtime/ Case Engine | trace-sql-store |
Audit | Audit consumer | audit-sql-store |
Failed messages | DCM Maintenance APP | maintenance mongo store |
This data is used from the case context, but might remain relevant even when the case is finished. Therefore this data is kept in the database.
Info |
---|
Some form of maintenance has to be done at these data sources to keep the DCM system running smoothly, since they are never archived automatically. |
...
In the DCM configuration an outbox pattern is used. The following data is being stored in the database when using DCM:
Data | Component | Datasource |
---|---|---|
Process outbox | Case Engine | process-sql-store |
Timeline inbox | Runtime/ Case Engine | timeline-sql-store |
Trace inbox | Runtime/ Case Engine | trace-sql-store |
The outbox mechanism prevents message events to be picked up multiple times, even when they are sent to the queue more than once. Each message is constructed and stored in the outbox. When the message is put to the queue, the message is deleted from the outbox again. So the outbox should remain almost empty when the system is running properly.
...