Installing BizTalk Server 2010 on a multiserver environment

I found a good whitepaper on the multiserver setup of BizTalk Server 2010. It can be viewed here.

Message inspector – huh?? whats that??

A message inspector is an extensibility object that can be used in the service model’s client runtime and dispatch runtime programmatically or through configuration and that can inspect and alter messages after they are received or before they are sent.

Click here for more…

Invoking restful services with BizTalk 2010

ReST supports GET, PUT, POST, and DELETE methods. So, if one has to use ReST with BizTalk Server, the adapter to be used should be able to:
•Exchange non-SOAP messages.
•Support GET, PUT, POST, and DELETE methods.

If we look at the adapters available with BizTalk Server 2010, only the HTTP adapter satisfies the first criteria but it does not support GET (it does support the POST method). Similarly, the webHttpBinding (that supports consuming and exposing ReSTful services) available with WCF-Custom adapter can send non-SOAP messages but that too has no way of specifying the HTTP verb to be used. All other adapters either do not support HTTP verbs or always exchange SOAP messages. So, there is no way to have an out-of-box BizTalk configuration to consume a ReSTful service. To use BizTalk Server with ReST, we’ll have to do some customizations around HTTP adapter or the webHttpBinding of the WCF-Custom adapter. There is no prescribed way of doing customizations around the HTTP adapter. However, to the webHttpBinding, we can add some custom behaviors that when coupled with webHttpBinding enable BizTalk users to invoke and consume ReSTful services. Through these customizations, we can specify the following:
•The HTTP method to use in the request (GET, PUT, POST, DELETE).
•How to form the request URL from operation method parameters (URL path and query string template).
•How to encode the request body and decode the response.

With WCF-Custom port configuration, there’s no way of specifying these customizations directly on the webHttpBinding. So, we’ll have to put these values in the request message. After specifying the values as part of the request message and adding a custom behavior to the webHttpBinding, when the request message hits the WCF-Custom port with the webHttpBinding, the custom behavior extracts the values from the request message and frames the required HTTP transport.

See this link to read more…

See this link for sample code.

CU2 for BizTalk 2009 released

MS have released a cummulative update to BizTalk 2009 which fixes a variety of issues that may or may not apply to you. See this link for details!

Resequencer Pattern – An Insider look

Here is a very good post on how to implement a resequencer pattern in BizTalk to ensure ordered delivery of messages. Good work there by Richard Seroter.