Doubt regarding testing Soap scenario (HTTPS)

Hello Experts,
I have a scenario where a Bapi functionality(server proxy) is exposed as a webservice .
So scenario will be SOAP -> XI -> Proxy (calls a BAPI).
I need to use https for this scenario. I have read most of the blogs and threads regarding this and will proceed accordingly.
I have a simple doubt :
After configuring a scenario to *only* accept a Soap message with appropriate valid certificate -
If I have to test my scenario using XML spy, how can I attach a certificate to Soap request in XML spy?
Or is their any feature available in XMl spy or in Xi itself to do these kind of test?
or please suggest me a work around to test the scenario configuration with certificates.
Thanks in Advance!
Regards,
Xi Queries.

Hi Swarup,
I would like to know :
What happens when a check for certificate validation fails in XI? It may be due to invalid certificate, expired certificate or a request from unauthorised user-
- Will it be raised as a exception and we need to do some configuration to inform it back to Sender?
- Will the message fail in Moni with red flag ?
- Alerts will be created ?
Please share your experiences and expert sugestions.
Thanks in Advance!!
Regards,
XI Queries.

Similar Messages

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>

Invalid request in SOAP Scenario - "HTTP 400 Bad Request"

Hi,
By sending request to a Webservice thorugh XI ,I am getting an error as "HTTP 400 Bad Request" in MONI and the response payload looks like this
"Request Error (invalid_request)
Your request could not be processed. Request could not be handled
This could be caused by a misconfiguration, or possibly a malformed request.
For assistance, contact your network support team."
I copy pasted the request payload in SOAP UI, there its working fine.I don't know where it goes wrong.
Please help me in that...
Thanks & Regards,
Yuga

Hi Yugapreetha,
Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED
Description: The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515, 910649, 706563 If it is because of Queue problems have a look into SMQ2 .
And also here are a list of possible reasons for your problem with solutions.
It could be that it cannot find your file adapter.
1. Have you specified your hostname or IP address? Often the server cannot resolve the ip address for the hostname of your PC.
2. Is the path and port in the directory the same as the path and port of your file adapter?
3. Try question 14 (integration engine section)
/people/mark.finnern/blog/2006/01/12/finally-best-of-sdn-2005
4. also question 11 (in the same section)
5. if the avove will not fix it open XI config guide and
have a look at section
"Connecting Business Systems with an Integration Engine to the Central Integration Server"
6. Your error code is 400, so check this link,
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
For http 400 - its a bad request.
'The request could not be understood by the server due to malformed syntax.'
If you have the XI trouble shooting guide see from page 54,and also try:
1.Check that the port really is the ICM HTTP Port (transaction
SMICM) and not the J2EE port
2.If the port is wrong, change the pipeline URL in the SLD in
the business system of the Integration Server
3.Restart the J2EE Engine to reset the SLD buffer of the
Adapter Engine
Source- "XI troubleshooting guide"
Check out this SAP Note- 824554
Also this links
ICM_HTTP_CONNECTION_FAILED
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Reprocessing failed XI messages:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Vinod.

Sender Soap scenario HTTP/1.1 404 Not Found error

Hello All,
I created SOAP to IDOC scenario, generated the WSDL file from Sender agreement and while testing the interface using SOAPUI tool iam getting HTTP/1.1 404 Not Found error.
i gave login authorization details in the SOAPUI tool.
Update: when i generated the WSDL file from sender agrement, in the URL the port number was 443.
when i check the port numer in SMICM transaction it show 50000.
Now when i test with port numer 443 iam getting Connction refused error.
Regards,
Chinna
Edited by: chinnasapxi on Mar 4, 2011 6:44 AM

