HTTP to SOAP scenario error
Hi guys,
I have developed an HTTP to SOAP scenario, in order to invoke a Web Service.
I am trying to test the scenario by using an HTTP client.
However, I am getting the following message, in the result:
Result:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Pipeline specified in URL attribute (type) not existing</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code><SAP:P1>/sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=++++&sap-client=100&sap-language=EN</SAP:P1><SAP:P2>ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS</SAP:P2><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Pipeline ID ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&amp;interface=GetStockQuote_Sync_OB&amp;service=HTML_Service&amp;party=&amp;agency=&amp;scheme=&amp;QOS=BE&amp;sap-user=xiappluser&amp;sap-password=++++&amp;sap-client=100&amp;sap-language=EN)
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Do you have any ideas?
Also, I am not able to see in SXMB_MONI the messages that are generated.
This is only possible in Message Monitoring in RWB.
Thank you
Evaggelos
Hi Evaggelos,
The URL you used to generate the WSDL for your webservice is wrong:
URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=+++++&sap-client=100&sap-language=EN
It should be of the type:
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
Thanks,
Varun
Similar Messages
-
Hi guys,
We have developed an HTTP to SOAP scenario, where XI acts as the WS client in order to call an already published WS.
When we are testing the scenario through RWB's interface (Component Monitoring --> Integration Server --> Integration Engine --> Self-Test Tab), we get error in SXMB_MONI.
The error is found in receiver SOAP adapter.
In Communication Channel Monitoring, we get the error "request entering", "call failed". The Message Id does not have a link in order to see the Audit Log.
In SXMB_MONI, the error in SOAP header is the following :
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.net.NoRouteToHostException: No route to host: connect</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
Our network does not use a proxy server, the Web Service hostname responds when we ping it from CMD.
Also, the WS works fine when testing it from Web.
We tried to play around with "Target URL" and "SOAP Action" parameters in receiver SOAP Com. Channel, but error remains the same.
Any ideas ??
EvaggelosWhen I am testing the url : http://fmgralxi01:50000/XISOAPAdapter/MessageServlet?channel=:StockQuoteService:Sender_SOAP
I get :
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#16 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
ModuleProcessorRemote not instantiated
As username: xiappluser -
HTTP to SOAP scenario, help needed.
Hi friendz,
I am tyring to do <b>HTTP 2 Soap scenario</b>, so can any one tell me how to download <b>"wsdl" file </b>
i know how to import an existing <b>wsdl file</b>, but i want to know how we ll download, the <b>file from webservices</b>. i hope u understood my question.
If possible , can any one send me the entire steps for the above scenario, please send me the pdf file to my email: <b>[email protected]</b>
regards,
Satish.so, you are going to consume webservice. First use the wsdl url in the browser and save the content as a file. After saving, go to ESR , use external definition tab and save over there. In IR, at the soap receiver side you have to configure target URL and user credentials over there.
If you have more questions, Please let us know. Hope I answered your question -
In HTTP to SOAP scenario. Error i get is "Invalid content type for SOAP"
Hi,
In HTTP to SOAP(synch) scenario. Error i get is <b>"Invalid content type for SOAP"</b>
When pass my data in the HTTP client, I get the following Error.
What may be the cause,How to reslove it.
Response am getting is below............................
Result:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN</SAP:AdditionalText></SAP:Error>hi ,
Just refer following 2 links
Re: Invalid content type for SOAP
Re: invalid content type for SOAP: TEXT/HTML
Regards,
AshwinM
Reward If helpful -
Synchronous Proxy - SOAP Scenario (Error 500 in Response).
Hi
I've built a few Synchronous Proxy -> SOAP Scenarios,
with 'Do Not Use SOAP Envelope' option.
For two of them, I'm facing a common error.
The error is: ADAPTER.HTTP_EXCEPTION (HTTP 500 Internal Server Error).
When I paste the EXACTLY SAME payload picked up from XI, into the SOAP client, it works giving valid response.
Trying to figure out the issue.
R/3 System:
WAS 620 (Level 0041)
XI System:
PI 7.0 (Level 0007)
SOAP System:
BizRights (Approva) 3.0
Any help is appreciated.
Rajendra.Hi,
Following SAP notes may help you- 804124, 807000
Regards,
Moorthy -
Hello ALL
I am trying to working in RFC to SOAP scenario in sap pi 7.31 single stack system.with help of blog **************** - Scenario on RFC to SOAP
i am trying to pass input values from ECC through RFC to web service .
while sending data using function module from ECC system i got following error
thnx in advanceHi Ganesh,
are you getting any error is SM58? Please check the below blog for configuration
Michal's PI tips: How do you activate ABAP Proxies with AEX - simplified version
IDOC_AAE To File with all Configurations
the below discussion will be useful
RFC to FILE(7.3) single stack -
Hi Experts ,
My scenario is http 2 soap.then soap url will be call to the sap(bapi).i dont have idea on that.can u please any body help me.if there is any links r there provide me.
Regards
SyedHello Syed,
Give a hit in sdn, you get tons of data.
However go [LINK|http://www.sdn.sap.com/irj/scn/advancedsearch?query=httptosoap]
/people/praveen.gujjeti/blog/2010/01/14/calling-abap-proxies-using-soap-and-http-adapters-in-sap-xi30pi70
riyaz.net/blog/xipi-a-guide-to-using-sap-xi-soap-adapter/technology/sap/113/
Regards
Pothana -
HTTP Post Outbound scenario - Error 110 - Timeouts in SMICM Tracefile
HI There
We have a scenario where we do a HTTP post using the HTTP Plain Adapter to a SMS service provider from a message received from a BW system via RFC, It works perfectly in our development system but we cannot get it working in our production system
In SXI_MONITOR the message fails with the error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Running a trace in SMICM shows the following in the tracelog
[Thr 4632] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 4632] IcmReadFromConn(id=9/140033): request new MPI (0/0)
[Thr 4632] MPI<3018f>19#4 GetOutbuf -1 cb2250 65536 (0) -> 0DE122B0 0
[Thr 4632] NiIRead: hdl 43 recv would block (errno=EAGAIN)
[Thr 4632] NiIPeek: peek for hdl 43 timed out (r; 500ms)
[Thr 4632] NiIRead: raw read for hdl 43 timed out (500ms)
[Thr 4632] IcmReadFromConn: read failed with timeout: 500 -> roll out
[Thr 4632] MPI<3018f>19#5 WriteOOB 00000000 02000000 09000000 01
[Thr 4632] MPI<30190>15#11 ReadOOB 01000000 01000000 2D000000 00 -> 0
[Thr 4632] IcmHandleOOBData: Received data on 1st MPI (seqno: 1, type=1, reason=1): 45/14512/0
[Thr 4632] MPI<3018f>19#10 ReadOOB 01000000 01000000 2D000000 00 -> 0
[Thr 4632] IcmHandleOOBData: Received data on 2nd MPI (seqno: 1, type=1, reason=1): 45/14512/0
[Thr 4632] IcmHandleOOBData: Received context key (type=1, reason=1): 45/14512/0
[Thr 4632] NiWakeupExec: send wakeup signal to 64997 (sock 16992)
[Thr 4632] IcmConnRollOut: connection (id=9/140033) rolled out:
[Thr 4632] CONNECTION (id=9/140033):
used: 1, type: 1, role: 2, stateful: 0
NI_HDL: 43, protocol: HTTP(1)
local host: 200.1.1.100:3405 ()
remote host: 196.30.220.242:80 ()
status: READ_RESPONSE
connect time: 23.07.2008 07:13:10
WP-status: ROLLED OUT (Context: 9, Role: 2)
tid: 45, mode: 0, uid: 14512, roll-reason: ICM_ROLL_NETTIMEOUT
With the following 2 lines ir differs from our development system - this is the point where it goes wrong
[Thr 4632] NiIRead: raw read for hdl 43 timed out (500ms)
[Thr 4632] IcmReadFromConn: read failed with timeout: 500 -> roll out
We have already checked the following between the 2 systems
1. Configuration in Netweaver Administrator is Consistent
2. Communication channel and Mapping is consistent
3. Profile parameters for ICM are consistent
Any ideas as to what this problem could be
Many ThanksHi
after you download the html client.
go to view -> source
and enter the present xiusername & pwd which you using and save.
Enter the below details in http client.
Servername : XIServername
Port : 80<instancenumber>
Client : XI server client number
Server : Sender service (business service or busienss system or integration process...when it comes to the HTTP adapter you need to create the business service that business service name you need to enter )
Interface name : outbound interface name
namespace : name for interface.
If you doing Party scenario enter the Party, Agency and Schema details also else optional.
Enter the Input xml data while enter the input data remove the first xml version line and paste the other data.
click on send message.
check the exchange profile set the httpport or not
check these links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
The specified item was not found.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/http%2bto%2brfc%2bsynchronous%2bscenario%2b-%2bfaqs
HTTP to RFC - A Starter Kit
/people/r.eijpe/blog/2006/02/19/xml-dom-processing-in-abap-part-iiia150-xml-dom-within-sap-xi-abap-mapping
Regards,
Suryanarayana -
HTTP- XI- SOAP(webservice) - error in outbound mapping
Scenario is HTTP(request)->XI->SOAP(webservice) ->XI->HTTP(response)
2 messsage mappings for request and response (syncronous)
1 interface mapping
HTTP payload reaches XI from there it appears problem translating request data to webservice external URL "http://webservices.imacination.com/distance/Distance.jws".
Message mappings when tested with sample xml in intergration repository results in success. Meaning source populated data gets copied to target in IR testing (both for request and response).
Here is the log from SXMB_MONI
- - - - SystemError synchronous 034E60D2-1D22-6B44-B424-E7A4527B7375 54F73912-E6A9-A741-A815-1F623FC79293 2007-01-23T14:50:58Z - vservice4 mi_inb_ws - vservice4 mi_out mi_out - BestEffort - Application <b>EXCEPTION_DURING_EXECUTE</b> com/sap/xi/tf/_mm_ws_ java.lang.NullPointerException During the application mapping com/sap/xi/tf/_mm_ws_ a <b>java.lang.NullPointerException was thrown</b>: N - - HTTP
server-protocol HTTP/1.1 user-agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) host <xiapp>:8050 content-length 230 remote-addr 10.20.40.120 <b>COMMIT is expected by application</b> !
SAP_CENTRAL - - - - R E C E I V E R - D E T E R M I N A T I O N Cache Content is up to date - - - - I N T E R F A C E - D E T E R M I N A T I O N Cache Content is up to date - - - - number of receivers: 1 Single-receiver split case - - - - Interface Mapping urn:
vmyvendor.org\http2webservice im_ws RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_ws_ java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59)
Any pointers would be greatly appreciated. ThanksFrom XML request message->SOAP Header->Trace & using XML spy problem is in <b>CL_XMS_MAIN-CALL_PLSRV</b>. The log also talks about message persist processing, is it valid for sync webservice?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
+ <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
<Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
<Trace level="1" type="T">user-agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)</Trace>
<Trace level="1" type="T">host xiapp:8050</Trace>
<Trace level="1" type="T">content-length 229</Trace>
<Trace level="1" type="T">remote-addr 10.20.40.101</Trace>
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 69CB2C55A02E1048AC67316A17FD109D</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
+ <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
+ <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
+ <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- <!-- ************************************
-->
+ <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="1" type="T">Interface Mapping urn:
vendor\http2webservice im_ws</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_ws_</Trace>
<Trace level="1" type="T">java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy176.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_mm_ws_: java.lang.NullPointerException; null</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_mm_ws_: java.lang.NullPointerException; null at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy176.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy176.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace> -
Hello,
Via an HTTP client (wfetch) I am trying to send a payload to a WebService I generated from the XI system(using the wizard).
The log from the http client is as follows:
<u><u>started....
WWWConnect::Close("16.16.158.134","8000")\n
closed source port: 1490\r\n
WWWConnect::Connect("16.16.158.134","8000")\n
source port: 1695\r\n
REQUEST: **************\n
POST /sap/xi/adapter_plain?namespace=http:\lab.hp.com&interface=LookForNewOrders&service=HTML_SERVICE&party=&agency=&scheme=&QOS=&sap-user&sap-password=
&sap-client=700&sap-language=E HTTP/1.0\r\n
Host: hp547-4.gre.hp.com\r\n
Accept: */*\r\n
Content-Length:174\r\n
Authorization: Basic eGlzdXBlcjoxMjM0NTY=\r\n
\r\n
<LookForNewOrders>\r\n
<Refnumber>4</Refnumber>\r\n
<CustomerID>444</CustomerID>\r\n
<Material>dd</Material>\r\n
<Quantity>1</Quantity>\r\n
<Status>N</Status>\r\n
</LookForNewOrders>
RESPONSE: **************\n
HTTP/1.0 500 Internal Server Error\r\n
set-cookie: sap-usercontext=sap-language=E&sap-client=700; path=/\r\n
content-type: text/html\r\n
content-length: 0\r\n
server: SAP Web Application Server (1.0;640)\r\n
\r\n
finished.</u></u>
For the soap receiver adapter I put the follwoing URL, which I took out of the WSDL of the webservice:
http://hp5474.gre.hp.com:8000/sap/bc/srt/rfc/sap/IF_Orders_Insert?sap-client=700
In SXMB_MONI I receive the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: SOAP processing failure, error id = 1001</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please advise,
Thanks
BoazHi Boaz,
It could be that there is nothing wrong with your XI config. The 1001 errorocde suggests that there may be an application processing error. Can yuou test the webservice directly with the data you are providing (to check that it is not causing the errors)?
Cheers
Manish -
Hi,
I am trying a http to soap scenario.
In the receiver soap adapter, I have specified the following:
Target url: http://test.abc.com/
Action: handleLogin()
When I send the request, I get a "time out error" as the response in the http client tool.
However, in sxi_monitor, I get a webpage as the response(A web page is being displayed in the monitor).
What I was expecting is a response message that matches the wsdl.
I have tried using "" and a blank value for the Action field in the soap adapter, but no luck.
Any help would be appreciated.
Thanks,
Smitha.Hi Shabarish,
Thanks for your response.
I provided the operation name in the soap adapter as specified in the blog, but I am getting a http_adapter exception. (500 internal server error)
Any clues?
Thanks,
Smitha. -
HTTP 500 Internal Server Error with Large Attachment in SOAP Scenario
Hi,
we have implemented SOAP - XI - SOAP Scenario in our landscape (Sap Neatweaver Process Integration 7.1) .
One of the functionality of this scenario is the Upload of Documents to External Web Service through standard SOAP Attachment.
If we try to upload a small file (smaller than 20MB), task works fine and the document is correctly uploaded.
If we try to upload a larger file, we encountered in this generic error:
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 error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
We tried to increase timeout parameters (in communication channel and in ICM Value) but the response is the same.
We verify also if icm/HTTP/max_request_size_KB parameter was set to a value smaller than our file size limit (20MB) but is set to default value (100MB).
The problem isn't on External Web Service Layer because if we try to upload the same documents directly to that web service upload works fine, and in External Web Service's Log there aren''t any indications of this error.
So I ask you: are there any System Parameters to verify to solve this issue?
For additional, in ICM Monitor LOG we can read this WARNING when we call our service:
WARNING => IcmReadFromConn(id=53/454390): temporarily out of MPI buffers -> roll out [icxxthrio_mt 2646]
This warning may be related to the problem? If yes, how can we solve it?
Thanks a lot,
Marcello RicciHi ,
Please answer my following questiosn.
1) which PI version are you using?
2) How many J2EE nodes you have.
please be reminded that SOAP is not for the heavy messages. Then you need to increase your timeout parameters from BASIS.
Rgds
Veeru
Edited by: viru srivastava on Dec 14, 2010 10:18 PM -
HTTP 401 Unauthorized, error in proxy to SOAP Scenario
Hi all,
We got the below error in our proxy to SOAP Scenario.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
So please let me know what could be the possible reasons behind it and how to resolve it.
Waiting for your valuable response.Hi,
Consider the parameters connection pool size and connection wait time:
ume.r3.connection.master.poolmaxsize
ume.r3.connection.master.poolmaxwait
These parameters are described in the note below:
#821026 - AdapterEngine messaging URL returns HTTP 401 under high load
Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Please kindly check the note below:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Regards,
Caio Cagnani -
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,
PushpaHi,
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 -
Error handling in File - XI - SOAP scenario without BPM
Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, TanjaHi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo
Maybe you are looking for
-
A friend's iMac (2010 - Snow Lepord - 27" display) won't allow them to shut it down or put it into sleep mode. The system continually reboots itself when using the Apple > "Shut Down..." command. Similarly, it continually turns the display back on w
-
I cant sign in with my ipad to face time or imassege
Hi i cant access or sign in to face time or imassege in mini ipad
-
Problem in Layout od Adobe PDF
Hi all, I have created and activated the interface. There is an import parameter and an internal table in the interface. the problem is I am getting the internal table fields and the parameter in the layout of the form as it is required to dra
-
Why aren't my software updates updating?
Today I was trying to install some software updates (13). The computer was plugged in and restarted, but when I checked to see if the updates had been installed they hadn't been. What could be the cause of this? Thanks for your help.
-
Has anyone gotten the Digi 002 to work on Mavericks?
Has anyone gotten the Digi 002 rack to work on OSX Mavericks? I know it says '002 rack and console are not supported (untested)' according to Avid's site, but I was curious if anyone has got it to run. I am currently using Logic Pro 9 with it right n