Exception handlin in BizTalk: It is most important point in BizTalk to handing exception. If we don’t apply exception handling in our BizTalk application then when ever message failed in processing then its suspend and store in BizTalk Message box and availabe in suspended instance in BizTalk admin console. It will create heavy cost for BizTalk performance as well as production support activity.
Here I say that If exception is not handle proper way then it will create problem for BizTalk Performance. for this we need to understand some activity related to message box database (BizTalkMsgDb). As we know every message stored at message box database and process. And Message box db deletes the message when it successfully send. So when message failed and availabe at suspended instance in admin console, then it stored in database and will not be deleted untill unless we terminate instance. BizTalkMsgDb size is fixed mostaly with 4 GB.
There are two way to handle exception
- ESB Management Portal
- Create custom pipeline or orchestration to track the exception and send alert.
How to apply Exception handling on BizTalk Application
- Exception Handling at port: We can handle exception at port level through Enable Routing failed meesage check box.
- Exception Handling in orchestration through custom coding in catch block.
For more info about how to handle exception at BizTalk Port level, you can refer to below reference: