Click here to Skip to main content
Click here to Skip to main content

Explaining the BizTalk Architecture to your Grandma

By , 27 Jan 2006
Rate this:
Please Sign up or sign in to vote.

Introduction

I have heard they ask "How would you explain Excel (any product) to your grandmother?" in many companies; a question popularized by Microsoft, I believe. First, I am not so sure my grandma would understand any technology product so easily. Also, I am not sure if this is a good question to ask a software developer; maybe, to someone from sales, yes! On the record, I must say that my grandmother is an incredibly smart lady. So the question really boils down to "How you would make an IT common man understand what a product is all about?" This is what I am trying to endeavor in this article.

Sometime back, I had to explain to a group of non-IT folks about BizTalk Server. You know the people who wouldn't understand all these geeky terms like SOA, XML, SOAP, or Orchestrations (pardon me, she says she knows about SOAP!). I thought I'd share my experience here in this article for the benefit of the CodeProject community. This article is aimed at you if you have heard about this wonderful thing called BizTalk Server, and want to understand what it is clearly before diving into the marketing material which seems to be the same for every product - the "panacea" of all your problems.

Drawing a Parallel

BizTalk Server is Microsoft's enterprise application integration solution, with built-in support for XML and SOAP. It offers integration with Visual Studio .NET, and provides speed, reliability, and flexibility for standards-based enterprise application integration. An analogy they say is "Similarity in some respects between things that are otherwise dissimilar". So for me, to explain BizTalk, I would start off with an analogy. In the section below, I am comparing BizTalk Server to a Customs facility.

The Customs Facility

sample image

What we have in the figure above is a Customs facility. We have an Import Terminal through which a large number of packages come in by different modes of transport: planes, ships, buses, trucks, barges. These packages then go through a standard inspection process, with several stages including identifying the package, unpacking the contents, and then identifying the shipper. The packages then go to a central store. From there, customs inspection of the packages takes place. The process could be different for different types of packages, and there is a "Customs Inspection Rules and Regulations Manual" which details the inspection process, and which in practice, gets updated from time to time. After a package passes the inspection process, it is sent back to the central store, from where it is packaged and sent to the correct destination.

The BizTalk Server Architecture

sample image

The figure above is the architecture of a BizTalk Server messaging subsystem. As you will notice, this figure is same as the previous figure except for the labeling. Here, instead of packages moving, we have XML messages that are moving. The files come in through Receive Ports and are passed to the "Message Box" through a "Receive Pipeline". They are then picked up by "BizTalk Orchestrations" and are processed. Custom rules maybe loaded and executed at this point. They are then send out using a Receive Pipeline through a "Send Port" to the destination.

Receive Ports

The Receive Ports are how messages come into BizTalk. Messages can come into BizTalk by any means of transport like HTTP, SOAP, SQL, file, EDI; just like the way packages arrive via planes, ships, buses, or trucks. How they are transported does not change how they are processed later. This is a very powerful feature because it gives you the ability to change the transport type and the source of the data even after your application is deployed, without changing your application implementation. For instance, let us say some sales related data is coming in from a shared "FILE" folder in Europe connected via WAN today, tomorrow you can configure it as an FTP pickup from a remote server from India, or probably accept it as an HTTP request over the web posted from a browser.

Adaptors

Adaptors are the BizTalk way of handling additional transport. Just like you can have a private plane fly your package in, you can write your own adaptor for a custom transport, like say POP3. So there is always scope for buying or writing your own custom adaptor to integrate with all the other available transports. For instance, you can have a DB2 adaptor or a SAP adaptor.

Receive Pipeline

The Receive Pipeline contains different mechanisms like "Decoding" (if encoded), "Disassembling" (if there are multiple parts), and "Party Resolution". This is similar to the unpacking and identifying the sender, in our example. Just like we have an express lane for certain packages, there is a "Pass Through" pipeline facility in BizTalk which is essential a smooth transfer to the Message Box. Just like you can have special handling instructions for certain packages, you can write custom pipeline components using the framework.

Message Box and Subscriptions

