Article ID: 948028 - View products that this article applies to.
In Microsoft BizTalk Server, you add inbound maps to receive ports, or you add outbound maps to send ports. When you do this, you cannot add more than one map by using the same source schema. This limitation exists even if the maps use different root nodes in a multiple-root source schema.
This behavior makes sure that no ambiguity occurs during runtime when the engine determines which map to apply based on the message that is going through the port.
By design, the BizTalk Server UI does not allow for multiple-root source schemas in multiple maps.
To work around this behavior, execute the transform by using an orchestration that contains logic to determine which map to apply to the incoming data.
For more information about transforms in orchestrations, visit the following Microsoft Developer Network (MSDN) Web site:
http://blogs.msdn.com/biztalk_core_engine/archive/2004/09/13/228633.aspxFor multiple-root scenarios, you can separate each root into separate schemas. Then, you can use the maps that have unique schemas in the port.
The purpose of adding multiple maps to a port is to let the port transform multiple message types at runtime. If you add multiple maps to a port, a message is processed by whichever map has a source schema that matches the message type when the message arrives. The message is transformed only one time, even if the output of the transform matches the source schemas of the remaining maps.
Article ID: 948028 - Last Review: March 18, 2008 - Revision: 1.1