i created the URl and when i tested the from SOAP UI below is the error detials.
Fri Mar 04 11:32:08 IST 2011:ERROR:com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing transport for protocol [ http]
   com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing transport for protocol [ http]
        at com.eviware.soapui.impl.wsdl.WsdlRequest.submit(WsdlRequest.java:241)
        at com.eviware.soapui.impl.wsdl.panels.request.AbstractWsdlRequestDesktopPanel.doSubmit(AbstractWsdlRequestDesktopPanel.java:146)
        at com.eviware.soapui.impl.support.panels.AbstractHttpRequestDesktopPanel.onSubmit(AbstractHttpRequestDesktopPanel.java:777)
        at com.eviware.soapui.impl.support.panels.AbstractHttpRequestDesktopPanel$SubmitAction.actionPerformed(AbstractHttpRequestDesktopPanel.java:488)
        at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
        at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
        at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
        at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
        at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
        at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
        at java.awt.Component.processMouseEvent(Unknown Source)
        at javax.swing.JComponent.processMouseEvent(Unknown Source)
        at java.awt.Component.processEvent(Unknown Source)
        at java.awt.Container.processEvent(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

Error while testing SOAP scenario

I have done SOAP(Sender)--SAP-PI- SOAP(RECEIVER) Scenario. It is in synchorous mode..
It works fine in Altove XML Spy.. and getting the response fron webservice..
but when i;m testing it PI (RWB->Comp Monit>Integration engine-->Test Messge ) it gives me error
" Error While Testing: Method Not implemented "
Can anyone please help me on this.. What acould be the reason.. for this..
Regards,
deep

Sunil, Thanks For your Reply...
Payload is correct.. and mapping is also fine. I'm getting reponse from Webservices using XML SPY..
But i have seen one warning about Integation Engine : Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client) in Component monitoring..
Does this warning cause this error anyway.. ? Because i'm getting error even in XML SPY when i defined business system as Sender and Receiver as Business Service. But if i define both are as Business Serivces.. it works fine.. (in XML SPY)
But in both cases i'm failing in RWB(INtegration engine-:>Test message)
Is there any relation to above mentioned warning " Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client) in Component monitoring.. "
Regards,
Deep

Doubts in Shelf life scenarios........

Hi All,
I have some doubts regarding Shelf life scenarios:-
1. In material master there are 2 fields in Plant/stor.1 view those are Min. rem. shelf life and Total shelf life.
   the field "Total shelf life" is ok. this field means in how long the perticular product will get useless and we can decide it at the time of material master creation for ex. for a perticular material it may be 30 days or 4 months etc.
but how can be decide the field Min. rem. shelf life bcoz as I know its mean How many days are remaining to get the product useless.and we can decide this field, if we know the manufactring date of product and total shelf life. hence we can calculate it
as suppose total shelf life for a product= 30 days
                   Manufacturing date = 1 jan 2010
                   current date = 20 Jan 2010
so Min. rem. shelf life   = 10 days
but here in material master how to calculate Min. rem. shelf life,and why its mandatory field, if we put Total shelf life field.
2.whats the use of Rem. shelf life field in po or what will its impact,while shelf life is only provide the impact to GR.
3.In GR,its mandatory to put the date in the field "Date of Manufacture" or we can get it any other ways excluding batch.
4.In GR there are a field "Shelf Life Exp. Date" ,we can get through Date of Manufacture (from gr) + Total Shelf Life (from Material Master) here again then whats the use of "Min. rem. shelf life" field shows in Material master and PO.

Hi Himanshu,
I mean if a goods are recived under the expiration date and min shelf life is also ok.
First of all no business will allow to receive already expired date into the premises.
but goods are issue at that time when date has been expired,so how this scenario is run/maintained.
At this instance system will throw an error while Goods issue " Goods expired , kindly check expiry date".
Hope this helps.
Regards
Utsav

Regarding A2A & B2B Scenario development in SAP PI /XI?

Hello Experts,
Kindly clarify my doubt regarding A2A & B2B Scenario's development in SAP PI / XI.
I mean when to use & which adapter user in which scenario & specifically what difference does it make when we use one adapter in one scenario meant for another one. Will it work?
The Question may be quite Naive to all of you but still want to clear some thing from my head.
Best Regards
Priyesh Shah

