SAP Job Monitoring and Management

 

Causes, Impacts

  • 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.

 

How is it monitored?

  • 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

 

 

For the main topic;
SAP BASIS and Monitoring