To meet these requirements, we used two different solutions. BizTalk BAM tracking was used to track the receiving and sending of each different type of message in the ESB. The second solution was a custom ASP.NET web site to display the information in a consolidated manner for the business users. I'll explain why we didn't use the out of the box BAM monitoring portal in a subsequent post.
As I've mentioned in some previous posts, the current BizTalk environment I work in performs a lot of content based routing for messaging. When looking at a way to monitor all of the messages, it made sense to leverage BAM tracking. This not only allowed the tracking of all the different individual messages, but it also provided a means of tracking specific information related to each message. Below is a screen shot of the web site that is displayed to the user:
My next post will walk through the "how to" of creating the tracking for an individual message. In my last post, I will look into more specifics of how the ESB monitor is organized and what it provides for the users.