This post originated from an RSS feed registered with Java Buzz by Michael Cote. Original Post: Business Activity Monitoring (BAM): Feed Title: Cote's Weblog: Coding, Austin, etc. Feed URL: https://cote.io/feed/ Feed Description: Using Java to get to the ideal state. Latest Java Buzz Posts Latest Java Buzz Posts by Michael Cote Latest Posts From Cote's Weblog: Coding, Austin, etc.

Here’s how BAM works: In EAI, applications talk to one another through a message bus, called a publish-and-subscribe model. BAM acts as a wild card to a lot of different events coming across that bus. The message bus duplicates the event and sends it to the monitor. “Sort of like a sniffer,” Gassman tells me.

. . .

BAM for IT people provides business service views by correlating the infrastructure with the delivery of a business process. For example, it’s no longer enough to know after the fact that the credit card validation process took 10 seconds; rather, the system needs to monitor the operational time itself, not just downtime. BAM can make this happen: If IT service guarantees say transactions will be complete in 5 seconds, BAM notes when the time goes beyond 5 seconds and triggers a warning. Perhaps the warning also executes a command to another system, giving the process a boost to get the validation completed before the buyer disconnects.