soap to proxy scenario Getting exception caught with cause error

[Former Member]

Hi Experts,

MY scenario is soap to proxy i am  getting below exception message in advanced engine configuration in ICO.

OAP: request message entering the adapter with user J2EE_GUEST

09/10/2014 11: 06: 03 346 XI Information Packaging (Bulk Mode) is not Enabled, Proceeding to the Normal Processing.

09/10/2014 11: 06: 03 346 XISOAP Information: Received an XI message for processing

09/10/2014 11: 06: 03 598 Error SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)

09/10/2014 11: 06: 03 598 Information SOAP: completed the processing

OAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)

09/10/2014 11: 06: 03 598 Information SOAP: completed the processing

09/10/2014 11: 06: 03 598 Information SOAP: response message to continuing 7477aafa-38da-11e4-beed-00000028af0a

09/10/2014 11: 06: 03 599 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)

09/10/2014 11: 06: 03 599 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)

payload is contains some  special charters in  which is in protiguse language

example.

• AWPJ SERV DE TERCERIZ and

dot is the special char

same payload while testing using sproxy tcode dot "•" is converting in " # "symbol and with out error its successfully updating the database in ECC.

while testing using the same payload using soap ui removing the dot symbol from the field its successfully processing  and updating the database.

is this interface is failing in PI level ? or ECC i am not getting dump in ecc.

is there any special character conversation in sap pi level.

where this message exactly failing is in PI level or in ECC level?

Help us find the solution.

[iaki_vila · Accepted solution]

Hi Ravinder,

From my point of view you have two options to face up this problem:

1. Try to change the charset enconding with SOAP adapter or module bean: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79f...

2. To check Do not use SOAP Envelope (this mean to wrap the the request with the SOAP envelope), in this way you will receive all the SOAP message in crude and later to try to do a java mapping/UDF to deal with this charset problem.

Regards.

[Former Member · Accepted solution]

Hi  inaki,

Thanks for your replay

1. Try to change the charset enconding with SOAP adapter or module bean:http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79f...

above changes are not working can you elaborate the  second option if have nay udf share with me .

Regards

Raviinder

[iaki_vila · Accepted solution]

Hi Ravinder,

When you mark the option Do not use SOAP envelope the adapter will not generate the SOAP envelope therefore you need to set an extra mapping in the Request to wrap the SOAP envelope. For example with XSL:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
    <xsl:template match="/">
        <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
            <SOAP:Header/>
            <SOAP:Body>
                <xsl:copy-of select="/"/>
            </SOAP:Body>
        </SOAP:Envelope>
    </xsl:template>
</xsl:stylesheet>

Later in the response you will have the SOAP envelope tags. (You can do a first try without java mapping only to see in the monitoring the response with the junk character).

When you determine the junk character you can try to use and to modify the next java mapping SAP PI - Deciphering apostrophes in XML - Process Integration - SCN Wiki to deal with your problem.

Hope this helps.

Regards.

[JaySchwendemann]

Are you able to get hands on the logs of the webservice provider? If so, there might be some more insights what's really going wrong there.

HTH

Cheers

Jens