Inlining Back-end Invocation
The inline call version, of the full solutions, provides the fastest processing times. The inline version eliminates the overhead of persisting the request and response messages to and from the backend systems in the MessageBox database. In the adapter version, the message goes from the sending orchestration to the MessageBox. The host running the adapter picks up the message, and sends the message to the back-end process by again posting it to the message box.
The efficiency of inlining comes at a cost of binding the orchestration directly to the transport protocols of the back-end systems. In the inline version, rather than communicating through logical ports, the orchestration calls the back-end systems through three custom assemblies. If a back-end system transport changes, an assembly must be rewritten and recompiled. The following table describes the assemblies and their function:
| Assembly Name | Back-end Connection |
|---|---|
| Microsoft.Samples.BizTalk.WoodgroveBank.PaymentTrackerCall | Uses MQSeries get and put message functions. |
| Microsoft.Samples.BizTalk.WoodgroveBank.PendingTransactionsCall | Invokes the Web service for the transaction system. |
| Microsoft.Samples.BizTalk.WoodgroveBank.SAPCall | Calls the web services simulating SAP. |
See Also
Implementation Highlights of the Service Oriented Solution
Developing a Service Oriented Solution
Translating the Patterns of the Service Oriented Solution
Monitoring the Service Oriented Solution with BAM