on 02-14-2012 4:36 AM
Hello,
My scenario;
1st: ABAP Proxy to PI to SOAP Sender(Third Party)
2nd: Idoc to PI to SOAP Sender(Third Party)
We have tested the endpoint URL using SOAP UI and its working without error.
But when try to do a test from RWB using Integration Engine, message is delivered successfully, no error in sxi_monitor but in communication channel, we get and error SOAP: call failed: java.net.ConnectException: Connection refused
Our Webserver communicates through 8080 port and which has been opened for communication.
also we are able to ping the webserver through PI.
Any input will be helpful
Regards,
Abhishek
Hi,
> But when try to do a test from RWB using Integration Engine, message is delivered successfully, no error in sxi_monitor but in communication channel, we get and error SOAP: call failed: java.net.ConnectException: Connection refused
This is connectivity issue, have you checked the below threads
http://forums.sdn.sap.com/thread.jspa?threadID=444378
http://forums.sdn.sap.com/thread.jspa?threadID=1364587
Regards,
Venkata Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The RFC destination maintained for Idoc to SOAP sent from R/3, the client was wrong in RFC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please go through this thread
[http://forums.sdn.sap.com/thread.jspa?threadID=1988766]
Regards,
Venkata S Pagolu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhishek,
Does your backend use special security like wsse?, is it a simple SOAP protocol?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhishek,
Make sure that you typed the correct Target URL and SOAP Action in the receiver Communication Channel parameters. This is the most common reason for communication problems, when you are able to successfully ping the target location. Most importantly, make sure that the URL does not contain the "?WSDL" ending and that SOAP Action is in accordance with the .wsdl file contents.
Hope this helps,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Thank you for your replies,
The URL address mentioned in correct, when i use the same URL, in the testing tool like SOAP UI, i do get a response back from the web service, but when i do the same from PI, it gives me connection error.
I have also maintained authentication for user, ie the user id and password.
Regards,
Abhishek
My scenario;
1st: ABAP Proxy to PI to SOAP Sender(Third Party)
2nd: Idoc to PI to SOAP Sender(Third Party)
i think ur scenarios is soap sender to Server proxy is it correct
if coreect then once you check the wsdl file whatever u was generated in sender agreement:
if ur scenario is Proxy to Soap :
once you check target url and actions in Receiver comm.channel.
please Elaborate ur issue and scenario and once you check the below blog
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.