Shortly after posting my ITIL and monitoring scenario about BMC Performance Manager notifying CONTROL-M that an SAP job was failing, I got a great response about how CONTROL-M even takes it a step further towards ITIL ideals with the Batch Impact Manager module.
Just read your blog. I wanted to update you on a couple of items which help to fill out the drive to ITIL standards achievement in the operations and monitoring environments.
BMC CONTROL-M has an additional module called BMC Batch Impact Manager. This module allows a user to reduce a large flow of jobs to a single service instance and monitor those services critical to the business. Is there any other kind? When a service is predicted by Batch Impact Manager to fail its due out time, Batch Impact Manager issues alerts to operations and provides an interface to Service Impact Manager to focus attention on bringing the service back to normal. Therefore if an SAP process was included in that critical service, as soon as the non-availability of the SAP process impacted the service, CONTROL-M and or Batch Impact Manager would start to squeal.
Great stuff! I’ve just added some links and spelled out the acronyms, otherwise unretouched. The embarrassing thing is, I knew about this module but hadn’t made the connection. Thanks Ronnie for bringing it to my attention!