Keith Lim's Biztalk BAM Blog

Soliciting Biztalk BAM scenarios and issues

How great it would be if every features we put in to the software is what customers need/want. Anyway, I am creating this entry to solicit your input on how you use or plan to use BizTalk BAM. Please response as a comment with your scnenario. Do also

BAM API: Using OrchestrationEventStream

Since there is not much documentation* on this yet on how to use OrchestrationEventStream (an EventStream that is in synch with Orchestration), here is a quick info on the howto: This new feature is found in Microsoft.BizTalk.Bam.XLANGs assembly. From

Sample code to retrieve server and database info of Biztalk MessageBox and PIT

Since there is a request for this, here is an example to retrieve server name and database for Biztalk MessageBox and BAM Primary Import database. Since this is accessing internal implementation, this code is not supportable (use at your own risk) and

Continuation scenarios with mixed of TPE-enabled and non-TPE-Enabled tracking:

It has been a while since I last blogged on this. Let's continue from where I left off. Let's pick two continuation scenarios: the first, a TPE segment continues to a non-TPE segment, and the reverse being the second. 1. TPE-enabled segment continues

DirectEventStream vs BufferedEventStream

Which EventStream to use: DirectEventStream (DES) vs BufferedEventStream (BES) Use DES when you don't want any latency of data appearing in BAMPrimaryImport database. Since this is synchronous call, any error will be thrown back to the calling application.