Interface Proxy to Soap

My problem is:
I have a interface Proxy to Soap Async, but the wsdl provided for vendor is sync and the return message is not important to me.
In Ack in the sxmb_moni, I have a message error:
com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Is there some way to ignore this return message from webservice?
Thanks,

Rosa,
I think problem is at your client's end. I had the sam error and in my case the object reference error was being sent from .net server.
We recommended client to change the structire of web service (wsdl) and issue was resolved.
Just try changing the structure of the web services and create & use a new wsdl and see what happens.
Also please refer the blog. They also had the similar issue.
Re: System Error in Message Monitoring while it shows checked flag in SXMB_MONI
Regards
Veeru
Edited by: viru srivastava on Nov 17, 2010 2:41 AM

Similar Messages

Webservice for proxy to SOAP adapter interface

Hi Experts,
we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?

we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL -
> yes that is possiable for only sender side as webservice because sender always consumer
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
No that is not possiable to import WSDl File In receiver agreement because receiver always Provider .
in ESR:
wsdl file ll be imported in External defination as external message.
in ID:
in receiver Comm.channel -> call the soap URL and Soap Action(not manadatary)

Error while invoking the ABAP Proxy via SOAP Adapter

Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath

> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

PROXY to SOAP ; HTTP403 error in PI 7.1

Hi team,
it was proxy to HTTP scenario. Receiver : webportal . We have chnged it to Proxy to SOAP ,due to HTTP does not support multi message generation . I have checked Do NOT USE SOAP Envelope in SOAP rcv channel. Pls find the config details.
Adapter Type: SOAP
Trans.protocal: HTTP
Mess.Protocal: SOAP1.1
Do not use SOAP envelope : Checked
Now Im getting error in RWB .
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Access denied"
I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
thnaks
Drumi.

Hello,
I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
The content type when Do Not Use SOAP Envelope is checked defaults to application/xml. To change it to the correct content type, use the MessageTransformBean for your requirement.
ProcessingSequence                         ModuleName           Type     ModuleKey
1          localejbs/AF_Modules/MessageTransformBean            LEB      0
2          sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean LEB      soap
Module Configuration
ModuleKey                ParameterName                ParameterValue
0                      Transform.ContentType          text/xml
For more info, see http://help.sap.com/saphelp_nwpi711/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
Check also if you are passing credentials in your Receiver.
Hope this helps
Mark

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

Error in Proxy to SOAP synchronous scenario

Hi Gurus,
Hope you are doing well. I have a Proxy to SOAP synchronous interface interacting with an external system (system outside the firewall/landscape of my company).
When I am trying to post the request message from XI, I am getting the following error.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
In the WSDL provided by the external application, i.e. receiver WSDL, there is no attribute/field with the name 'IncludeExceptionDetailInFaults' and there is no fault string defined.
Where is this error being thrown up? Is it a network/firewall error that XI is unable to determine?
Please provide an answer as soon as possible.
regards
Debansu

Hi,
i think it is the problem in the WSDL provider system, because it is throwing the Error with some string".NET",
do the below steps for investigating the issue
1)try pinging the URL provided in the WSDL from internet explorer.
2)if it is successfull, try to push one message from SOAP UI to by importing that WSDL, if you get any error then it is problem in the end system.
Thank You,
Madhav

Abap proxy 2 soap

Hi,
this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
I checked target url and soap action in receiver soap adapter, and those value is correct.
on sxmb_moni
i got NO_MAPPINGPROGRAM_FOUND
http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
and Applicatoin Error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
here is Sent message log on MDT.
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-08-29 13:25:37 Success Trying to put the message into the send queue.
2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
2006-08-29 13:25:37 Success The message status set to DLVD.
2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
here is Receive message log on MDT.
2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
2006-08-29 13:25:37 Success Message successfully put into the queue.
2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
2006-08-29 13:25:37 Success The message status set to DLNG.
2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
2006-08-29 13:25:37 Success SOAP: request message entering the adapter
2006-08-29 13:25:37 Success SOAP: completed the processing
2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i can see source data on sxmb_moni.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
<TITLE>46</TITLE>
<GUBUN />
<REQUESTOR>46</REQUESTOR>
<TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
</nr1:APPROVALREQ_SES_MT>
request message mapping of request
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
<args1>46</args1>
<args2>46</args2>
</ns1:ApprovalRequest>
I can not see any return value comming from target webservice on sxmb_moni.
request message mapping error on response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
payload of request message mapping of response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
please check what was my fault.
thanks
venjamin

Hi Bhavesh.
thanks for the note.,,
please look at the bottom of this content.
i can not see "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
is this happening something wrong? or is it normal log?
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
here is detail message log on MDT.
--SAP_512dbe91-372d-11db-b291-00145e483080_END
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
<sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'>
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>synchronous</sap:ProcessingMode>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
<sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
<sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
<sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
<sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
</sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
<sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
<sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
<sap:Engine type='IS'>is.00.xi0034</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
<sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body>
<sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'/></SOAP:Body></SOAP:Envelope>
--SAP_512dbe91-372d-11db-b291-00145e483080_END
content-id: [email protected]
content-type: application/xml
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
thanks
venjamin
Message was edited by: venjamin

Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
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: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

