SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Hi All,
I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
Please suggest what will be possible way out to resolve this issue.
Thanks,
Priya Ranjan

Dear Priya
Have you configured Fault Message for this scenario.
This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
Sourabh

Similar Messages

SOAP: response message contains an error Application/UNKNOWN/APPLICATION

Hi,
My scenario is Proxy>Soap>WS. When I tested proxy using SPROXY,the web service call is working fine and I am getting response. However, when I call proxy in the the program, I am getting "SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault" in adapter engine. I have gone through many similar posts in SDN but did not help.
Thanks for your help.

Thanks. I used SOAPUI outside SAP and it works perfectly fine. Even in SAP, it works fine when using Sproxy. Here is the error from adapter engine:
2010-06-24 12:59:34     Success     SOAP: continued from request message 6600174c-8a22-613e-e100-000018280c11
2010-06-24 12:59:34     Error     SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2010-06-24 12:59:34     Success     SOAP: response message leaving the adapter
2010-06-24 12:59:34     Success     MP: Leaving module processor
2010-06-24 12:59:34     Success     Application attempting to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
2010-06-24 12:59:34     Success     Trying to put the message into the send queue.
2010-06-24 12:59:34     Success     The response message for message 6600174c-8a22-613e-e100-000018280c11(INBOUND) was successfully transmitted to the calling application.
2010-06-24 12:59:34     Success     The message status set to DLVD.
2010-06-24 12:59:34     Success     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.

SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCE

Hi ,
I am getting below error in SOAP reciever channel.
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 XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started. at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor501_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2662_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.GeneratedMethodAccessor326_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy114_10002.process(Unknown Source) at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

Hi,
Can you please elaborate more on your problem.
Regards,
Raghu.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
Scenario: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
SOAP Receiver adaptor.
Target URL http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
SOAP Action http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the sender soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

SOAP: response message contains an error

Hi,
I send a message by PI to a service and I get the following message:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation SETCOMPANYFIELDVALUERequest
The scenario that I use is a RFC --> PI --> SOAP. The WSDL looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:DefaultNamespace" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:DefaultNamespace" xmlns:intf="urn:DefaultNamespace" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:message name="SETCOMPANYFIELDVALUERequest">
<wsdl:part name="COMPANYNAME1" type="xsd:string"/>
<wsdl:part name="COMPANYNAME2" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="SETCOMPANYFIELDVALUEResponse">
<wsdl:part name="SETCOMPANYFIELDVALUEReturn" type="xsd:anyType"/>
</wsdl:message>
<wsdl:portType name="AppLSDataSync">
<wsdl:operation name="SETCOMPANYFIELDVALUE" parameterOrder="COMPANYNAME1 COMPANYNAME2">
 <wsdl:input message="intf:SETCOMPANYFIELDVALUERequest" name="SETCOMPANYFIELDVALUERequest"/>
 <wsdl:output message="intf:SETCOMPANYFIELDVALUEResponse" name="SETCOMPANYFIELDVALUEResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DominoSoapBinding" type="intf:AppLSDataSync">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="SETCOMPANYFIELDVALUE">
 <wsdlsoap:operation soapAction="SETCOMPANYFIELDVALUE"/>
 <wsdl:input name="SETCOMPANYFIELDVALUERequest">
 <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DefaultNamespace" use="encoded"/>
 </wsdl:input>
 <wsdl:output name="SETCOMPANYFIELDVALUEResponse">
 <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DefaultNamespace" use="encoded"/>
 </wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AppLSDataSyncService">
<wsdl:port binding="intf:DominoSoapBinding" name="Domino">
 <wsdlsoap:address location="http://localhost"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
When I send the same message using the WebServiceNavigator everything is working fine.
The WSDL that I have imported into PI is the same that is available that I use calling by the WSNavigator.
Anyone an Idea?
Thanks Ron

HI
WSDL is having some problem
When you imported this wsdl how many messages does it show. Check weather it is having SETCOMPANYFIELDVALUE request and response. you can check the messages carried in a wsdl using the messages tab in external definition.
Thanks

Response message contains an error

Hi Experts,
i have a idoc to soap scenario. i am able to send idoc to soap adapter. but at receiver communication channel am getting following error : response message contains an error XIServer/UNKNOWN/ADAPTER/_JAVA_EXCEPTION. Parsing ERROR.ORG.XML.SAXParselException. Premature end of file.
Pls suggest

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

SOAP response message error

Hi,
We have a scenario where in we perform a synchronous send from a BPM and post the request to a url using a SOAP receiver channel.
When we test the scenario,the message fails in PI with the following error "com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"But when we try to test the same in SOAPUI by using the same payload,we do not have any issues in getting the response back.
Please could anyone advise on what could be the issue.
Thanks and Regards,
Induja

>
Induja Ramesh wrote:
> Resolved.
How?

WSRM Adapter replaced with soap in PO7.4. Getting error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"

