on 05-09-2019 9:52 AM
Hi Experts,
I have a pass-through synchronous scenario from SOAP to REST-XML and when I generate WSDL from ICO and use the short URL from it that says "WSDL URL" and paste it into SOAPUI then I get the error of "HTTP 405 Method not allowed. Error: HTTP method POST is not supported by this URL".
If I use the long HTTP url from WSDL then from SOAPUI everything works fine. Please let me know what am I doing wrong here?
Regards,
Arkesh
For short URL try this :
The URL which you are using is dynamic its gets changed . Check the sender soap channel config as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj,
Thank you for sharing the short URL format. It works fine in SOAPUI.
But in BODS system, who is the actual sender to our SAP PO system, does not accept this format of the URL. It takes only the WSDL URL of the format :
http://<host>:<port>/dir/wsdl?p=ic/<ICO Object ID>
I tried sharing the long URL but that URL is too long for the BODS system and it gets trimmed automatically towards the end of the URL. So, its of no use to them.
Regards,
Arkesh
Ideally the SOAP adapter needs query parameters which makes it hit adapter engine, the short URL which I provided or the one you took the long URL from WSDL has query parameters which push the message to adapter engine .
The URL which you are trying to use does not have nay such query parameters , so i am not sure if that really works for you.
Arkesh ,
It should work with both the URL , URL from the WSDL or the short URL.
Can you paste the URL format you are using and make sure your are usig HTTP as protocol in sender cc.
Thanks,
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj,
In SOAPUI, I am using the short endpoint URL of the format:
http://<host>:<port>/dir/wsdl?p=ic/<ICO Object ID>
And the long URL is of the format:
http:// <host> : <port> /XISOAPAdapter/MessageServlet?senderParty=&senderService=<Sender_BS>&receiverParty=&receiverService=∬erface=<Sender_Interface>InterfaceNamespace=<Sender_Namespace>
Regards,
Arkesh
Do you have the WSDL url and and endpoint used in this test?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Alexandre,
In SOAPUI, I am using the short endpoint URL of the format:
http://<host>:<port>/dir/wsdl?p=ic/<ICO Object ID>
(I have copied it when I generated the WSDL from the ICO and this appeared on the top as 'WSDL URL')
And the long endpoint URL is of the format:
http:// <host> : <port >/XISOAPAdapter/MessageServlet?senderParty=&senderService= &receiverParty=&receiverService=∬erface= InterfaceNamespace=<Interface_Namespace>
Hello Arkesh,
You can trigger a call to the sender SOAP adapter using below URL and specify the parameters in the URL even if some of them do not have values.
http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?senderParty= <name of the sender party> &senderService= <name of the sender service> ∫erface= <name of the interface>&receiverParty= <name of the receiver party> &receiverService= <name of the receiver service>∫erfaceNamespace= <name of the interface namespace>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
are you using wsdl url to call the service from soap ui? wsdl url shlould be used to load wsdl file into soap ui. in order to call service, you have to use the long url.
please check possible end points to call soap service in this.
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.