Article Series on BizTalk and WCF: Part V, Publishing Operations Patterns

UPDATE: I have since moved these articles to my own blog and they can be found here.

I just posted another article for TopXML.com as part of my series on BizTalk + WCF.   This post covers the various ways to expose WCF services and endpoints out of BizTalk itself.

Topics include: exposing one-way services, working with services exposed via schemas or orchestrations, handling exceptions, generating MEX endpoints, hosting the WS-Http adapter in-process, using simple type service parameters, and using multi-part messages.

Series Summary
 BizTalk and WCF: Part I, Operation Patterns Get the source code!
 BizTalk and WCF: Part II, Security Patterns
 BizTalk and WCF: Part III, Transaction Patterns
 BizTalk and WCF: Part IV, Attachment Patterns
 BizTalk and WCF: Part V, Publishing Operations Patterns Get the source code!
BizTalk and WCF: Part VI, Publishing Advanced Service Patterns
BizTalk and WCF: Part VII, About the BizTalk Adapter Pack Get the source code!
BizTalk and WCF: Part VIII, BizTalk Adapter Pack Service Model Patterns
BizTalk and WCF: Part IX, BizTalk Adapter Pack BizTalk Patterns

Technorati Tags: ,



Categories: .NET, BizTalk, SOA, WCF/WF

6 replies

  1. Absolutely fantastic. Exactly the sort of information I was looking for.

    Great stuff!
    Tarun

  2. Great stuff. It was really helpful.
    We were trying to inprocess hosting for ws http binding.
    We are not able to generate the contract and we get the ‘scheme already exists’ as you have rightly pointed out.

    Can you please guide about How do we create stub WCF service using the BizTalk WCF Service Publishing Wizard? Any help is appreciated. Thanks

  3. To add to the above question when we generated the stub hosted in IIS the cs file had only the data contract and did not have port specific methods. Were we missing something?

  4. Hi Sirish,

    I cover this extensively in the book, so pick that up😉

    What you might want to do is take your in-process hosted receive location, add a metadata behavior, and set the externalmetadatalocation attribute to an externally defined WSDL of your own making. This way you can define the messages and opereations that you want to associate to the in-proc receive location.

    It might take a few minutes to drum up the WSDL file, but it’s more flexible in the long run.

  5. Excellent article with well detailed examples.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: