SAP Basis Monitoring for Background or Batch Jobs

• The monitoring architecture of SAP is used to monitor selected jobs and to display problems as alerts.

• SAP also makes provision for central job monitoring based on the End-to-End Monitoring and Alerting Infrastructure (MAI)

  for monitoring jobs like BW process chains, ABAP jobs, SAP Data Services (DS) jobs etc.

• Resource-intensive jobs are better run when there is sufficient system resource or on an Aditional Application Server so as not to impact overall system performance.

• The pain point is the difficulty in monitoring thousands of recurring jobs during the day across a complex, heterogeneous system landscape and the available tools for this purpose are at best useful only for identifying exceptions and performing a few useful tasks in the system.

• The challenges in Batch Monitoring include:

  • Health: health monitoring of batch processing environment; Utilization vs Capacity.

  • Alerts: Alerting based on status, runtime, duration, delay and error logs.

  • Performance: Job performance and details of individual jobs.

  • Workload Management: changes in job performance in relation to current capacity; Trend analysis.

• Manual Job Monitoring using SM37

• Job performance analysis can be done after the fact using ST03 workload statistics

• Long running jobs can be view live by logging on to each system and checking SM50 (work processes) and/or SM66 (global work processes)

• Netweaver CCMS using RZ20 background job alerts in conjunction with: SE16 using table ALBTCMON

• Solution Manager: Job and BI Monitoring -

  • Job Management: Scheduling & Monitoring

  • Solman 7.2 introduced Unified Job Monitoring

  • lengthy setup and over-aggregated metrics, multiple UI 'Apps' to manage, monitor, report

  • See IT-Conductor prior blogs on Solution Manager including eBook downloads for setup, migration and features comparison

IT-Conductor as the cloud-based agentless monitoring solution is designed to provide active monitoring of all scheduled jobs, their status, performance, and correlation to other activities in the system:

• Job Scheduling: single or multi-step SAP jobs and native jobs can be scheduled centrally for all managed SAP systems.

• Process Automation: orchestrate a set of activities on one or more applications, databases or systems.

• Failed Job Alert: the most basic requirement is to monitor and alert when job failure occurs.

• Delayed Job Alert: alert on jobs with an undue delay time to run

• Job In-flight Time: in-flight tracker providing valuable job runtime as well as a historic footprint of long-running jobs.

• Jobs with abnormal finish time: alerts are generated for jobs with unexpected response time.

• Targeted Notification: alerts are sent to the person responsible to gain timely response to failed jobs by using subscribers and selective criteria.

• Workload Monitoring: monitoring of overall workload and intelligence gathering to properly diagnose and manage shared resources. Drill down on the job and get more details on internal stats such as DB time, CPU time, memory usage, IO metric, etc.

• Related Events: provision of both events and service management to help correlate information.

• Dashboard: events, charts, KPIs and analytics focusing on IT processes. Zoom in to clickable charts time synchronized with customizable KPIs.

• The general performance and state of your systems can be significantly improved through the use of IT-Conductor cloud-based monitoring solution.  See more on the topic of IT-Conductor SAP Job Monitoring