Service Bus, Workflow, BizTalk Server, and Windows Azure BizTalk Services

I see questions from various customers and partners – Microsoft has so many technologies for doing “Integration”, when do I choose what? In this post, I will put forth my views on firstly, why there are so many technologies, and then based on that, it should become clearer when you should use what. Let me…


Improved performance for ordered send ports in BizTalk 2010 R2

BizTalk 2010 R2 CTP has been released – you can read more about it here. One of the features mentioned is – We have also made enhancements in our engine to improve the performance in ordered send port scenarios. Here, I’ll briefly describe the enhancement we’ve made. Assume you have 5 ordered send ports (SP1 through…


The new WCF-WebHttp Adapter in Microsoft BizTalk Server 2010 R2

One of the new adapters we’ve added in Microsoft BizTalk Server 2010 R2 is the WCF-WebHttp Adapter. This adapter is designed to make it easy for users to consume REST services as well as expose REST endpoints using BizTalk. The Adapter allows you to easily define URI parameters and map them to BizTalk Context Properties,…


Invoking one-way operations with the WCF Adapters

I had documented a workaround at a while ago. This post is to inform you all that the workaround has been incorporated into the WCF Adapter product code. Henceforth, it will be possible to set up a 1-way Send Port which uses a binding such as BasicHttp (or the WCF-BasicHttp adapter) and invoke a 1-way…


Workflow with one-way contract (only Receive), NamedPipe transport with TransferMode = Buffered – observed behavior

I came across this behavior a few days back while investigating a bug.   Here’s what I had: Workflow: 1. Has a number of activities executing in sequence. None of the activities are of type AsyncCodeActivity, and none of the activities create Bookmarks. 2. The Workflow starts off with a Receive, and has no SendReply….


Scale-Out Dynamic Send Ports

NOTE: BizTalk 2013 now supports assigning Dynamic Send Ports to non-default hosts! Thus, the hacky workaround in this blog is no longer required for BizTalk 2013.   Before your read further – please note that the technique mentioned here for scaling out dynamic send ports is UNSUPPORTED by the Product Team. I’ve gotten this to work…


“Route Failed Messages” routes the wrong message – really?

Consider the following scenario: You have an adapter on a Receive Location, which submits a message in Format A into BizTalk. The Pipeline configured on this Receive Location converts the message into Format B. Assume that there is no map configured on the Receive Port. You have the “Route Failed Messages” option enabled on the…


Performance Tip – when using WCF-Custom with Dynamic Send Ports and Custom Bindings on BizTalk Server 2009

In BizTalk Server 2006 R2, when the WCF-Custom adapter was used with any binding, the WCF-Adapter would try to determine, at runtime, whether a System.Transactions TransactionScope was required when sending a message over a channel. This involved the following: If an out-of-box binding was used, then most of those bindings have a Transactions property. We…


Using the WCF federation bindings with the WCF Adapter in Microsoft biztalk server

Even though the WCF Federation bindings aren’t yet officially supported for use with the WCF Adapter, for most purposes, you can get your scenario to work (and in case your scenario does not work as expected, you should contact Microsoft Support so that we can investigate the issue – we of course might not fix…