on 01-06-2014 10:51 AM
Hi Uday,
As you said your scenario is "(ECC-PI-.NET system integration)" but you are trying to send message to PI system through SOAP UI instead of your .NET system. change the target URLwhich point to .Net system
Regards
Gagan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your URL seems ok. In SOAP UI, after importing WSDL, dig it till Request1.
Check if your request is sent to URL in this format from SOAP UI:
and check if your request is sent to URL in this format from SOAP UI:
http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=<Sender service>&receiverParty=&receiverService=&interface=<Sender SI>&interfaceNamespace=<name space>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Abhinav,
i have the same format as shown below
Regards
Uday
Hi Uday,
Could you please shared the error into AuditLog of adapter enginne
Kind regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Viana,
This is the audit log for the above message.
06.01.2014 17:07:14.696 | Information | Message was received by the messaging system. Protocol: XI URL: http://sndpips1:50200/MessagingSystem/receive/AFW/XI Credential (User): PIISPS1 |
06.01.2014 17:07:14.698 | Information | Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue |
06.01.2014 17:07:14.701 | Information | Message successfully put into the queue |
06.01.2014 17:07:14.702 | Information | The message was successfully retrieved from the request queue |
06.01.2014 17:07:14.702 | Information | Message status set to DLNG |
06.01.2014 17:07:14.703 | Information | Delivering to channel: CC_WS2WS_REC |
06.01.2014 17:07:14.703 | Information | MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean |
06.01.2014 17:07:14.703 | Information | XI packaging (bulk mode) is not enabled. Switching to normal processing.... |
06.01.2014 17:07:14.703 | Information | XISOAP: XI message received for processing |
06.01.2014 17:07:14.704 | Information | SOAP: Request message entering the adapter processing with user J2EE_GUEST |
06.01.2014 17:07:14.711 | Error | MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Error | SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Error | SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Information | SOAP: Continuing to response message e3b4647d-76c6-11e3-9bac-000001c8cd9a |
06.01.2014 17:07:14.711 | Information | SOAP: Processing completed |
06.01.2014 17:07:14.720 | Error | Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.724 | Error | Delivery of 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 errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .. Setting message to status failed |
06.01.2014 17:07:14.725 | Error | Message status set to FAIL |
Hi Mark,
Still i am facing the same problem. Let me explain my complete scenario so that you can provide me helpful inputs.
I am developing a mock (ws-pi-ws) scenario. I have taken target wsdl. I have imported target wsdl under external definitions and created service interface for target. At source side i have manually created DT, MT, SI for source system with the same fields in the target side. Later created 2 MM and a operation mapping. Later configured the end to end scenario with a soap CC at each side.
Request & Response transformations are correct in test tab of message mapping in ESR. Also configuration set up is correct when i test it from tools options in application tool bar in ID.
Ganerated wsdl from sender aggrement. Loaded it in SOAP UI 4.6.1 and selected HTTP end-point; authentication type preemptive. Provided username and password. When i hit the end point it throws the following error.
<!--see the documentation-->
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
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:78)
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:78)
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:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
---------------------------------------------------------------------------------------------------------------
The audit log in message monitoring of AE is as shown below
06.01.2014 17:07:14.696 | Information | Message was received by the messaging system. Protocol: XI URL:http://sndpips1:50200/MessagingSystem/receive/AFW/XI Credential (User): PIISPS1 |
06.01.2014 17:07:14.698 | Information | Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue |
06.01.2014 17:07:14.701 | Information | Message successfully put into the queue |
06.01.2014 17:07:14.702 | Information | The message was successfully retrieved from the request queue |
06.01.2014 17:07:14.702 | Information | Message status set to DLNG |
06.01.2014 17:07:14.703 | Information | Delivering to channel: CC_WS2WS_REC |
06.01.2014 17:07:14.703 | Information | MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean |
06.01.2014 17:07:14.703 | Information | XI packaging (bulk mode) is not enabled. Switching to normal processing.... |
06.01.2014 17:07:14.703 | Information | XISOAP: XI message received for processing |
06.01.2014 17:07:14.704 | Information | SOAP: Request message entering the adapter processing with user J2EE_GUEST |
06.01.2014 17:07:14.711 | Error | MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Error | SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Error | SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.711 | Information | SOAP: Continuing to response message e3b4647d-76c6-11e3-9bac-000001c8cd9a |
06.01.2014 17:07:14.711 | Information | SOAP: Processing completed |
06.01.2014 17:07:14.720 | Error | Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: . |
06.01.2014 17:07:14.724 | Error | Delivery of 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 errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .. Setting message to status failed |
06.01.2014 17:07:14.725 | Error | Message status set to FAIL |
Later rechecked the SAP_XI_APPL_SERV_USER role; target url and soap action but still the issue persists.
Note : Cannot see all the pipeline steps(1 step i can see)
Please share your ideas
Regards
Uday
Hi Uday,
As per the log you do not have issue is sender channel.
Hence you can test this scenario from RWB .
Probably issue is receiver channel and more specifically in soap action.
Do check the soap action from wsdl provided by dot net developer.
Soap action in nothing but the namespace followed by class name which must be present in dot net application.
Also this class name must present in wsdl which you are using in MM.
Do check this two parameter your issue will be resolved .
Hi Uday,
The scenario is web service -> PI -> web service.
Hope you have a SOAP Sender channel to accept the request. Having said that the SOAP URL used in the wsdl is wrong. The endpoint URL should be as below:
http://appserver:port/XISOAPAdapter/MessageServlet?channel=:Sender Business Service: Sender Soap Adapter
You cannot send a message directly to integration URL from SOAP UI.
-Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
Also i have tried with the following url
and also passed the username and password combination in the url.
In both the ways, i am getting the same error.
Regards
Uday
Hi Uday,
Abhinav answer applies to SOAP UI 4.5.1.
may i know which verison of SOAP UI ur using?
Message was edited by: mastan vali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Masthan,
I am using SOAP 4.5.0 and SOAP 4.6.1. I have set the parameter Authentication Type = Preemptive by selecting Sets global UIpreferences symbol in application toolbar -> select the check bax as shown below
Again i have reloaded the wsdl. Still i am facing the issue.
When i use the integration url wsdl, i am getting the above error. But if use use the wsdl generated from sender aggrement , i am getting the following error description.
<!--see the documentation-->
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: .
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
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:78)
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:78)
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:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.