Messaging Event Streams
You use Messaging Event Streams (MES) when your application runs on a computer on which BizTalk Server is installed and you are you are tracking items that are part of BizTalk pipeline transactions. Using MES ensures that your BAM event persistence remains in sync with the BizTalk pipeline transactions.
Messaging Event Streams are instances of EventStream objects returned by the Microsoft.BizTalk.Component.Interop.IPipelineContext.GetEventStream method.
Messaging Event Streams are asynchronous and store tracking data first in the BizTalk MessageBox database. Periodically the data is processed and persisted to the BAM Primary Import database by the Tracking Data Decode Service (TDDS).
IPipelineContext is found in the Microsoft.BizTalk.Component.Interop namespace. To use the API you must add the Microsoft.BizTalk.Pipeline (in microsoft.biztalk.pipeline.dll) to your project.
See Also
OrchestrationEventStream
Microsoft.BizTalk.Bam.EventObservation.EventStream
Microsoft.BizTalk.Component.Interop
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for