Testing XI SOAP scenario via XMLSpy

I've completed the following -
1. Created the scenario SOAP => XI => RFC
2. Using XI config, generated WSDL specifying the Message Interface which triggers the scenario in XI.
http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<Channel Name>
3. Transported this WSDL to local directory
4. Testing WebService by sending a SOAP message using XMLSpy. Option Soap=>Send request to Server.
I don't see any pop-up to enter xiappluser and password .
I get the following popup error message
HTTP error: could not POST file
'/XISOAPAdapter/MessageServlet?channel=:HTTP_LINK:testSoap&version=3.0&
Sender.Service=HTTP_LINK&Interface=urn%3Agoodyear.com%3AInfoLinkToSAP%5EInfoLink_XML_Req_Sync_Abs' on server 'xi0.goodyear.com' (404).
Please let me know if there is anyway to resolve this error condition.
Thank you.

Hi Prasad, thank you.
Niall Guerin wrote me a message in which he explained that some of my XI components are inconsistently patched. I will verify and correct that.
Thanks again.
Ivan
<i>Hi Ivan,
Thanks for the patch level information above. Your components are not
up to date.
As you can see the following XI AFW components are inconsistently
patched:
sap.com SAP-XIAFC 3.0 SP12
sap.com SAP_XIAF 3.0 SP17
ALL XI components MUST be on the same patch level. This means:
XIAFC, XIAF, and XITOOLS must all be on SP17. The same goes for the
ABAP stack. Basis must be on SP17 and so must your J2EE Engine. With
XI, ALL patch levels must be consistent as a prerequisite. Please
refer to attached note: 750511.
In addition, it looks like you've got a PCK deployed on the XI host
as well? A PCK cannot co-exist with an XI installation, so please
ensure you did not do this and undeploy it if it was installed on top
of the XI host.
Please patch the XI Java components correctly and then reproduce the
SOAP Adapter problem after sending a soap request to the adapter.
For more information on the message status in your screenshot, refer
to the weblink below. This is an enhancement with SPS17 for the Runtime
Workbench:
Communication Channel Monitor
http://help.sap.com/saphelp_nw04/helpdata/en/44/2a1a8620323f0ee10000000a114a6b/content.htm
Kind Regards,
Niall Guerin</i>

Similar Messages

Error while testing sender SOAP scenario from XMLSpy-but can test from RWB

HI,
I developed one scenario with sender SOAP adapter and Receiver side ABAP proxy.
Now I want to test my scenario.
I tested my scenario successfully from RWB-->Integration server Integration Engine. ( it posted successfully and I can see checked flag in SXMB_MONI)
But when I tried to test the scenario fro XML spy it is throwing HTTP error 500.
When I type my URL in internet explores it is giving Message Servlet is in Status OK.
I am not sure what is the difference between there two type of testing.
What does it mean by successful from RWB and fails from XMLSpy?
Why I am getting this error from XMLSpy?

Dear Ashok,
if RWB showing you successful then message in not in error.
XML Spy giving error HTTP 500 not it is just server error.This might be due to large payload.
here is the description of all error related with 500+
5xx Server Error
The server failed to fulfill an apparently valid request.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates (RFC 2295)
507 Insufficient Storage (WebDAV) (RFC 4918)
509 Bandwidth Limit Exceeded
This status code, while used by many servers, is not an official HTTP status code.
510 Not Extended (RFC 2774)
first ping your server
Tcode for this is SM49>ping
Then in additional parameter put the server IP and execute it will show you its reachability.
if it is not reachable then contact the server vendor,
Else if it is timeout problemthen
you run Tcode SXMB_ADM>intregration engine configuration
put category RUNTIME
then click specific configuration
Then change/increase HTTP timeout
**PS: Reward points if useful**
Regards,
Sumit Gupta

How do I test Sender SOAP scenario?

Hi
Soap - IDOC.
The authorizations on the WS to send data is not yet provided to me.
thus, I m trying to send a sample data from Altova XML spy.
For this purpose I have created a WSDL from ID (Tools -> create WS)
in Receiver NS, receiver MI, I have given receiver side details only
but in sender side NS and MI and Sender service, I have given the Sender service that I have created in ID and the XI's local NS and receiver MI
For URL, I have selected on "Propose URL". Now will I be able to send data to the R3 server with this link?
(R3 is production server in my network)
now with that WSDL, I coudlnt validate in XML SPY.
have I provided the correct details?
Please suggest me is there any other way of testing Sender WS to IDOC?
Thanks and Regards,
Venkat.

oops I guess I have confused u
let me detail it again
Scenario : SOAP - XI - IDOC
The scenario is finished.
I dont have authorizations on WS to logon n send the data
Thus, I have created WSDL from ID (in XI)
now I want to send data to XI which inturn will post the data to R3 and create a IDOC
when I try to validate the WSDL created through XI using SPY, it couldnt validate and I couldnt send the request
I want to send the data from outside XI and I want to generate a IDOC with the test data I have specified.
how do I do it?
Hope I made it clear this time
Thanks,
Nikhil.

Testing SOAP scenario

hey guys
i m doing a very simple SOAP scenario,can anyone help me out with how should i test my scenario,i came across XMLspy in some of the blogs,do i need to download that and how will i test my scenario.
thanx
ahmad

