The main reason for this blog post is due to this newsgroup post Download Sample from here . Step #1: Catching SOAP Exception: Whenever you call a Web service it's a good practice to handle the SOAP exception specifically rather than just leaving the orchestration to throw an un-handled exception which will result
Similar Posts
Exposing an Orchestration as Web Service This is the safest option you can choose, when you want to expose your business process as an industry standard
Normally when we need to consume a .asmx web service in BizTalk 2004 2006 (NOT R2) inside an orchestration, we add a web reference, which will create all
UPDATED 24th August 2007, to reflect Richard Seroter's comment There is no necessity to explain the importance of caching in any server based developments
So what if I want to open up a BizTalk web services channel that accepts any XML message and then lets BizTalk Server figure out what do with that data
