The current version of BizTalk (2013 R2) ships with hundreds of features like Exception Handling, and there are textbooks published which list tons of patterns making use of these features. It is practically impossible for an individual, or even an organization who implements BizTalk Server to take advantage of all of these features the way the features were meant to be used by the original designers of BizTalk, and even harder to use those features in a way that is ideal. The only way to learn how to use these features in the best possible way is through practice and lots and lots of experience.Art2link Corp. has been involved with BizTalk Server since its inception, working with different clients, different verticals, throughout the years providing feedback to Microsoft’s Product Team in the improvement and enhancements for this product. Having this kind of exposure allows us to have a more comprehensive understanding grasp of all the product’s features, and it allows us to provide a solution that more precisely matches our client’s needs, and the needs that we know will arise in the future.
In the following posts of this series we will talk about:
- What is Exception Handling?
- Types of Exception in BizTalk Server
- What happens if we don’t Handle BizTalk Exceptions?
- What is the best practice, per Microsoft?
- Case study
As with any other system there are many different ways to handle the exceptions, some better than others depending the case. Here we’ll talk about the best real practices for Exception Handling in BizTalk based on real cases. Regardless of the systems you are integrating these samples and practices will help you and your team to develop safer solutions and be at the top of the game for BizTalk Exception Handling.
Came back next week and find out what is the best way to avoid any unexpected crush in your system.