Here's another code sample. This one I wrote quite awhile ago and just hadn't gotten around to posting it. When working in BizTalk - one of the most important pieces of information floating around is the Message Context. The Message Context is essentially a set of name/value pairs (qualified by a schema namespace URI) that follow messages around as they flow between Receive Ports and the MessageBox, from the MessageBox to Orchestrations, from the MessageBox to Send Ports (you get the idea - messages don't go anywhere without their corresponding context).
The Context is almost always used by the subscription services in the MessageBox to figure out where a particular message is supposed to be routed. Often times the Context property "MessageType" is used (especially with Orchestration subscriptions this is often the case).
Most of what Receive Pipelines do is promote or add properties into the context (only promoted properties are used for subscriptions services however). Other components use Context properties as well, for example the HTTP Send Adapter will send a SOAPAction HTTP Header if there is a value for the SOAPAction Context Property in the message it is processing (this is if you want to use the HTTP Adapter in the raw to send SOAP messages to a Web Service).
The code sample - which I call the Context Adder pipeline component (which you can download here (full source) is a component you can place in any stage of either a Receive or Send pipeline, and you can configure it with a collection of Context properties (simple written properties or promoted properties). The component will just blindly put whatever values you configure it with into the context. This is just useful as a generic way to add properties into the Message Context when needed (and it is needed pretty often - at least I need it pretty often).
BizTalk Comments [6]
Remember Me