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>

Similar Messages

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

Proxy to soap synchronous

Hi.
In my synch proxy to soap scenario, facing the error while testing web service from altova spy.
Err thrown after i send request is "<RCVR Deter> "MESSAGE_INCOMPLETE"
This is when i use WSDL generated from my ID.
When i use wsdl given from client it doesnt post at all, with message code (500).
Scanned sdn and asked everyone i cud, but cudnt hit any solution.
I noticed following things in WSDL given by client,
1. URL within WSDL's adress tag, when pasted in browser doesnt opens WSDL or any web page rather says "Welcome to axis.."
2,When added ?wsdl at the end of the url, the wsdl can be seen.(so using URL with "?wsdl" as my target URL in soap receiver ID, is approach right??)
3.In WSDL from client has, <wsdl:operation name="XXX" parameterOrder="XXXXX">
what ideally shud be approach when soap is at receiver end.
Also, Great confusions about These::
1. URL in target url in soap receiver
2.URL of file location, while sending request. (shud b wsdl file saved in desktop, or url of wsdl )
3.soap end point and action (what if, when no action is there in wsdl) when changing soap parameters
4.In moni and also in altova getting err <Receiver determintaion> Message_incomplete
5.when to use wsdl generated from ID and when to use wsdl provided from client.
I am badly stuck in this scenario. Couldnt find any way out, at the same time its v v critical object.
wud be thankful if someone can help me in sorting out this..
thanks

5.when to use wsdl generated from ID and when to use wsdl provided from client.
This should be your first question
Use wsdl generated by ID in case of soap sender scenarion and use wsdl from client in case your scenario is soap receiver.
This is when i use WSDL generated from my ID.
For the receiver soap scenario, you dont have to generate wsdl in ID. Use the wsdl given by receiver.
When added ?wsdl at the end of the url, the wsdl can be seen
If your scenarion could work after adding this, then there is nothing wrong in this approach.
1. URL in target url in soap receiver
Use the URL provided by the receiver system. The same url is present in the wsdl file that receiver provide to you.
2.URL of file location, while sending request. (shud b wsdl file saved in desktop, or url of wsdl )
What do you mean by this? For a soap receiver channel, you only need the URL and use the wsdl provided by receiver.
3.soap end point and action (what if, when no action is there in wsdl) when changing soap parameters
Action is not compulsary. Just use the wsdl provided by client and check whether it contains <action> tag or not. If it has, then only provide the action.
4.In moni and also in altova getting err <Receiver determintaion> Message_incomplete
Your case is of soap receiver. You should not send messge from Altova to XI in this case.
Regards,
Prateek

Scenario proxy to soap synchronous with external definitions

Hi all,
I have a problem with my scenario.
In development environment all is working fine, but when I have transported to preproduction environment and we have executed my scenario I have the following error:
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://geisiedes.endesa.es/WSRespuesta/WsRespuestaSIE.asmx/EnviarRespuestaNocturnaWF.</SAP:AdditionalText>
<SAP:Stack />
I attach the receiver communication channel configuration.(cc_config.jpg)
I changed the target URL in the receiver channel, with the preproduction machine, but I didn't change the sopa action because is define in the wsdl ( soap_action.jpg).
I have othe external definitions for preproduction environmet but its contect is different to external definitions in development change the reference to machine where geisiepre instead geiseides.
Whe I import this external definitions I lose the configuration in messages mappings.
How can I solve this problem? Is mandatory to have the same external definitions in the three environments??
Thanks and best regards
Mónica

Hi Monica,
I normally use the all the tag content in the SOAPAction tag, but you can try with EnviarRespuestaNocturnaPC in the SOAP receiver communication channel.
Have you tried to test your wsdl endpoint with SOAPui?, you can get sometimes valuable information about how design/configure in PI and if the request is identical in PI and in SOAPui.
Regards.

Proxy to SOAP in PI 7.1

Hi Experts
I have requirement for Proxy to SOAP (Synchronous) and it needs a BPM to get the response from SOAP and post to the Proxy
Can any send the Prototype
Thanks
PR

BPM design:
Receive(Async From Proxy) -
> SyncSend(To SOAP) ---> Send(Async from BPM to Proxy)
you need to have:
1) 1 OB Async SI for SAP ---> BPM.......1 ABS Async SI to receive the SAP message into BPM.....message in both the SIs is the Proxy structure
2) 1 ABS Sync SI for BPM <---> SOAP ...... 1 IN Sync SI at the SOAP side
3) 1 ABS Async SI for BPM----> Proxy.......1 IN Async SI at the SAP end....message will be the Proxy structure.
You may need:
1 OM for BPM <---> SOAP flow
1 OM for BPM ---> Proxy....
Have you opened one more thread with the same requirement??
Regards,
Abhishek.

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...

Webservice-(Proxy to Soap)

Hi All,
I am having a requirement of Proxy to Soap synchronous scenario.
In that Client has given three webservices to connect 3rd party systems.
1.Authentication information (seperate)
2. Request
3. Response
I skipped the first webservice , as we can use the authentication option in communication channel.
Please let me know, any further settings has to done in client side or in PI side for skipping this authentication webservice.
Thanks,
Karthikeyan.

authentication can always be provided in the SOAP CC.
So you should be fine.
Additional Reference - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

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.

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

Synchronous Scenario SOAP to Proxy and Proxy to SOAP

Hi Sdn,
I am new to Synchronous Scenario.
Third party will send SOAP message requesting some information from SAP.
SOAP - > PI -> Proxy SAP
they are expecting a response Proxy - > PI -> SOAP.
Could you please let me know how to design teh Synchronous Scenario in PI .
Thanks

