exposed web service with SOAP UI

[Former Member]

Hi,

I created a SOAP to proxy interface in PI. I sucessfully published my web service in Service Registry. And when I use the test tool (WS Navigator) of Service Registry, my web service work perfectly! Happy!

BUT... when now, I try to call this web service from SOAP UI (last version), that does NOT work 😞

Here's what I use in SOAP UI ?

Endpoint address = http://MyHostname:55000/XISOAPAdapter/MessageServlet?senderParty=&senderService=MySender&receiverPar...http://MyNamespace/

note: I use the same user / password than this one for Service Registry.

note: my namespace has a '/' at the end.

note: PI 7.11

May I have your external point of view on what is wrong with this endpoint address?

Many thanks

Mickael

[former_member184681 · Accepted solution]

Hi Mickael,

Did you generate a .wsdl file for your web service from Sender Agreement, or imported it directly from service registry? What error do you get in SOAP UI?

Regards,

Greg

[Former Member · Accepted solution]

Hi Greg,

I get the WSDL file by using "Display WSDL" of my Sender Agreement, and use it in SOAP UI.

For Service Registry, I used menu "Publish in SR", also from my Sender Agreement.

error on SOAP UI is: org.apache.http.client.ClientProtocolException

Regards.

Mickael

[former_member184681 · Accepted solution]

Dear Mickael,

The good news is that I think this is caused by SOAP UI itself, not your PI configuration . One of my colleagues had similar error few days ago, while the same web service worked fine when called from my computer. I have two solution proposals:

1. Try using older version of SOAP UI. Personally, I am using version 3.6.1, and it works just fine.

2. If you are using 64-bit Windows, you might have to look for a dedicated SOAP UI installation, or one already containing Java VM and required libraries.

Regards,

Greg

[Former Member · Accepted solution]

Hi Greg,

I downloaded and I'm currently using version: SOAP UI 4.5.1 for a windows 64bit.

so I will try with an older version that I have somewhere... and will keep you inform.

Thanks.

Mickael

[Former Member · Accepted solution]

Hi Mickael,

I've experienced the same issue weeks ago, and as Greg says, it was a SOAP UI version kind of bug. I've downgrade to an older version of SOAP UI (in my case 3.5.1) and worked fine!

Give that a try!

cheers,

Edu

[former_member201264 · Accepted solution]

Hi,

Your end point should be as follows:

Endpoint address = http://MyHostname:55000/XISOAPAdapter/MessageServlet?channel=senderParty=&senderService=MySender&rec...

You missed "channel=" in end point.

Try with this.

regards,

Sreeni.

[former_member201264 · Accepted solution]

Hi,

Generel SOAP Sender URL should be as follows:

You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option. 

•   http://<host name>:<port name>/XISOAPAdapter/MessageServlet?channel=<party name>:<service name>:<channel name>. If you have not created a party, enter channel=:<service name>:<channel name>
•   http://<host name>:<port name>/XISOAPAdapter/MessageServlet?senderParty=<name of the sender party>&senderService=<name of the sender service>&interface=<name of the interface>&receiverParty=<name of the receiver party>&receiverService=<name of the receiver service>&interfaceNamespace=<name of the interface namespace> 

You must specify the parameters in the URL even if some of them do not have values.

Exmple if you do not have party then it should be llike  channel=:bs:cc

Regards,

Sreeni.

[Former Member · Accepted solution]

Hi Sreeni,

Endpoint address I given is this one which is written in Service Registry, as a "Target Address".

When you select your Service, then go in "Endpoint" tab, select "HTTP", well... just below we have "General" tab with this target address that I used in my SOAP UI.

I will try the two combinations(with channel or by specifying the receiver aggreement), both are empty in this address given by service registry.

Thanks.

Mickael

[Former Member]

Hi Greg and Sreeni,

many thanks, that's work !

Summary:

by using my address (*) and SOAP UI 3.6.1,  it's ok.

by using my address (*) and SOAP UI 4.5.1, I have the issue above about "apache".

(*) see Address Target in Service Registry, BUT it's mandatory to replace the "%2F%" which are inside the Namespace by "/", else I have an SOAP exception:   "com.sap.aii.af.service.cpa.CPAObjectNotFoundException : Couldn't retrieve inbound binding for the given P/S/A values".

by using the smallest address (**) and SOAP UI 3.6.1, it's ok.

by using the smallest address (**) and SOAP UI 4.5.1, I have the issue above about "apache".

(**) 1st address given by Sreeni.

by using long address (***) on SOAP UI 3.6.1, I have the same SOAP exception, so I probably did a small error... not a matter for me.

by using the long address (***) and SOAP UI 4.5.1, I have the issue above about "apache".

(***) 2nd address given by Sreeni

So In my case,

• with SOAP UI 3.6.1 (32bit) on my Windows 7 x64bit, SOAP UI works fine.
• with SOAP UI 4.5.1 (64bit) on my Windows 7 x64bit, I have an apache issue which blocks me .

I hope these details help other people...

regards

Mickael

[former_member184681]

Hi Mickael,

Good to see you sharing the final solution with other users who could possibly have same problem in the future and find this thread. Keep on doing that

Regards,

Greg