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

Chaining orchestrations using business rules


In Chapter 4, we talked about how to chain orchestrations together. The simplest way to do so (from a developer's perspective) is to use the Start Orchestration or Call Orchestration shapes and explicitly invoke one orchestration from another. While this strategy is easy to develop and allows for transfer of more than just message data (such as variables, ports), it's also a very tightly-coupled and inflexible way to connect stages of a business process. Ideally, you should pursue a route of Message Box direct binding which enables fully encapsulated, reusable orchestrations that can be invoked by a wide number of clients (for example, services or other orchestrations).

What if your business process consists of a number of discrete steps that are subject to change over time? That is, let's assume a process by which an inbound "adverse event" must pass through a set of business logic and human review stages prior to commitment into the enterprise...