JobScheduler Monitoring Interface should process the Master messages configured with JOC Cockpit

Current Situation

• The functionality to manage System Monitor configuration file is directly available from JOC Cockpit that forward the configuration to the respective JobScheduler Master.
  • configuration file location after deployment:
    • {$scheduler_data}/config/live/sos/.configuration/notification/notification.xml
• The JobScheduler Monitoring Interface supports handling the JobScheduler Master messages:
  • <MasterMessage/>, <TaskWarning/>
  • <TaskIfLongerThan/>, <TaskIfShorterThan/>
  • In this case the JobScheduler Monitoring Interface search for a configuration file only in the {$scheduler_data}/config/notification location and not use a configuration (if available) created with JOC Cockpit.

Desired Behaviour

• In case of processing the Master messages the Monitoring interface should:
  • use the configuration file created with JOC Cockpit
  • if this configuration not exists - check for the configuration files in the {$scheduler_data}/config/notification folder

Applicable JobScheduler Releases

A patch is available for download with JobScheduler releases:

• JobScheduler 1.13.1
  • Download the patch patch-20191118-JITL-579-1.13.1.zip
  • Extract the patch-20191118-JITL-579-1.13.1.zip to any location
  • Copy patch-20191118-JITL-579-1.13.1.jar to
    • {$scheduler_home}/lib/patches
  • Perform a restart