Hi Inaki Vila,
Thanks for Reply, i did searched SDN before raising this question. i stumble upon this difference between A2A and B2B scenarios.but the question still remain in my head what adapters should i use for B2B scenario is it necessary that i should use EDIFACT for B2B & not for A2A. Here in my company we are handling a client which has several legacy system in landscape which are integrated to SAP ERP with SAP PI here they mostly used File Adapters, what happens if i use File Adapters for B2B scenario.
Best Regards
Priyesh Shah

Doubt Regarding SOAP to File Scenario

Hi All,
I am trying to create a SOAP to File scenario .These are the following things I have done so far :
IR - 2 datatypes ( 1 for soap message and 1 for file message )
       2 message types for the corresponding messages
      2 Message interfaces, both are asynchronous
      1 message mapping
      1 interface mapping
ID- 2 business systems (1 to send soap, 1 to recieve file )
    2 communiccation channel (soap sender, file receiver )
soap sender adapter parameters - Interface Name - Message interface for soap message
                                                  interface namespace - scenario namespace
Then, i generated a wsdl file to expose the outbound message interface for soap message as a web service, url for message interface : http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
After generating the wsdl file, i imported it in external definition
Could anyone plz. tell me, is this the right approach to creat this scenario ? how can I test this scenario?using altova spy ?

Hi,
The URL you have mentioned to genarate WSDL is not a valid one
http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
Check the below valid URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel.
You no need to import this to the Eexternal Definition as you already have DT,MT and MI, Any way this dosn't make any difference.
You can use SOAPGUI Tool to test:
->Create New Project -> provide WSDL you have genarated.
->Select Request and provide username and password and click the green button on top(Submit request to end URL).
Using altova spy:
Select SOAP Menu->Create New SOAP Request and provide your WSDL file and
SOAPMenu->Send Request To Server
Then you will get response..
Regards,
Prasanna

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 TO TEST SOAP SENDER TO FILE SCENARIO

Hi gurus,
I have designed and configured SOAP to file scenario.
I have used http://xyz namespace in design time.
I have created two business systems for this sceanrio.
I have downloaded and installed soap client on my system.
When I open this soap client it is asking
1)URL
2)load request from
3)In the editor request tab what should i give.
4)wht is the response tab here
I want to send data to XI from SOAP and then to file.
Please help how to give data and how to get the data format to give in the requst editor?
Points will B rewarded
Regards
Sreeni

Hi,
You can use a SOAP client like Altova XML spy for posting a message to XI.
The best way to do this is to use the generated wsdl for creating a soap request.
once the wsdl file is picked up by the soap client, it automatically generates the url.
now the response which comes back to the soap client is usually a http status code of successful post. (since u r performing an async scenario)
also ensure u use the j2ee port while genrating the wsdl using the "Create Webservice" option in Int Directory.
Also chk the link for the weblog on sender soap scenario.
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
Hope this helps.
Award points if found helpful
Cheers!!
Sidharth

When will we go for Altova xml spy testing in case of soap scenario ??

Hi
suppose I have a scenario like this: rfc-xi-soap. In this scenario if somebody say's testing the scenario using Altova xml spy means Altova xml spy will be acting as webservice ?? what is the ( or is there) significance of below URL in testing ??
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=<party>:<service>:<channel>
thanks
kumar

Hi Kumar
I am using XmlSpy for following reasons ::
*) To check & confirm the Request/Response/Fault Structure of the WebService.
*) To check the whether the WebService is UP or not, in case someone has reported an issue.
*) To develop the xsd structure for the WebServices, in case I am getting different structure after importing the WSDL in XI. Like in the case of this Weblog -->
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
In this response structure is created, you can also use other tools for creating xsd.
- Lalit -

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

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

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

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

Doubt regarding testing Soap scenario (HTTPS)

Similar Messages

Maybe you are looking for