UPDATE: I have since moved these articles to my own blog and they can be found here.
I just posted my third article in a series about BizTalk Server 2006 R2 integration with Windows Communication Foundation. The topic of this piece is Transactions and how to create and consume WCF services using the WS-AtomicTransaction specification. Transactions are sometimes a tricky thing to grasp, so I included a brief (but hopefully understandable) explanation of the key WCF transaction concepts. Then I showed how to use BizTalk to flow transactions to services. A few gotchas arose, which simply demonstrates that while BizTalk Server 2006 R2 is a move forward, it’s still relatively immature with regards to .NET 3.0+ integration.
As always, if you have any questions or comments on the article, let me know.
Richard Seroter's Architecture Musings 
I am not able to configure and run the sample for BizTalk and WCF: Part I, Operation Patterns.
How to configure receive port/location to absorb the “starter” message which triggers the orchestration from winform app?
Thanks
Panch,
You can auto-generate the receive location/port from the BizTalk WCF Service Publishing Wizard. That wizard creates the IIS service (if you’re using an Isolated adapter) and BizTalk receive location (if you check that box in the wizard). Then you create metadata for the Winform app by pointing svcutil.exe at the IIS endpoint.