Hello All,
We have scenario proxy->pi->webservice. In older versions of PI system they used wsrm adapter at receiver side and it's working fine.
Receiver interface is asynchronous. So no response structute is present and receiver service is business component(since receiver is a third party).
During migration, we have replaced the receiver adapter with SOAP adapter and used message protocol as SOAP 1.1 but the message is failing and in communication channel it is showing error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error". In this case the receiver interface is stateless xi 3.0 compatible(re using the old), after changing it to just stateless also issue persists.
In target url field if i prefix the url with "http" then above mentioned error is occurring otherwise if i use the hostname:port/path.. then it is giving error
"soap: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: Unsupported protocol". So maintaing the url as http://hostname:port/pat.....
As in old channel wsrm channel there is no userid and password, i haven't given any userid/pwd in receiver channel.
used the bean sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean with parameters
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
and
xmbws.No SOAPIgnoreStatus = true
but not successful.
Please help me. I got stcuk here.

Hello Jannus,
The connectivity is working fine. Network team has confirmed it. I doubt that any strucutre(header) difference might be present in message when sending with wsrm adapter compared to sending with soap adapter.
Please let me know the exact difference between soap and wsrm functionality in receiving end.
By considering the structure issue, i have checked the "do not use soap envelope" check box, then i got error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type"
Then i used message transform bean, but not successful.
Regards,
Ch.Venkat.

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Need to get SOAP request and SOAP response message.

Hi All,
I need to know that how can I get the SOAP request and SOAP response message. Now I am using WSDL2Java tool from Axis to generate the stub classes (such as ServiceLocator, SoapBindingStub, and soapPort ) and applying the classes to make the SOAP request. I have seen the solution for getting the SOAP request with Dynamic invocation interface (DII) style (http://mail-archives.apache.org/mod_mbox/ws-soap-user/200310.mbox/%[email protected]%3e), but not Static stub like what I did. Could anyone suggest me how to do it please ( I can't run tcpcom on the linux server, because x-window is not allowed to install ). Thank you for any help in advance.

You can try writing a client-side handler.
Handler gets called before the actual request is sent, and you can get the SOAP
message in it.
You have to deploy the handler in client-config.wsdd.
Handler is just like Servlet Filter.
I think there might be a simpler solution, but I dont know.

An email can't send "server response: Message contains spam...

One of my email accounts can’t send an email.. And the message came up
“Server response: Message contains spam or virus or sender is blocked: field32_1e2afb1a2cd02"
It says to select a different out going server..
Have I done something wrong, or is there a setting I need to change?
Thank you

Hi
Could you please confirm if the issue was resolved or needs further assistance?

Handling/Mapping a SOAP response message back to the RFC request Message

Hi
I was wondering if you could kindly offer some advice on how to handle the SOAP response back to an RFC in a RFC>SOAP>RFC.Response scenario. When executing an RFC function module that triggers a message to XI, the outbound message seems to process successfully, however, there is an error in the response message. I am not sure how to map the response back to the function module response message because it looks like the response payload is empty. It is also strange that the interface seems to run in synchronous mode despite being configured as an asynchronous interface. If it ran in asynchronous mode, there would not be a problem because we actually do not need a response back. The interface also runs perfectly when executing it from the Runtime Workbench, and it also runs in asynchronous mode as it should.
I would really appreciate any suggestions on how to solve this problem.
Thank you,
Brendon

Hi Reyaz,
This is actually an RFC-->SOAP scenario where the message structure of the source and target systems are different. We don't actually need a reponse back from the SOAP system. I was wondering if you perhaps know how we can cancel the Response response back to the requestor or at leaset map the SOAP response back?
The interface runs perfectly in asynchronous mode when executing it from the Runtime Workbench in the test section, but it runs in synchronous mode for some reason when executing the RFC function call in SAP.
Thank you,
Brendon

SOAP Response Message Capture in PI 7.1

Hi
I am working on Proxy to SOAP scenario and web service is synchronous to the external vendor,
ECC Sends a message to External Vendor by using the Web service(ClaimSearch Request Proxy) and would be receiving the response back from the External vendor by SOAP
I want to capture the SOAP response and send it to ECC by different proxy (ClaimSearch Response) proxy,
Do I need to use BPM to capture the response and sends it across to the ECC
Please suggest how can I capture the SOAP response and send it to ECC,
Thanks a lot in advance
PR

Hi!
If your scenario is completely synchronous the sending proxy expects a response.
If your scenario is asynch Proxy to synch SOAP, you can use the so-called asynch-synch bridge in BPM to achieve what you need.
1. asynch send ECC Proxy to XI/PI BPM
2. In BPM mapping and synch send XI/PI to SOAP Receiver
3. In BPM synch receive of SOAP response
4. in BPM decision which ECC Proxy is to be called asynchrobously
5. if neccessary mapping
6. asynch send response to ECC Proxy
You can have a look at the process patterns delivered by SAP and search for synch/asynch resp. asynch/synch bridge in SDN and/or help.sap,com
Hope this helps!
Regards,
Volker

Soap response message encryption using integration broker

hi gurus,
i have a requirement that to send encrypted soap response to a third pary system. so for testing purpose i am using soapui tool. i am able to encrypt request message and i am getting proper response from peoplsoft but its not in encrpting formate. so can any one suggest me is there any thing setting i have to do with for encrypted response.
i implemented the encryption on service operation level . as according to peoplebook if request is cming in encrypted formate then response ll also return in encrypted formate. i am using peopletool 8.52.
so kindly suggest me any solution

Hi,
Can you please elaborate more on your problem.
Regards,
Raghu.

SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Similar Messages

Maybe you are looking for