The examples shown will work in an environment where the number of trading partners is small or volume of data is relatively low. However, it gives a good outline for integrating the two products for transport purposes.
For scaling and high volume implementations, develop a common XML or flat file routing record that identifies the document, sender, receiver document type, and a control number. An example of an XML routing record is shown below.
<routing ReceiverKey="Sojourn Information Systems" SenderKey="e*BIS" DocumentName="StandardPO" ControlNumber="X57394" />
Additional routing records can be created for flat files or other formats of data besides XML depending upon your needs. Routing records provide all the information necessary for a component or receive function to process "self-routing" documents into BizTalk Server. Doing this can make your deployment scalable because you do not have to set up multiple BizTalk Server receive functions.
You can find recommendations for developing custom envelopes for routing data and further details about meeting your specific needs in the BizTalk Server documentation.