BAM Data Sources – Where the data came from?

The most common data sources used with BAM are:

• BizTalk Application: BAM can capture data from fields in BizTalk messages, can capture milestones from the date and time a BizTalk message is received or sent and also can capture fields in the BizTalk context properties.
  Data capture from BizTalk, normally, is configured using the Tracking Profile Editor (TPE)
• BAM API: .NET code can write data directly into BAM using an API. Code that is executed in BizTalk, normally use either the OrchestrationEventStream (in orchestrations) or MessagingEventStream (in pipelines) classes.
  Code that isn’t executing in BizTalk will use either the DirectEventStream or BufferedEventStream classes.
• WCF Services (WCF Interceptor): BAM can capture data from SOAP envelope in a WCF request, response or fault message. The data is specified using the interceptor configuration (IC) file (XML file created by the developer).
  The service’s app.config must be modified to load the BAM components at runtime.
• WF Workflows (WF Interceptor): like WCF Services, BAM can also capture milestones from WF Activities. Am IC file is used to specify the data that must be captured. BAM components must also be loaded at runtime.

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community. View all posts by Sandro Pereira