Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Best way to handle exception › Re: Best way to handle exception
Hi Nick,
Thank you very much to take intrest in my problem.
I have put tarminate shape in CATCH EXCEPTION block itself. Following is the design my orchestration.
1. Receive file from local (Get XML)
2. Map some other schema
3. Start scope -> (withing scope ) send FTP
4. CATCH EXCEPTION -> Send to local folder using SEND shape not expression shape -> trerminate shape
5. catch exception and scope block is over
6 send that file to Local Processed folder. ( Only execute if file uploaded on FTP successfully )
7. Rename one local file Using Expression shape. (If file not exist then catch exception and terminate instance successfully)
I need above flow.
but i just show the message execution flow in HAT report. Below is the flow.
1. Receive file from local (Get XML)
2. Map some other schema
3. Start scope -> (withing scope ) send FTP
4 send that file to Local “Processed” folder. ( Only execute if file uploaded on FTP successfully )
5. CATCH EXCEPTION -> Send to local folder using SEND shape -> trerminate shape
6. catch exception and scope block is over
I dont know why the flow execute unorderly while my “PROCESSED” Folder is after scope and catch exception block.
but it execute first and then flow goes to catch block.
Regards,
– Dhaval M