Problem Proxy to SOAP Synchronous

Hi Experts, I was looking for a solution to this problem, but I could not find the solution, I hope you can help me.
I have the scenario PROXY ==> PI ==> SOAP (Synchronus).
When the Web Service is ok, I have no problems, my problem is with the Fault Exception, because I tested it in SoapUI, and I'm getting this message.
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
         <faultcode>S:Server</faultcode>
         <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
         <detail>
            <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
            <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
               <message>Error al insertar Domicilio en servicio Empleado</message>
               <ns2:stackTrace>
                  <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                  <ns2:frame class="sun.reflect.GeneratedMethodAccessor267" line="unknown" method="invoke"/>
                  <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                  <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                  <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                  <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                  <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                  <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                  <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                  <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                  <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                  <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                  <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                  <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                  <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                  <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                  <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                  <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                  <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
               </ns2:stackTrace>
            </ns2:exception>
         </detail>
      </S:Fault>
   </S:Body>
</S:Envelope>
So, I was reading a lot of threads, those said to copy the structure, but it doest not work.
I tried to check the "Do Not Use SOAP Envolve", but when I did that I got this error.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type
When I unchecked I got this error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:Fault. Value</SAP:P3>
<SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:Fault. Values missing in queue context. Target XSD requires a~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I could never see the Fault Structure in PI and neither in Web Service Navigator.
Please, I need some help.
Thank you very much.
Regards

If I test it in Soap UI I get the Fault, and in WsNavigator I can see the FaultCode and FaultString as a message on the top of the page.
I do not know what more to do.
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
         <faultcode>S:Server</faultcode>
         <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
         <detail>
            <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
            <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
               <message>Error al insertar Domicilio en servicio Empleado</message>
               <ns2:stackTrace>
                  <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                  <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="native" method="invoke0"/>
                  <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="39" method="invoke"/>
                  <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                  <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                  <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                  <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                  <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                  <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                  <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                  <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                  <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                  <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                  <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                  <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                  <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                  <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                  <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                  <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                  <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                  <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                  <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                  <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                  <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                  <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
               </ns2:stackTrace>
            </ns2:exception>
         </detail>
      </S:Fault>
   </S:Body>
</S:Envelope>

"Configure Proxy in SOAP Receiver"

Hi ,
Can some one help in providing me the information regarding "Configuration of proxy in SOAP receiver adapter (PI 7.1).
Thanks ..

Hi Stefan,
I have my Proxy Values ,the Host and the Port ...even then i am facing some issues., I want to know are there any other details which needs to provided inorder to configure proxy ...(My receiver is a 3rd party Webservice outside the firewall.)
Do i need to check the conversion parameters.
Error:
SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: "*********************************". at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:Stack />
Edited by: Madhusree Nagalla on Oct 28, 2010 3:28 PM
Edited by: Madhusree Nagalla on Oct 28, 2010 3:29 PM

Proxy to SOAP Scenario

Hi,
I have a requirement where the scenario is Proxy to SOAP (synchronous) from SAP CRM to the third party system. On XI we have a web service which will be invoked to create a SOAP request and receive SOAP Response.
Can someone please tell the Step by Step procedure for this scenario and what all objects need to be created in IR and ID.
Thanks,
Vikas

Hi Vikas,
I think you are quite new to XI.
The IR objects need to be created for this scenario are listed below.
1. 2 data types one for request proxy(outbound) and the other one for response proxy(inbound) and 2 message types associating these two data types.
2. You need to import WSDL files (for Request and Response webservice schema) under the External Definitions Tab.
3. 2 message Interfaces one for outbound and the other one for inbound(both will be synchronous), select output message and input messages accordingly.
4. Two message mappings one from Proxy to webservice and the other one fron Websevice to proxy
5. One interface Mapping.
Activate all the IR objects when they are created.
ID objects need to be created for this scenario
1. Create a configuration scenario
2. Assign sender and receiver business systems to this configuration scenario from the Objects Tab.
(you can also create a business service, incase the business system is not defined in SLD)
3. Create 2 communication channels, one under each business system.
For exp: suppose the names of sender and receiver systems are SAP and Webservice respectively.
Create a communication channel for exp: proxy_sender for SAP system.
Attributes for communication channel Proxy_sender are:
Channel Name: Proxy_sender
Serveice: SAP (sender Busines system in your case)
Adapter type: XI(browse it from the list) and check the radio button sender.
Transport protocol: HTTP 1.0
Message protocol: XI 3.0
Adapter Engine: Integration server(if you are using any non central adapter engine then select the same from the list)
select the HTTP security depending on the requirement.
Create another communication channel for exp: SOAP_Receiver for webservice system.
Attributes of communication channel SOAP_Receiver are:
Channel Name: SOAP_Receiver
Serveice: Webservice(receiver Busines system in your case)
Adapter type: SOAP(browse it from the list) and check the radio button Receiver.
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter Engine: Integration server(if you are using any non central adapter engine then select the same from the list)
Target URL: Mention the URL of the server where the webservice is executed.
Configure the
Receiver Determination,Interface Determination,Sender Agreement and Receiver Agreement for this scenario.
Activate all the objects created under the configuration scenario from the change lists Tab.
I beleive it is good enough to start with, although I have not explained the configuration steps in details.You start the implementation, in case you have any doubts please post it.
Best Regards,
Nitin...