The BizTalk Message Box lies in the heart of the BizTalk messaging subsystem; this is like our central store. This message box is, in fact, realized as a SQL Store; so this way, BizTalk ensures reliability for your messages in terms of guaranteed delivery. Even if a node in BizTalk fails, the message will be picked up by another node in the farm. BizTalk also ensures that it does not delete the file from a pickup folder location while using file/any transport, unless it is persisted completely in SQL. Well, this also means you need to have a fault tolerant SQL Server architecture. Just like we will be noting down a few important details while we unpack the packages, in the pipeline, certain properties are promoted into the context, like transport information: the most important of these being the incoming XMLSchema#RootNode. The BizTalk Publish-Subscribe mechanism identifies which Orchestrations subscribe to that particular message, based on this promoted information, and routes it accordingly.

Orchestrations

Orchestrations are processes that are defined in the Business Process Execution Language (BPEL). This could be something like, say: if quantity is greater than threshold, apply discount, else standard discount. At this stage, you can also change the format of the message using Transformation Maps, or you can call some other web service to do an operation like credit card verification. This is like our example in which we have the customs inspection process and checking with the bank if the excise payment is cleared.

Business Rules Engine

Business Rules Engine is used by BizTalk to load the current policies which are a collection of Rules from the Orchestration. These rules are kept separately as these could change from time to time. In our example above, this would be something like, during Olympics there could be certain relaxations in guidelines or certain promotions in effect. These change from time to time, and they are kept separate. This is the idea behind the Rule Store in BizTalk.

Send Pipeline

The "Send Pipelines" are just the opposite of the "Receive Pipelines" and they do operations like "Encoding" the message, or "Assembling" or "Signing" the message. This is like packing and sealing a package before we send it. Just like we have different types of packaging like bubble wrapping and cushion mailers, there could be different pipeline components at this stage.

Send Ports

Send Ports also handle transport like receive ports, but their direction is the reverse. Here, the message direction is from the Message Box to the destination. Send Ports can subscribe to a message directly from the Message Box, without passing through the orchestration. This is like having a package coming in from a certain shipper which has a prior clearance attached with it. This is called Content Based Routing (CBR).

Summary

The example above of the Customs facility is certainly flawed when you think deeper because the BizTalk Server is way more powerful than this example to illustrate. But for a person who is quite new to BizTalk, this is a good start. I hope this article has addressed that objective, has got you excited about BizTalk, and has lived up to its title.

I feel a small sample is in order here, at the least a CBR, maybe picking up a file and sending it to an FTP location or maybe even another folder. But I guess that has to be another article, to stay within the scope of the original objective.

P.S.: The views expressed in these essays are those of the author, and in no way represent, nor are they endorsed by Microsoft or anyone else, as far as I know.

History

  • Version 1.0 - January 25, 2006.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

_ABHILASH_MS_
Architect
United States United States
Abhilash is from Kerala, South India. He is presently working as an Integration Consultant for many fortune 500 companies in his current role at Neudesic
 
Abhilash has been programming since he got his first PC, when they used to load BASIC using tapes. He got his first real PC in 1994 - a 286 with a 40 MB hard disk, 1 MB RAM, and a 5.25 " FDD with a HGA graphics card.
 
Pascal was his first favorite programming language. And he thought at one time that it was the greatest language. He never really got on to the Delphi wagon, but went with C++, and then progressively VC++ SDK, MFC, COM, and then eventually chose C# as his preferred language once .NET came along. With the emergence of SOA into mainstream, Abhilash chose BizTalk as his SOA realization tool of preference. He opines that BizTalk helps implement SOA; by so clearly separating the message and the underlying implementation, and connect apps purely based on contracts. This is what many classic technologies like IDL tried to do, but somewhere, the point got lost. BizTalk is his tool of choice for EAI. Abhilash has worked in various platforms including Win32,.NET,Linux, and Mainframes and has professional experience in embedded development and voice telephony.This helps him understand the EAI domain better.
 
His passions include programming, blogging ,cricket and chess. He likes to troll MS user groups and used to run a site www.biztalkcafe.com as a hobby. The site has a forum, so if you work with BizTalk server, he would like to hear about your experiences there.
 
He was awarded Biztalk Server MVP in April of 2006.
 
His life events gets recorded here www.abhilash.in. You can connect with him on Linkedin

