Thursday, March 22, 2007

Port exception in orchestrations

How to handle transmission errors on a port in an orchestration ?!

I added a send port (FTP) to an orchestration and after the send port I updated a log. But the orchestration continued even the send port failed (i.e. FTP server down).

The solution was to add a scope shape including a generic exception handler, around the send port. But it did not work - the exception was newer through.

What I forgot was to change Delivery Notification on the send port to "Transmitted".

That did the trick :-)