BizTalk™ Unleashed

Example 3: HTTP-Based Schedule Correlation, with BizTalk Server on One End and Any External Business Process on the Other End

This example illustrates a case of schedule correlation where BizTalk Server is at one end, and a non-BizTalk Server external process is at the other. Schedule correlation back to a BizTalk Server orchestration schedule does not require a BizTalk Server on the receiving end. A primary design goal of BizTalk Server was to allow interoperability with other environments not running BizTalk. Let's see how this is possible. The correlation information is passed as part of the message as seen in earlier examples. The message moves from the source schedule to the destination schedule with the correlation information contained ...