Book Image

SOA Patterns with BizTalk Server 2009

By : Richard Seroter
Book Image

SOA Patterns with BizTalk Server 2009

By: Richard Seroter

Overview of this book

SOA is about architecture, not products and SOA enables you to create better business processes faster than ever. While BizTalk Server 2009 is a powerful tool, by itself it cannot deliver long-lasting, agile solutions unless we actively apply tried and tested service-oriented principles. The current BizTalk Server books are all for the 2006 version and none of them specifically looks at how to map service-oriented principles and patterns to the BizTalk product. That's where this book fits in. In this book, we specifically investigate how to design and build service-oriented solutions using BizTalk Server 2009 as the host platform. This book extends your existing BizTalk knowledge to apply service-oriented thinking to classic BizTalk scenarios. We look at how to build the most reusable, flexible, and loosely-coupled solutions possible in the BizTalk environment. Along the way, we dive deeply into BizTalk Server's integration with Windows Communication Foundation, and see how to take advantage of the latest updates to the Microsoft platform. Chock full of dozens of demonstrations, this book walks through design considerations, development options, and strategies for maintaining production solutions.
Table of Contents (18 chapters)
SOA Patterns with BizTalk Server 2009
Credits
About the author
About the reviewers
Preface
Index

Choosing an endpoint address


It's great that we've talked about the important C (the contract) in the ABCs of WCF endpoints, but the story is far from complete. So far, we have a service definition completely devoid of transport information. That is, where does someone go to consume this service? The goal of the endpoint address is to:

  • Tell us the communication scheme

  • Tell us the location of the service

WCF provides a number of out-of-the-box communication schemes for accessing WCF services. These include options such as:

  • HTTP

  • TCP

  • MSMQ

When looking at a service URI such as https://rseroter:8081/VendorService/SecureVendorService.svc, what am I able to infer from this WCF address? First, I can see that I'm using an HTTP/S scheme in order to secure my HTTP transmission channel via SSL certificates. Next, I can tell that the domain hosting this service is called rseroter and uses port 8081 for the HTTP/S traffic. Finally, I can gather the path of the service that I wish to call.

We'll see shortly how...