Monitor Background Processes
In many areas of the system, functionality is driven from business object configuration as a BO driven record progresses through its lifecycle. Refer to Business Object Lifecycle for details. As part of that functionality, it is possible that a background process, called a monitor batch process, is used to execute functionality for the record.
Monitor processes are designed to support parallel threads processing. When the number of records to process is unpredictable and
can range from zero or few records to a many, submitting the batch with a fixed number of threads
that fits the higher volumes means waste of threads with each run. Monitor processes are
therefore designed to not create any batch run, and none of the thread level artifacts associated
with a batch run, when there is no data to process. The batch job submission record is completed
as usual but indicates that no batch run was needed.
Note: In an
on-premise installation, monitor batch processes may be submitted via the command line, i.e.
without creating a batch job submission record. In this situation, a monitor batch run will
still be created even if there is no data to process because without a batch job record there is
no way to communicate the reason for not creating a batch run.
The following sections further expand on concepts and features associated with monitor rule processing.