Business Activity Monitoring in BizTalk

Business can take advantage of using BAM on leveraging BizTalk server for integrations.

BizTalk ships with BAM feature,  so can business leverage this feature for tracking the data at important milestones, can know trends in business based on the data that is being tracked.

To implement BAM,  business analyst should identify requirements and have to come with fields and other data need to tracked.

Also BA will play important role in defining the BAM views.

For Creation of BAM Activities and Views, Analyst will use BAM Excel feature.

On successful creation of  activities and its views, developers will leverage activities those are created by analyst for further development.

To Track data, BizTalk dev. will leverage either BAM API or will configure BAM tracking profiles

If dev. Use BAM tracking  profiles for tracking, then no need to write any code, simple tracking profile configuration will be enough.

If you want to track data changes that message undergoes,  you have to leverage BAM API.


BAM API can be implemented using any of the below streams:

MES : Pipeline Event Stream
BES : Buffer Event Stream
OES : Orch. Event Stream
DES : Direct Event Stream

DES and BES can be leveraged even in Non- BizTalk Applications.
OES and MES : Can be used only in BizTalk applications.


DES will have very less latency, as it tracks data directly into BAM primary import database. For latency to be  very less, use DES.

If you are coding against pipeline, use MES
If you are coding against orch., use OES

Dev. should use stream based on the component where they are coding, it will have impact on performance.