Book Image

BizTalk Server 2010 Cookbook

By : Steef-Jan Wiggers
Book Image

BizTalk Server 2010 Cookbook

By: Steef-Jan Wiggers

Overview of this book

BizTalk enables the integration and managment of automated business processes within or across organizational boundaries. To build a solid BizTalk solution, deploy a robust environment, and keep it running smoothly you sometimes need to broaden your spectrum, explore all possibilities, and choose the best solution for your purpose. By following the recipes in this book you will gain required knowledge and succeed in your implementation. With BizTalk Server 2010 Cookbook, you can leverage and hone your skills. More than 50 recipes will guide you in implementing BizTalk solutions, setting up a robust and well performing BizTalk environment, and choosing the right solution for monitoring it. As a developer or administrator you greatly benefit from taking these recipes to work. In this book a developer and administrator will see how to deploy, build, and maintain a BizTalk environment. How to apply patterns for robust orchestrations, messaging and testing. Administrators will learn to set up an environment using Microsoft best practices and tools to deliver a robust, performing and durable BizTalk environment. Besides setting up their environments administrators can also decide through a number of recipes how to monitor and maintain the environment. A developer can contribute to a healthy environment by implementing instrumentation in artefacts, applying well suited pattern(s) and testing the solutions built.
Table of Contents (17 chapters)
BizTalk Server 2010 Cookbook
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Implementing a retry pattern in an orchestration


A challenging situation with a BizTalk orchestration can be when communication with the external system fails and we have no idea what to do next. You can, for instance, in a Send port, configure a number of tries before an error message is generated by BizTalk. In case there is no properly planned action, the message and orchestration both are suspended in the BizTalk Administration Console and cannot be resumed in a fashionable manner. Once the communication is restored, resuming messages may work, but messages sent from an external system will not connect with the corresponding orchestration. Resuming the orchestration could fail if it is waiting for a specific message type. What you could do in this situation is to implement a retry pattern. This pattern basically has some logic programmed into an orchestration that will suspend it so it can be resumed properly by an administrator.

Getting ready

Open Visual Studio 2010 to develop the parallel...