> Create DT and respective MT for Request and Response.
> Create Service Interfaces with Synchronous mode with respective MT's.
> Create Two separate MM with respective Request and Response MT's.
> Create Operation Mapping and call both Request and Response Mappings in it.
> Complete the Configuration part considering Sender SOAP and Receiver ECC Services.
> Configure CC with required parameters in Sender SOAP CC and Receiver XI CC.
> Generate wsdl from Sender agreement and save it as a local file.
> Use SOAP UI or any available Tool for testing purpose. Import the generated wsdl, provide input data and execute the test.
> If you are comfortable with expected result, deliver wsdl to the Sender Party.
> For Inbound Proxy, you can refer initial replies.
Hope it helps.!
Regards,
Sunil

Java Proxy - XI - RFC Synchronous Scenario OUTBINDING Problem.

Java Proxy -> XI -> RFC Synchronous Scenario. Problem
Hi,
 I'm doing a Java Proxy -> XI -> RFC Syncronous Scenario.
 A Java Server Socket is running as a Demon. When a client make a request to the Java Server Socket, this one call Java Proxy Client and set up the parameters.
 The first time that execute the scenario it works perfectly but no the next one and so on.
 The error when I check the monitor (TCODE: SXMB_MONI) is in PLSRV_OUTBOUND_BINDING.
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">no outbound binding found.</Trace>
<Trace level="1" type="T">No standard agreement found for , DES210_DEV, , JPX_DEV, urn:servipago:SERVIPAGO_SAP_02, mi_os_t1</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
And it has sense, because my scenario doesn't begin with the execution of FM (RFC).
A Hint, my services in the first try are:
 Sender Service: JPX_DEV (Java Proxy Client)
 Receiver Service: DES210_DEV (R/3 4.6C)
But the second try and so on the services that I saw in the monitor are:
 Sender Service: DES210_DEV (R/3 4.6C)
 Receiver Service: JPX_DEV (Java Proxy Client)
I can't understand why they swich each other.
Any idea?

Hi,
Outbound binding problem is because of Reciever Determination/Agreement is not activated or refreshed correctly.
Try to recreate or refresh and activate it. Then check it.
also do the cache refresh in SXI_CACHE.
Also in go to Integration Builder(XI home page)->Administration->Cache Overview and do all the cache refresh.
Hope this helps
Regards,
Moorthy

SOAP Synchronous messages

Hi experts,
I am testing SOAP synchronous messages. this is sender is SOAP receiver is ABAP proxy.
while testing if the message is successfully processed, i am not able to see the message details in SXMB_MONI.
but if any errors are processed i am able to see the error message.
Here my question is for synchronous interface can we see the sucessfull messages in SXMB_MONI.
thanks
Srinvas

HI Srinvas,
-->Recheck your entire scenarios once again if the process flow involves the Integration Engine definately the messages should be visible in the SXMB_MONI.
-->So you are inserting the Record into db table using the ABAP server proxy.......
-->I think there may not be any problems in the configuration of INtegration Engine, SXMB_ADM since you can view the error messages.
Thanks

ABAP-Proxy to SOAP: Error in SOAP Adapter

Hi!
I would like to implement ABAP-Proxy to SOAP scenario.
Unfortunately my SOAP receiver channnel has the following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Furthermore the call of /sap/bc/soap/rfc of business system B is erroneous
http://<server system B>:8000/sap/bc/soap/rfc
Here I get the error: HTTP 500 Internal Server error
Can some one help me to solve this problem?
Thank you very much!
regards
Holger

Hi,
Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
If at all you are using the SAP webservice, the wsdl link should be.
http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
The target url you will be able to see in the wsdl itself also
amit

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

Proxy to SOAP Scenario, payload with the SOAP envelops

Hi ,
We have Scenario like Proxy to SOAP,As per Business requirement they are asking payload with ENVELOP . Like below message
================================================================
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
 <SOAP-ENV:Header>
 <nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
 <nseps:to>
 <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
 </nseps:to>
 <nseps:from>
 <nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
 </nseps:from>
 </nseps:endpoints>
 <nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
 <nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
 <nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
 <nsprop:topic>CostObjectInformation</nsprop:topic>
 </nsprop:properties>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
//Payload of the message to be added here.
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I am trying out this in XSLT, but I am not sure how to add the SOAP Envelops and these Envelops are Static.
Can someone help me out in this.
Joe

But if you look at the SOAP Envelop Structure below it is not XI generated SOAP Envelop. IBX (3rd party) has its own standards, so XI has to Produce the SOAP Envelop according to their standards.
I have created the XSD with SOAP Envelop stucture with what ever structure 3rd party wants, but the problem is when Creating the SOPA Envelp tag, where it has a ":" where its not allowing me to create the valid XSD. And at the same time 3rd party is not in position to give us even WSDL file and we are not using Webservice call and they are not able to provide the XSD with SOAP envelop structure.
I thought of going for XSLT and started doing as well with what ever XSD 3rd party has provided, which does not have the SOAP Envelop structure and has only payload XSD structure.
80% of the SOAP Envelop structure is Static, it does not change. Only 2 fields keeps changing. IS there any solution that we can create XSD with the SOAP structure with Special Character ": "or is there any way in doing in XSLT.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">
<SOAP-ENV:Header>
<nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">
<nseps:to>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:to>
<nseps:from>
<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>
</nseps:from>
</nseps:endpoints>
<nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">
<nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>
<nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>
<nsprop:topic>CostObjectInformation</nsprop:topic>
</nsprop:properties>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
its a high priority issue.
Thanks in Advance.
Joe.

Problem Proxy to SOAP Synchronous

Similar Messages

Maybe you are looking for