hi,
you need to be more specific:
1. are you trying to create w web service exposed by XI?
(then you need a SOAP test tool - like stylus studio etc)
2. or maybe you want to call a web service from XI
then you can do an HTTP - SOAP scenario
and you don't need any toos except the http adapter test tool
which can be found on XI FAQ page (link below)
basicall these are your two options
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Testing of SOAP to FILE Scenario

Hi all
I have done with SOAP to FILE scenario.
--> while defining web service what we need to give in the URL????
--> How to test this SOAP to FILE scenario to see wheather it is working fine or not, what are the all options
Thanks
Dheeraj

Hi Dheeraj,
Definitely you can test it through the microsoft infopath tool.
steps to follow:
Executing wsdl File Using Microsoft Info Path
1.>Click on the design a from template
2.>Select the Web service icon and click ok
3.>Select the radio button u2018receive and submit datau2019 and click on next.
4.>Enter the path of the generated wsdl which u have saved and click next.
5.>Select the interface and click next
6.>Select the interface and click next.
7.>Double click on parameters.
8.>Double click on the parameter (which you want to send as request). Then click on the query field and click ok.
9.>Click next. And click Finish
10.>Now drag the query fields on the data fields to the left side. And click preview.
Please follow these steps I hope you will be able to test it.
Thanks and regards,
Nutan

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.

RFC TO SOAP SCENARIO

Dear Experts,
I am facing the Following error for RFC to SOAP Scenario, i Tried
1. Full Cache Refresh
2.Delete and create Sender Agreement Again
3.Specifying the Program id Again
yet the Scenario is not Working, could you please help me in Resolving this at the Earliest
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'ISU64', toParty '', toService '', interface 'YGVK_SEND_WS_TO_WS', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_YGVK_SENDER_WS_TO_WS' (channelId f1219fd41be734a2a72cd3ddcb779475)
Regards,
Vijay Karthik G

Hi,
copy the sender agreement to the same one but in party field
remove the " * " (it has to be empty)
test it and let me know
Regards,
Michal Krawczyk

RFC-to-SOAP-Scenario: XIServer:NO_MAPPINGPROGRAM_FOUND

Hey guys,
We've implemented in SAP PI 7.11 a RFC-to-SOAP-Scenario. The whole scenario is sync. WSDL and RFC are imported objects.
Now we're going on to test in backend and call the related remote function module via se37.
The error message is (from xsmb_moni)::
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What we've already done:
-> Cache refresh
-> server restart
-> soap fault mapping
-> dummy changes
-> mapping is available in sxi_cache
-> function module is not dumping in backend
Any ideas how we can go futher with this?
Thank you very much and greetings,
Stefan

FYI...
Apparently, this error message can sometimes be misleading.
I found in another thread that this message came after a short dump in the ABAP function. After viewing ST22 in our backend system I noticed short dumps corresponding to the times when I make the SOAP call.
[NO_MAPPINGPROGRAM_FOUND SOAP RFC Adapter]
We can call SE37 with the same parameters and there is no ABAP error. So the search for root cause continues, but maybe this info will help someone.
-Aaron

Error RFC to SOAP Scenario

Hi Experts,
I am getting an error while dealing with RFC to SOAP scenario::
soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
IS it problem from the webserver in sending the response?
Please suggest.
Thanks & Regards,
Sushama

Hi Suraj,
Thanks for the imputs.
We are given with the webservice by separate team, also I am accessing the application via Citrix. I cant test the WS outside the client network and in client desktop they haven't installed Altova Xml Spy
Request and response both are generated in Moni. It seems problem in receiving response only ?? WS url is also correct.
Regarding Receiver Soap parameters:
I have checked adapter specific identifiers and Variable transport binding.
Please suggest, if this is problem with the WS, I need to check with the team.
Thanks & Regards,
Sushama

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

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, Tanja

Hi 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

HTTP to SOAP scenario

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 ??
Evaggelos

When 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

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Sync File to SOAP scenario

Hey guys
i m doing a Sycn FIle to SOAP scenario(i guess i need BPM for that,right?)
lemme know if my configuration is correct
For sender FIle:
DT_sender,MT_sender,MI_sender,AI_sender(async)
For SOAP
DT_soap,MT_soap,MI_soap,AI_soap(sync)
For Receiver file
DT_receiver,MT_receiver,MI_receiver,AI_receiver.
and BPM would be
start>>Receive>>Sync send>>send>>stop
and ofcourse i need to import the WSDL for the webservice.
is this all,or i need to do some other designing too?
thanx
ahmad

Ahmad,
The weblog says you are sending a request from R3 using RFC. Then it gives back you the response from the webservice.
So first you have two scenarios:
Request:
Source: No datatype needed because you are importing the RFC.
Target: For this you need the datatype. Just create the datatype what he has mentioned.
Response:
Source : Just copy and paste the xsd. You import as an external definiton.
Target: Since your RFC is a synchrounous you will have the response for it. That is your target.
Then after that you do message mappings for request and response and then the interface mapping.
You dont need to have BPM for this interface. So dont worry about BPM for this interface.
Then you complete all the steps given in his weblog2. Then test it out.
---Satish

Testing XI SOAP scenario via XMLSpy

Similar Messages

Maybe you are looking for