...
- JobScheduler: carries out a two step process around the interface:
- Detecting errors and other events: A Job running at regular intervals - typically every 2 minutes - analyses the History Log information recorded by the JobScheduler in the database and notes a predefined set of information about . This job is configured not only to filter but also to analyze the log information for the Job Scheduler objects being monitored. The information noted is typically whether tasks have been successfully completed and or whether errors or warnings have been logged. This job then writes this information in a separate Notifications database table.
- Sending alerts: A second Job is responsible for sending the alerts to the relevant System Monitor. This job is also run at regular intervals, analyzing the Notifications database tables. It then carries out a predefined action for each item it finds in the table. Typical actions would be informing a particular monitor that a particular type of event has occurred, such as the successful completion of an order or , a job ending in error or whether error recovery is being attempted.
- JobScheduler: The solution architecture allows analysis of the Log History of more than one JobScheduler using the database specified. It may also be configured to monitor more that one database.
- System Monitors: the JobScheduler is able to connect to more than one System Monitor at the same time.
...