BAM API – Using OrchestrationEventStream to write BAM Events from BizTalk orchestration
The OrchestrationEventStream (OES) is one of the artifacts developers should consider in order to programmatically populate a BAM activity model from within a
BAM API – Using MessagingEventStream to write BAM Events from pipeline components
MessagingEventStream (MES) is used inside a BizTalk pipeline component to write Bam as part of the messaging transactions ensuring that your BAM event
BizTalk Server: The BAM API objects…
The BAM API defines four main classes: DirectEventStream: used in a NET application to do a buffered write of data to BAMBufferedEventStream: used in a NET
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
BAM – Why are the times for my tracking data in the BAM portal incorrect?
BAM captures milestones for objects derived from MicrosoftBizTalkBamEventObservationEventStream in Coordinated Universal Time (UTC) format When you send