Fault message issue

[maheswarareddykonda]

Hi All,

currently i am working on Proxy to Soap synchronous interface and working good.

and we are expecting Fault msg with exact error from web services server when we try fault cases(wrong data), but this is not working in PI.

when we tried to test in Soap ui tool, i could see fault msg with exact error and below are the ways we tried.

1.created Service interface with fault message type(here External definition used which provided by WS team) and used in Operational mapping.

2.we tried dummy interface also (without structure) in PI and tested with correct data and wrong data, correct data case working fine and wrong data case there is no fault msg is coming from receiver server.

Note:in Saop ui tool i could see fault msg, which mean web services team already done the code for fault msgs.

Please suggest me where is wrong.

Thanks & Regards,

Maheswarareddy

[iaki_vila · Accepted solution]

Hi Maheswareddy,

Please use the second parameter (XMBWS.NoSOAPIgnoreStatusCode) like this example:

Regards.

[maheswarareddykonda · Accepted solution]

Hi Inaki,

thanks for reply.

i have used module which you have shared and now i am able to get an fault msg but its seem always same error text like below.

<faultcode xmlns:a="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">a:InvalidSecurity</faultcode>

<faultstring xml:lang="en-GB">An error occurred when verifying security for the message.</faultstring>

and same data tested in soap ui , there its showing specific issue. like authentication issue and data issue on specific field..the same thing i am expecting in PI also

can you please correct me?

thanks again.

thanks & Regards,

Maheswarareddy

[iaki_vila · Accepted solution]

Hi Maheswareddy,

The error seems to be in your request. I think you SOAP endpoint expects a wsse authentication () in your SOAP header.

Have you get a right answer from SOAPui?.

Regards.

[maheswarareddykonda · Accepted solution]

Apologies for in correct update in previous msg ..

actually i done wrong way which is totally not related to that module.

thanks that module is working perfect ...over here i am getting small doubt, can you please confirm this is related to only soap channel or i can use where ever?

Thanks & Regards,

Maheswarareddy

[maheswarareddykonda · Accepted solution]

yeah that related to wsse and corrected thanks

[maheswarareddykonda · Accepted solution]

Hi Inaki,

i am re-opening the thread.

actually earlier i have tested dummy interface and fault msg are coming from receiver system, but now i just created the interface with structure(request, response and fault ) and have tested ..i am not getting any fault msgs when i tried wrong data.

i read few blogs soap adapter has limitations on fault msg's is it correct?

Please suggest me.

Thanks & Regards,

Maheswarareddy

[iaki_vila · Accepted solution]

Hi Maheswarareddy,

It's a weird thing. In the scenario that i used the parameter that i told you i need to do a XSL mapping and to use a dummy schema on the receiver side because the XML structures are different in both cases. Go to the monitoring and try to do a first mapping with XSL taking into account this double XML incoming.

Hope this helps.

Regards.

[maheswarareddykonda · Accepted solution]

Hi Inaki,

yeah both xml structures are little bit different and i was expecting mapping exception for fault mapping.

but its not even coming that fault msg from receiver.

and one more thing i tested data with correct one its working fine and the same payload changed with small data for one field which should carried correct data, then fault msg is not coming.

also deleted fault msg mapping in operational mapping , there is no help.

please suggest me.

Thanks,

Maheswarareddy

[iaki_vila · Accepted solution]

Hi,

but its not even coming that fault msg from receiver.

Are you sure?, have you checked the PI monitoring, i think that it is probably raising an exception. It has no sense that before worked and right now the message is not coming to PI.

From my point of view, may be someone has another technique, i use in the response first a XSL message to deal with the two types of messages and to generate a new one to be used on an follow message mapping.

It is primordial for you to figure out what is happen right with the fault messages. Pleas check message monitoring and communication channel monitoring.

Regards.

[maheswarareddykonda · Accepted solution]

Hi Inaki,

yes indeed, that technique is worth in case i get the fault msg.

yeah , i am sure there is no fauly msg and i could see only one log with error below.

SOAP: Processing completed
02.07.2015 12:12:06.658	Error	SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
02.07.2015 12:12:06.658	Information	SOAP: Continuing to response message 8e7e973c-20b3-11e5-c62d-0000185d0526
02.07.2015 12:12:06.663	Error	SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
02.07.2015 12:12:06.666	Error	MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
02.07.2015 12:12:06.670	Error	Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
02.07.2015 12:12:06.671	Error	Transmitting the message using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
02.07.2015 12:12:06.678	Error	Message status set to FAIL

and the same data tested in dummy interface , where i am using same channel and i am able to see fault msg.

and here is the Log viewer screen shot

Thanks,

Maheswarareddy

[maheswarareddykonda · Accepted solution]

Hi Inaki,

i am not sure why system behaving such a way..after reactivation the channel its working fine..

Thanks for your help

Thanks & Regards,

Maheswarareddy

[shiva_roy]

For the scenario , I feel it can be done since we can define the Fault message at both the O/B & inbound interfaces

Regards,

shiva