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

Supporting dual initiating message exchange patterns


Back in Chapter 4, we looked at Message Exchange Patterns (MEP) and evaluated differences between them. We concluded that asynchronous patterns can be more service-oriented and loosely coupled than synchronous patterns. However, there are cases where you want a single business process to accommodate invocation by either mechanism. In certain scenarios, the caller has no interest in the outcome, but in other situations, the caller requires resolution about the service outcome. You could choose to build two distinct processes, which support each distinct MEP, but that is fairly inefficient and challenging to maintain. What if we want to build a BizTalk orchestration with the least amount of effort required that can be invoked either synchronously or asynchronously?

Building the BizTalk solution

In keeping with our "drug product safety" theme, this scenario works with a "product complaint" schema. A product complaint is typically an issue that...