Job RecordEventualities

Purpose

The recordEventualities job executes all EventualitiesDetector beans registered in the Spring context and keeps the system eventualities detected by them up to date in the database. In the descriptor that ships with the product, the job is currently not active and not configurable.

Process per detector

1. The detector determines the currently existing eventualities of its type.
2. The eventualities already stored for this type and the current date are loaded.
3. Newly detected eventualities are stored. Their validity begins with the current date.
4. Stored eventualities whose serialized metadata no longer appear among the currently detected eventualities are historized.

Comparison and error behavior

The identity of an eventuality is compared via the serialized raw data of its metadata. The respective detectors must therefore deliver stable and appropriate metadata.

An error in one detector is logged. The remaining detectors are executed anyway. If a detector delivers no current eventualities, no new entries are created; eventualities of this type that are already stored can be historized in this run.

The general job parameters such as trigger and mail notification apply as described in the central job management.