Configuring BizTalk Orchestrations to handle un-typed messages

Found one of useful article thought of sharing

A typical orchestration in BizTalk deals with several kinds of messages. A message in BizTalk is always strongly typed. It is usually associated to some schema defined in the project. A Receive/Send shape in an orchestration is tied to a message declared in the Orchestration View. In the case of an un-typed message, the message type is set to 'System.Xml.XmlDocument', instead of a schema type. The class "XmlDocument" is a super class for all XML messages, and hence it can hold any type of XML message and subsequently any type of orchestration message. To summarize, an un-typed message is one whose message type is set to "XmlDocument" in an orchestration

Consider that we are integrating several small messages into a StoreFront application. This application deals with several kinds of messages like "Car", "Music" and "Book". These messages need to be integrated into a "StoreFront" message. So, a designed orchestration would receive several different types of messages. The orchestration in the article is shown below:

In the above orchestration, the "Send" and "Receive" shapes can handle any type of message. It is because the "Receive" shape is associated with a message which is of type "XmlDocument".

The Decision shape separates out the different kinds of messages.

// Message Type consists of TargetNamespace#SchemaRootElementName

InputMessage(BTS.MessageType) ==

http://untypedmessages.book/#BookMessage

// Message Type consists of TargetNamespace#SchemaRootElementName

InputMessage(BTS.MessageType) ==

http://untypedmessages.car/#CarMessage

// Message Type consists of TargetNamespace#SchemaRootElementName

InputMessage(BTS.MessageType) ==

http://untypedmessages.music/#MusicMessage

Notice the commonality in the above schemas. A quick explanation of one of the schemas is as follows:

The schema "Car.xsd" has the following properties:

RegID - The registration ID.

Make - The make of the car.

Model - The year of manufacture.

Operation - Can be either "BUY" or "SELL".

ExpectedPrice - The expected price.

The "InputMessage" message is specified in the Receive shape:

The "OutputMessage" message is specified in the Send shape:

The Message Assignment shape has the following lines of code: