Book description
Pro BizTalk 2006 is a high-end resource that is based on real feedback from BizTalk developers. Authors George Dunphy and Ahmed Metwally are well known within the BizTalk community, and here they cover topics not discussed in other books, like performance tuning, scalability, and administration. This book also features examples of specific, real-world implementations.
Table of contents
- Copyright
- Foreword
- About the Authors
- About the Technical Reviewers
- Acknowledgments
- Introduction
-
1. Readme.1st
-
1. BizTalk in the Enterprise
- 1.1. What Is in the Toolkit
-
1.2. New BizTalk Solution Checklist
- 1.2.1. What Are the Teams' Current Core Skill Sets? What Skill Sets Will the Team Need to Attain?
- 1.2.2. What Are the Project Timelines? Will the Team Be Using BizTalk Exclusively to Decrease Development Time?
- 1.2.3. Is There Enough in the Budget to Implement BizTalk?
- 1.2.4. How Many Servers Are Required to Implement a BizTalk Solution?
- 1.2.5. How Much Custom Code Are You and Your Team Willing to Create? Would You Rather Use Completely Out-of-the-Box Functionality?
- 1.2.6. Is BizTalk Suited for the Application in Question?
- 1.2.7. Will Every Transaction in the System Need Monitoring? Will the Tracked Data Need Saving for Archiving Purposes?
-
1. BizTalk in the Enterprise
- 2. Starting a New BizTalk Project
- 2. BizTalk Revealed
- 4. Pipelining and Components
- 5. Pipeline Component Best Practices and Examples
-
6. BizTalk Design Patterns and Practices
- 6.1. Implementing Dynamic Parallel Orchestrations
- 6.2. Handling Ordered Delivery
- 6.3. Building a Resequencing Aggregator
-
6.4. Editing and Resubmitting Suspended Messages
- 6.4.1. Strategy for Edit and Resubmit
- 6.4.2. Pulling Data from the Suspended Queue
- 6.4.3. Canonical Format
- 6.4.4. Clients for Editing the Message
- 6.4.5. Additional Workflow
- 6.4.6. Moving Correct Data Back into BizTalk
- 6.4.7. Sample Flows for Edit and Resubmit
- 6.4.8. Pseudo-Walkthrough to Perform Edits and Resubmits
-
6.5. Managing Exceptions in Orchestrations
- 6.5.1. The Exception Management Challenge
- 6.5.2. BizTalk Server 2006 Failed Message Routing As a Blueprint
- 6.5.3. Failed Orchestration Routing API for BizTalk 2006
- 6.5.4. Running the EAIProcess
- 6.5.5. Processing and Retrieving Messages and Exceptions from the Fault Message
- 6.5.6. Beyond the Next Horizon
- 7. What the Maestro Needs to Know: Advanced Orchestration Concepts
- 8. Playing By the Rules? Use the Business Rule Engine.
-
3. You Mean You Aren't a Developer?
-
9. BizTalk Server 2006 Operations
- 9.1. Configuration and Management
- 9.2. Scalability and High Availability
- 9.3. Maintaining the BizTalk Group
-
9.4. Disaster Recovery
- 9.4.1. How Does BizTalk Log Shipping Work?
- 9.4.2. Configuring the Destination System for Log Shipping
- 9.4.3. BizTalk Group Disaster Recovery Procedures
- 9.4.4. BizTalk Runtime Server Disaster Recovery Procedures
- 9.4.5. Restore Procedures for BAS Site and Database
- 9.4.6. Restore Procedures for BAM
- 9.4.7. Restore Procedures for the Base EDI Adapter
- 9.4.8. Other Disaster Recovery Tasks
- 9.4.9. Related Non-BizTalk Application Disaster Recovery Procedures
-
9. BizTalk Server 2006 Operations
- 10. Deploying and Managing BizTalk Applications
- 11. To Tune or Not to Tune? Nobody Should Ask That Question.
-
Bibliography
Product information
- Title: Pro BizTalk 2006
- Author(s):
- Release date: February 2008
- Publisher(s): Apress
- ISBN: 9781590596999
You might also like
book
Pro BizTalk 2009
A compendium of best practices and implementation wisdom, Pro BizTalk 2009 is based upon real feedback …
book
Professional BizTalk® Server 2006
This book provides insight into how industry experts have successfully architected, developed, and maintained Microsoft BizTalk …
book
First Steps: Developing BizTalk Applications
First Steps: Developing BizTalk Applications is a primer to most other introductory BizTalk books. If you …
book
CIO Wisdom II: More Best Practices
World-class IT leadership solutions from working CIOs: detailed, realistic, proven Every year, IT leadership becomes more …