Example 4: Non-HTTP-Based Correlation Using Two BizTalk Servers

Non-HTTP-based correlation is much more difficult to implement than HTTP-based correlation. The dynamic orchestration port (the port through which we send a message out of the orchestration schedule to the external entity) and the orchestration BizTalk Messaging receive ports (the ports through which we receive the response message back into the orchestration) support HTTP transports natively.

This is evident when you are required to enter a URL (for the return ASP page) in addition to the channel name in the BizTalk messaging orchestration receive port as shown previously in Figure 16.23. This simply means that there is built-in support for HTTP-based transport. For non-HTTP-based ...

Get BizTalk™ Unleashed now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.