Scenario:
We have a synchronous (RFC <--> PI <--> SOAP) interface and implemented a request-, response- as also a fault-mapping.
When the webservice throws a SOAP fault (incl. HTTP500) this will run through the fault mapping and will be sent to the ERP via RFC as application fault.
Issue:
In message monitoring the fault message is shown as "successful" message. That's ok. But at the same time the SOAP channel goes into error state in the channel monitoring. This raises an alert email.
Question:
How to avoid the SOAP channel to throw an error in channel monitoring, when the SOAP fault was handled? (It should go into error state, when the fault couldn't be handled, but shouldn't when a correct fault message could be mapped/created.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.