RFC-SOAP(Fault MSG/Attachment)

[Former Member]

Hi,

Scenario is: RFC - XI - SOAP (SYNC)

Current version of XI: PI 7.0 (SP 13)

Web service sends response in plain XML. But, Fault message will be sent as attachment(text/XML).

Q1: How do I read the content of attachment in message mapping(fault message mapping)? Does this require adapter module development?

Q2:Web service sends (response) error text in fault message. I can only set RFC exception by mapping a constant based on error.

So, calling application would not have specifics of actual error description(received from webservice) except exception.

Q3: Is it a good idea to use ABAP proxy instead of RFC sender to solve the above issues?

Please help.

[Former Member]

Hi,

I think, using java mapping you can access the content of fault message attachment

instead of doing same in the custom adapter module.

Once you access the content then you can easily map the fault content.

Regards,

Rajendra

[former_member181985]

Rajendra,

we can not access the attachment in mapping.

@ mallik kancharla ,

May be we can use payloadswap bean, but I am not sure how it behaves in synchronous scenario.

Regds,

- Gujjeti.

[Former Member]

Web service sends "successful" response in plain XML(no attachment).

Only "fault message" will be in attachment.

So, if I use payloadswap bean then "successful" response message can not be read by XI (as it does not have attachment).

Please clarify.

[Former Member]

Another follow up question:

1. SOAP adapter is supposed to remove soap envelope/header in response payload even though I have checked "Do not use SOAP envelope" in conversion parameters.

So, I had to explicitly need to add simple XSL mapping to remove soap envelope/header.

2. How to capture "faultstring" in mapping(fault message mapping)?

3. In interface mapping(fault tab), there is no option to add multiple mapping programs. I need to add XSL mapping to remove soap envelope/header from fault response.

Following is sample fault message:

- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

- <soap:Body>

- <soap:Fault>

<faultcode>soap:Client</faultcode>

<faultstring>Operation policy forbids object creation. Parameter: requisition</faultstring>

- <detail>

<WebServiceFault xmlns="http://www.abc.com/ws/integration/toolkit/2005/07" />

</detail>

</soap:Fault>

</soap:Body>

</soap:Envelope>

[former_member181985]

I think ABAP proxy is much better..............