Connection refused: SOAP

[EdgarTabar]

Hi,

when I testing a webservice from the PI I get the following error message:

SOAP: call failed: java.net.ConnectException: Connection refused: connect

SOAP: request message entering the adapter with user J2EE_GUEST

WhenI try it in the internet explorer, then i can see the wsdl definition of tthe webservice.

Thanks

[markangelo_dihiansan · Accepted solution]

Hello,

 checked the url from the receiver channel in the internet explorer and i can see the wsdl definition of the webservice.
I don't have a user-id, passowrt or any other SOAP action.
So i guess that the port is ok.

What you are seeing is the URL for the service definition which is different from the URL that you will be posting the message and the SOAP action that is also needed. See this example:

http://www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx in this website, if you click the Service Description. It will give you the WSDL http://www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx?WSDL

But once you click an actual operation, say add

http://www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx?op=Add

You will know that the SOAP Receiver URL (SOAP 1.1) will be:

Host: www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx

SOAP Action: http://tempuri.org/Add

and the content-type is: text/xml

Regards,

Mark

Edited by: Mark Dihiansan on Feb 7, 2012 10:19 AM

[EdgarTabar · Accepted solution]

Hello,
> 
> Can you share to us the details that you have placed in your SOAP Receiver Comm channel?
> 
> Regards,
> Mark

Adapter: SOAP http://sap.com/xi/XI/System SAP Basis 7.11

Receiver

Trans. Prot.:HTTP

Message Prot.: SOAP 1.1

Adapter Engine: Central Adapter Engine

url: http://server.local:8082/soap?service=WebService

[markangelo_dihiansan · Accepted solution]

Hello Edgar,

I re-edited my previous post and gave an example. Were you able to read it?

Regards,

Mark

[EdgarTabar · Accepted solution]

Hello Edgar,
> 
> I re-edited my previous post and gave an example. Were you able to read it?
> 
> Regards,
> Mark

Hi Mark,

yes i see it and it is very helpful.

In my webservice i have some operation like update, Insert an so on..

Now i will change the url to: url: http://server.local:8082/soap?service=WebService?op=Update

Edited by: Edgar Tabar on Feb 7, 2012 10:57 AM

[former_member184681 · Accepted solution]

Dear Edgar,

This error "Connection refused: connect" can also be caused by the Firewall blocking connections from PI to the target system or the target system listening to a different port than what is specified in your receiver CC. You can verify if PI has access to the target system by executing the TELNET OS command (to your particular hostname and port) from transaction sm69 of your PI ABAP stack. You might have to add this command there manually first.

Hope this helps,

Greg

[markangelo_dihiansan · Accepted solution]

Hello Edgar,

In the example I gave

But once you click an actual operation, say add
http://www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx?op=Add

Here are the parameters in the SOAP Receiver CC

Target URL: www.html2xml.nl/Services/Calculator/Version1/Calculator.asmx 
Soap Action:http://tempuri.org/Add

So the Target URL that you will be providing

http://server.local:8082/soap?service=WebService?op=Update

is not correct. If you want, you can execute the webservice (without using PI) by using a third-party tool such as SOAP UI. The SOAP Action is needed because native SOAP Adapter is using SOAP 1.1

Hope this helps,

Mark

[former_member184681]

Hi Edgar,

It looks like you are using a bad URL for the connections. Most probably you have chosen Tools -> Display WSDL in Integration Directory to generate the .wsdl file that you delivered to your sender system's responsible. Instead, you should right-click your Sender Agreement and choose Display WSDL to get the right file, with correct endpoint URL. Importing this new .wsdl file to the sender system should solve your problem.

You can also try manually changing the target URL to the following:

http://{PI HOST}:{PI PORT}/XISOAPAdapter/MessageServlet?channel={Communication Channel}

Moreover, in the CC name in the URL above, replace the "|" character with ":" and delete * that you have for Receiver Party & Component.

Hope this helps,

Greg

[EdgarTabar]

Hi Greg,

the wsdl is not created by the PI. I get the wsdl from a third party system.

My scenario is file -> PI -> SOAP

File to PI works. PI to SOAP doesn't work.

[former_member184681]

Ok, got it now. Then make sure that your target URL in receiver CC does not end with ?WSDL.

[EdgarTabar]

Ok, got it now. Then make sure that your target URL in receiver CC does not end with ?WSDL.

The url is like this: http://server.local:8082/soap?service=WebService

[EdgarTabar]

Here the full error message, that I get in the runtime workbench / communication channel monitoring

07.02.2012 09:36:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxx.local:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

07.02.2012 09:36:15 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

07.02.2012 09:36:15 Information The message was successfully retrieved from the receive queue.

07.02.2012 09:36:15 Information Message successfully put into the queue.

07.02.2012 09:36:15 Information The message status was set to DLNG.

07.02.2012 09:36:15 Information Delivering to channel: SOAP_ReceiverChannel_xxx

07.02.2012 09:36:15 Information SOAP: request message entering the adapter with user J2EE_GUEST

07.02.2012 09:36:16 Error SOAP: call failed: java.net.ConnectException: Connection refused: connect

07.02.2012 09:36:16 Information SOAP: sending a delivery error ack ...

07.02.2012 09:36:16 Information SOAP: sent a delivery error ack

[Former Member]

Hi,

this is usually a connectivity issue in terms of the net work

confirm with your network team as to find the exact issue and a better log on this issue.

Can you check the Target URL....confirm that you have configured the receiver SOAP CC with the exact Target URL, User-id & password (if Any), and SOAP Action (if any)

[Former Member]

Hi Edgar,

In your communication channel are you using IP or hostname ?

If using IP you might be in the wrong subnetwork if using hostname, it might be that the dns is not properly configure.

Are you able to do connect from the operating system to the target server ?

Horia

[EdgarTabar]

Hi,
> this is usually a connectivity issue in terms of the net work
> confirm with your network team as to find the exact issue and a better log on this issue.
> Can you check the Target URL....confirm that you have configured the receiver SOAP CC with the exact Target URL, User-id & password (if Any), and SOAP Action (if any)

Hi,

i checked the url from the receiver channel in the internet explorer and i can see the wsdl definition of the webservice.

I don't have a user-id, passowrt or any other SOAP action.

So i guess that the port is ok.

Bye

Edgar