SOAP Fault Error Details not going over to sender system

[Former Member]

Hi Gurus

We have external vendor provided WSDL (Producer) which is mapping to the PI WSDL (Consumer) for synchronous web service between an third party client application & external vendor.

External Vendor (WSDL) <--> PI <--> ThirdParty application (PI WSDL)

The synchronous call is requested by the third party application and external vendor sends a successful response back - the PI mapping handles teh request & response transformation successfully.

However, the SOAP Fault details on failure are not being passed over to Thirdparty application even though we can see the SOAP fault in MONI whenever there is an error encountered.

Wat do you think is the issue OR how can we make sure SOAP fault details are passed on to the Third paty applications as we do see it in PI that on error there is SOAP fault sent from External vendor - how do I make sure it gets passed on to the client application whnever there is no VALID response - as right now the client application just receives an error on failure - but no SOAP fault detals.

Please, kindly advice how we can make sure SOAP fault is transmitted back through PI as we can definitely fine the details in MONI.

Thank you,

Rithvik

[manoj_khavatkopp · Accepted solution]

Rithvik,

Well you need to use fault message type for handling this :

Br,

Manoj

[former_member190293]

Hi Rithvik!

In case of application fault there must be fault message type described in WSDL, which you can use in fault mapping for your synchronous interface.

If you talk about SOAP system fault, the only way I know is:

1. Switch off using SOAP Envelope in adapter settings (you will need to add SOAP Envelop to your request message and remove it in response message with java/xslt mapping).

2. Create your own "common" structure for response message including both normal response and fault structures with occurence 0..1. Thus, you'll get either response or fault part filled in response message. In further response mapping you can check which part exists.

3. Set "XMBWS.NoSOAPIgnoreStatusCode" parameter to "true" in order to ignore System fault and proceed in SOAP module's parameters.

Regards, Evgeniy.