Tony
2009-07-20 09:12:01 UTC
I'm an AX dev working with a BizTalk engineer setting up integration between
AX and a 3rd-party application for a client.
I have created an AIF service to receive requests for creating ProjTable
records. The interface works fine except when message validation fails and an
error response is sent back to BizTalk. The BizTalk engineer was expecting a
response message containing the error details, but what actually happens on
BizTalk is the message ends up in the Application Event log. The engineer
says he can implement exception handling in the BizTalk orchestration to trap
the excepion, but this only occurs after the message has gone through the
standard number of resubmits.
What I'm wanting to know is what is the recommended way for handling AIF
exceptions in BizTalk? Ideally we would like the failed response message to
act the same as the success response ie a message that the orchestration can
process and feed back to the initiating system or is exception handling the
only way to do this?
Regards,
Tony
AX and a 3rd-party application for a client.
I have created an AIF service to receive requests for creating ProjTable
records. The interface works fine except when message validation fails and an
error response is sent back to BizTalk. The BizTalk engineer was expecting a
response message containing the error details, but what actually happens on
BizTalk is the message ends up in the Application Event log. The engineer
says he can implement exception handling in the BizTalk orchestration to trap
the excepion, but this only occurs after the message has gone through the
standard number of resubmits.
What I'm wanting to know is what is the recommended way for handling AIF
exceptions in BizTalk? Ideally we would like the failed response message to
act the same as the success response ie a message that the orchestration can
process and feed back to the initiating system or is exception handling the
only way to do this?
Regards,
Tony