Job Scheduling & Monitoring

During the night, batch jobs ran and shoveled data back and forth between silos. The announced disaster always occurred when a job was unscheduled or hung in a deadlock.

The IT manager tried to prevent such crashes with the "right" scheduling and monitoring. The "real-time computing" advertised by SAP on the basis of the Hana database platform does not officially know any batch jobs and therefore also no job scheduling and monitoring - because everything has to be done in real time!

But the fact is that even in a Hana and cloud computing era, data needs to be moved and messages exchanged between programs. Even the use of SAP Data Hub, to avoid too much data movement, requires planning and monitoring.

SAP's existing customers know it very well: Whether system copy, transport request or release upgrade - trust is good, control is better. SAP itself has neglected the "Job Scheduling and Monitoring" function in recent years, although the function is now particularly needed by existing customers in a hybrid and multi-cloud environment.

Actually, a hybrid IT architecture with on-premises data centers and multi-cloud is inconceivable without scheduling and monitoring. The SolMan does not manage this - wait and see who of the SAP partners can offer a good hybrid cloud monitoring solution.