Live Blog - Day 1 Pluralsight BizTalk Course - WCF Adapter Receiving

• BizTalk AND WCF
• WCF fits nicely into the BT architecture
• Both have pluggable protocol stacks
• WCF Receieve Adapters expose WCF endpoints
• Messages routed to BT via BT Adapter API
• HTTP based binding are isolated (run in W3WP.exe)
• Send Adapters build a dynamic Channel Stack
• No proxy needed in Orchestration or Send Port ala SOAP Adapter
• Configuration stored with Receieve Location or Send Port instead of app config file
• Use same WCF config for supported features
• One adapter per supported OOB Binding
• WCF Adapters
• WCF-NetTcp      (In Process)
• WCF-WsHttp     (Isolated)
• WCF-NetNamedPipe
• WCF-BasicHttp
• WCF-NetMsmq
• WCF-Custom
• WCF-CustomIsolated
• Receieve Adapter Architecture
• BT receieve adapter creates a ServiceHost derived instance for each Receieve Location
• Public WCF extensibility point
• Rather than implementing particular contracts, endpoints expose loosely typed contracts
• Behaves like a SOAP intermediary
• Avoids double serialization (known issue with SOAP Adapter)
• WCF-NetTcp Receieve Adapter
• BizTalkServiceHost will use NetTcpBinding for its endpoint
• Use Cases:
• For Windows based internal
• Arguably the most direct way to access the MessageBox