Doubts in Biztalk

[quote:758cbce30c=\”BizTalkSavvy\”]
1. what’s difference between message routing and content routing
[/quote:758cbce30c]

Content-Based Routing (CBR) is one of the options for message routing. The Pub/Sub engine of BizTalk supports routing based on predicate expressions based on Promoted Properties. Promoted properties can be independently added to a message by adapters, pipeline components and so on to achieve routing (you could call that Context-Based routing, I guess). But, BizTalk can also route messages based on the content of the body of the message itself by promoting content (the values of attributes or elements within the message) to to the message context, allowing them to be used as part of the routing rules predicates.

[quote:758cbce30c=\”BizTalkSavvy\”]
2. I will use promotion properties for making the msg available in send ports. Then where should i use distingushed fields? Can any one give a real time example.
[/quote:758cbce30c]

Promoted properties are usually used for routing. I guess this is what you mean by \”making the msg available in send ports\”. Distinguished properties on the other hand are used solely within orchestrations as a way to enable easy access to content within the message in Expression shapes.

[quote:758cbce30c=\”BizTalkSavvy\”]
3. What is Convoys in BizTalk ?
[/quote:758cbce30c]

Convoys are a messaging pattern you can apply in biztalk that allow processing of related messages by a single orchestration instance. They are typically used to achive sequential, in-order processing of related messages (a sequential convoy).

Here’s a very good article on the subject:
http://msdn.microsoft.com/library/en-us/bts_2004wp/html/956fd4cb-aacc-43ee-99b6-f6137a5a2914.asp?frame=true

[quote:758cbce30c=\”BizTalkSavvy\”]
4. What is the difference between static and dynamic binding. Can any one give example?[/quote:758cbce30c]

Static binding usually means that the definition of the relationship between orchestration and port is static: defined once. Usually this means that the decision to use a specific adapter and endpoint (URL) was either done at design time (early binding) or is made during deployment (late-binding), though I guess this could include direct-bound ports as well.

With dynamic binding, however, there’s no way to know to which url (endpoint) and though which adapter the message is going out until at runtime when the send actually is done. This allows you to decide at runtime to where you want to send the message without creating complex (or sometimes impossible) routing rules.

For example, you could use a dynamic send port to send a reply EMail message using the SMTP adapter to an EMail address that was included inside an element in the original message you’re processing. Since the EMAil address is not known until you’re actually processing the message, there’s no way to use static binding to support the scenario, but using a dynamic send port makes it very easy to address.