Testing Services in SOAPUI

[Former Member]

Hello,

I want to test webservices in SOAP UI. The services are provided in an abap backend, and will be consumed in a 3rd party system. The communication is via an integration server. I created . In WS navigator the service can be tested succesfully. In SOAPUI the WSDL URL is providing me the interface description - but when I try to execute it, I get an error saying "error getting response; java.net.ConnectException: Connection refused: connect". In SOAPUI the tool tip of the WSDL URL says "no endpoint set for request". Is it an autheification problem? Does anybody have a suggestion?

Kind Regards

Felix

[rajasekhar_reddy14 · Accepted solution]

SOAP UI out side of network thats why you may getting error,anyway you have tested using WS Navigator so that is fine,your development will work.

[Former Member · Accepted solution]

Thanks for the anwer. I need to make it run on SOAPUI because it is requested. You said, it might be because SOAPUI is outside the network. Do you have an idea how to solve that problem? A 3rd party consumer will also be outside the network.

[Former Member · Accepted solution]

I agree with Raja.

ps. have you set up User/Password for WS authentication in SoapUI call (in request view, under "Authentication and security-related setting" tab)?

[Former Member · Accepted solution]

Hey,

I could not find the view/tab you mentioned. I am working with the free version of SOAPUI - maybe you are refering to the pro version? But anyway, I set the userID and password in "request properties". I suppose this is the same?

[Former Member · Accepted solution]

Yes, request & password in the request properties is the same.

What is the endpoint that you are calling with SoapUI and setted on the request (it should be something like this: http://<PIhostname>:<port>/XISOAPAdapter/MessageServlet?channel=:<BusinessSyst>:<Channel>&version=3....; )???

[Former Member · Accepted solution]

The URL looks similar, but there are differences...:

https:// <piHostname> :50001/XISOAPAdapter/MessageServlet?senderParty=&senderService= <Business Component> &receiverParty=&receiverService=&interface= <Interface_out> &interfaceNamespace= <namespace>

Apart from <piHostname>, <Business Component>, <interface_out> and <namespace> this is the original URL. Something missing?

[Former Member · Accepted solution]

1) Make sure that you are calling the proxy address with HTTP:// and not the HTTPS:// one; Both are listed in the WSDL.

2) Take the whole URL and test it with an Internet browser outside the firewall

- It should ask for your credentials. If you get a success, then it should work with soapUI.

- If it fails, then you have authorization issue or your firewall is tightly blocking external entry

3) If your firewall is blocking you (which is most likely) you will have to have the network guys open a port for your 3rd party to PI's IP port.

[Former Member · Accepted solution]

I agree with John, call the http endpoint, and not the https.

[baskar_gopalakrishnan2]

>>In SOAPUI the tool tip of the WSDL URL says "no endpoint set for request".

SOAPUI is looking for the proper endpoint to consume webservice. Check in WSDL area <soap:address Location http=> and specify that URL in the soapUI endpoint fileld. Basically the connection URL is not given or invalid to test. This is not authentication problem. If you have authentication issues, You will find 401 errors.

[Former Member]

I used the URL I got via "SenderAgreement ->right click -> display wsdl" as the input for the wsdl location. The interface description could succesfully retrieved that way. This URL is specified as definition URL. Another URL was automatically set under Endpoint in the "Request Properties" setttings. Do i miss something?

Edited by: Felix F. on Jun 15, 2011 4:23 PM

Edited by: Felix F. on Jun 15, 2011 4:24 PM

[hemant_chahal]

Hi

Check if your WSDL has the end point URL.

Refer this http://help.sap.com/saphelp_nwpi711/helpdata/en/cf/9fb513ced74bbf82cac2231a358086/frameset.htm

Hemant

[Former Member]

I thought I do not need to create an endpoint in soamanager when communicating via the integration server. For the communication proxy/pi it is not required. Am I wrong?