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

Exploring BizTalk's out of the box deployment


A developer builds a BizTalk solution and deploys it to his own BizTalk environment and tests it. As soon as he determines that his BizTalk application is finished enough, he can export it from the BizTalk Administration Console. An MSI and binding file (XML) are extracted and can be viewed as a complete "backup" of the application. The MSI and binding files can be separate or binding files are included within the MSI. Both can be used to install an application in another BizTalk environment. The administrator does not have to rely on Visual Studio to deploy straight from the code as the ability to create an MSI is offered through the BizTalk Management Console.

The drawback with MSI is that it represents a certain version, and when outdated an extraction of the right version is required. Deployments to different stages (test, acceptance, and production) are manual tasks and require some discipline by administrators. Besides that, versioning is...