Contents tagged with BizTalk Services
-
BAM whitepaper available on MSDN
After presenting our session about BizTalk Server Business Activity Monitoring (BAM) at Teched 2008, my partner in crime and CTO of Tellago Joe Klug and I decided to coauthor a paper that highlighted the capabilities and architecture of BAM from a developer perspective. The final result is an 87 pages paper that is now available both for download and online on MSDN.
-
WCF behaviors vs. pipelines on BizTalk Server R2
BizTalk Server R2 is close to be released and one of the most attractive features for traditional BizTalk developer is the new set of Windows Communication Foundation (WCF) adapters. As of today, this set of adapters represents the best way of leveraging the WCF capabilities into BizTalk Server applications. Arguably, the WCF adapters can be seen as a continuation of the previous SOAP and WSE 2.0-3.0 adapters. However, there are major differences between WCF and its technology predecessors. WCF is fundamentally a messaging framework that offers a lot of capabilities beyond the traditional Web Services frameworks. By this time you might already know that WCF is going to be the core of the future BizTalk messaging engine. However, at this point, there is still some overlapping between WCF and the BizTalk messaging engine capabilities. Why I am writing all this? Well, I decided to start writing a series of posts about how to utilize some of the WCF capabilities that present some overlapping and also complement existing BizTalk Server features. Thinking about that, I don't see a better place to start than with WCF behaviors and BizTalk Server pipelines.
-
SCA committees
For more than I disagree with the goals of Service Component Architecture (SCA), it is undeniable that this is going to help.
-
Christian on Duplex messaging with BizTalk Services
I just realized that my friend Christian Weyer has blogged a fantastic sample about Duplex messaging using BizTalk Services. In fact, Christian details some of the benefits of this approach for real world scenarios. So read Christian article first and then you can complement with mine.
-
Implementing duplex messaging with BizTalk Services
It is undeniable that the use of BizTalk Services opens up a new set of possibilities for distributed applications. This post is not intended to provide an overview of BizTalk Services. My friend Clemens Vasters and the BizTalk Services team have been doing a fabulous job in that regard. Instead, I’ve decided to start blogging about different messaging scenarios that I have been implementing using BizTalk Services. Particularly, this post is focused on duplex messaging. As you might already know, duplex contracts are one of the features of WCF that allows implement scenarios on which both WCF endpoints exchange message independently. Duplex messaging becomes difficult to adopt in scenarios on which the two endpoints reside on different organizations (different networks). This is partially given that a real world duplex messaging scenario requires a whole new set of considerations in terms of network resources (opening ports for receiving the callbacks), different security boundaries, etc. This is what makes BizTalk Services an ideal solution for this type of scenario. Now organizations don’t have to spend time and resources implementing the trusting mechanisms with other organizations. Instead they can rely on BizTalk Services for all that. The following picture might help to clarify my point.