Proxy to soap : async

Hi
Wanted to understand if we have a async comm : proxy to soap and suppose the target system goes down while we transmit proxy data. If it is an async scenario ,it will error out in moni and an alert can be generated but this interface has to be again triggered from the source system ,SAP to send proxy data again ? is my understanding correct ?
wanted to understand in async scenario how can this be automated ? suppose target is down async scenario needs to be triggered again.
Thnx

aync proxy to SOAP -> if the target system is down, the message will come into PI and will be persisted.
By default the adapter engine tries to redeliver the message to the target 3 times. if after these default times it is unsuccessful it will go to error and will be persisted in PI. At any point when the target is up you can go to rwb and manually reprocess the message.
you can also control the redlivery - /people/shabarish.vijayakumar/blog/2010/03/31/did-you-know--delivery-attempts-customizable-per-communication-channel

401 Error Proxy to SOAP

Hi,
We have sync interface for Proxy to SOAP. This interface works fine when run once.
When we did volume testing, 10% of the messages ( randomly) failed with 401 Unauthorized & 503 Service not aviabale.
After researching we found a note 821026 which talks about the issue. We have done changes as per the note & inclease the connection Pool max to 100.
Please advice, if there is anything we can do as it is still failing with 401 & 503 in PI.
Regards

Hi All,
Thanks for reply. We have 3 PI Systems which calls the same Web service via SOAP ( Syn proxy-SOAP.
First we observed this error in one of the system & now it comes in all. The error is
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
The sequence of event is Inbound message from ECC looks good, the Mapping is OK. I see in response the red & the error is in Inbound of Response.
Below is the log in MDT
02.02.2012 18:12:03 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxxxpd312.r1-core.r1.xxx.net:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
02.02.2012 18:12:03 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
02.02.2012 18:12:03 Information Message successfully put into the queue.
02.02.2012 18:12:03 Information The message was successfully retrieved from the request queue.
02.02.2012 18:12:03 Information The message status was set to DLNG.
02.02.2012 18:12:03 Information Delivering to channel: CC_SOAP_Rcvr_PaymentVerification
02.02.2012 18:12:03 Information MP: entering1
02.02.2012 18:12:03 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
02.02.2012 18:12:03 Information SOAP: request message entering the adapter with user J2EE_GUEST
02.02.2012 18:12:18 Error SOAP: call failed: java.net.SocketTimeoutException: Read timed out
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error Adapter Framework caught exception: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out. Setting message to status failed.
SXMB Log from ECC . This is shown

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I am not sure if this is issue in calling adapter engine( while sedning to web service) or When the Data is being send to Proxy this issue comes in.
Ps: We have gone through many notes & increase the connection pool & max wait time.
Also we have increase the time out in SOAP adapter with no effect. BASIS is looking at SXMB_ADM Http paramterto increase but this was systems were working fine before that.
Now even one message is not flowing.
Thanks & please advice
I

Async proxy to soap messages to be processed like EOIO

Hi,
I have a proxy to soap interface. What I want is to route these message these message through one queue in IE level so that, these would be sent to the receiver in order. Also doing this confirm that at the AE level, they would be delivered in order?
I looked at the tuning parameter for eo_outbound_parallel with the reveiver id, but it is routing all the messages to the receiver system in one queue. but I want this only for one interface.
any ideas?
thanks.
Sri

This is what I have observed -
Asynchronous interfaces.
Maintain Order at Runtime checked in the interface determination.
It is an enhanced interface determination producing at the most 3 messages.
When the mapping produced just one message -
In RWB when I checked for the messages processed under integration engine, I found Quality of Service - EO.
At the adapter engine level also the quality of service is - EO
The converstion ID in this case is blank
When the mapping produced more than one message -
In RWB when I checked for the messages processed under integration engine, I found Quality of Service - EO.
At the adapter engine level also the quality of service is - EOIO
The converstion ID in this case is non blank. (this is different at different times. But all of the message generated at the same mapping split have the same value)
So what I understood is, only when there are multiple messages getting generated from the split mapping, only then the AE takes care that only these messages (generated at that instance) would be delivered in order.
Any other observations are welcome.
VJ

Interface Proxy to Soap

Similar Messages

Maybe you are looking for