Comments and Discussions

 
GeneralMultiple Instances of one type of Adaptor Pinmemberjnky_boy2-Mar-10 5:30 
GeneralNecessary Article, But Misses the Point [modified] PinmemberMember 36807855-Jan-10 7:06 
GeneralRe: Necessary Article, But Misses the Point [modified] PinmemberPetr Abdulin27-Feb-12 17:02 
QuestionTo get Total message sent/Received by Biztalk using C#.net Pinmemberchentil_m27-Dec-09 0:12 
AnswerRe: To get Total message sent/Received by Biztalk using C#.net PinmemberLe Centriste8-Feb-10 6:29 
Generalhi can i use biztalk with bpel Pinmemberkapamarou12323-Mar-09 21:32 
GeneralInformative article Pinmembersujith ms17-Feb-09 15:43 
GeneralThe best way to introduce BizTalk Pinmemberthawait.himanshu26-Oct-07 2:24 
GeneralRe: The best way to introduce BizTalk Pinmember_ABHILASH_MS_29-Jan-08 8:07 
GeneralBrilliant WORK, Pinmembermysmehmood9-Jul-07 4:31 
GeneralSuggested reading ..... Pinmemberfwsouthern28-Jun-07 16:55 
GeneralBizTalk Server Implementation Pinmembersankranti6-Jun-07 20:42 
GeneralRe: BizTalk Server Implementation Pinmember_ABHILASH_MS_7-Jun-07 9:24 
GeneralVery clear introduction Pinmemberjamba20058-May-07 22:12 
GeneralRe: Very clear introduction Pinmember_ABHILASH_MS_7-Jun-07 9:25 
GeneralMessage from my friend PinmemberNaveen Karamchetti3-May-07 11:06 
GeneralGood Read Pinmemberbellie26-Dec-06 19:59 
Generalgood one Pinmemberrmu90918-Dec-06 8:01 
JokeBiztalk rule utilities [modified] PinmemberMarco Ensing21-Apr-06 17:28 
NewsRe: Biztalk rule utilities [modified] PinmemberMarco Ensing2-Jan-07 12:24 
GeneralRe: Biztalk rule utilities PinmemberMike100116-Jun-07 1:22 
GeneralRe: Biztalk rule utilities PinmemberMarco Ensing18-Jun-07 2:09 
GeneralThe Sample you folks wanted Pinmember_ABHILASH_MS_24-Feb-06 1:57 
GeneralGood Work :-) PinmemberJerin7-Feb-06 2:33 
GeneralRe: Good Work :-) Pinmember_ABHILASH_MS_9-Feb-06 8:06 
GeneralInteresting but got more confused Pinmembermsali6-Feb-06 19:21 
GeneralRe: Interesting but got more confused Pinmember_ABHILASH_MS_9-Feb-06 8:05 
GeneralDoesn't hit the spot Pinmemberantidemon31-Jan-06 23:57 
GeneralRe: Doesn't hit the spot Pinmember_ABHILASH_MS_2-Feb-06 6:38 
GeneralRe: Doesn't hit the spot PinmemberDoug Houck9-Feb-06 5:00 
GeneralRe: Doesn't hit the spot Pinmember_ABHILASH_MS_9-Feb-06 8:02 
Questionhow about a cricket analogy? Pinmemberjasperp30-Jan-06 20:48 
AnswerRe: how about a cricket analogy? Pinmember_ABHILASH_MS_31-Jan-06 13:03 
AnswerRe: how about a cricket analogy? PinmemberDamage_Inc17-Feb-06 4:04 
QuestionNice Article But?? Pinmembervl950t30-Jan-06 20:28 
AnswerRe: Nice Article But?? PinmemberDoug Houck31-Jan-06 3:36 
GeneralRe: Nice Article But?? Pinmember_ABHILASH_MS_31-Jan-06 13:01 
GeneralExcellenet PinmemberMATTIE30-Jan-06 12:01 
GeneralGreat Article! Pinmemberkdubious28-Jan-06 0:36 
GeneralRe: Great Article! Pinmember_ABHILASH_MS_28-Jan-06 8:27 
GeneralGood work again :-) PinstaffNishant Sivakumar27-Jan-06 12:25 
GeneralRe: Good work again :-) Pinmember_ABHILASH_MS_27-Jan-06 18:18 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web02 | 2.8.140421.2 | Last Updated 27 Jan 2006
Article Copyright 2006 by _ABHILASH_MS_
Everything else Copyright © CodeProject, 1999-2014
Terms of Use
Layout: fixed | fluid