Portal Web Service calling a R3 WSDL

[Former Member]

Hi,

We have an R3 web service which has a valid wsdl and it can be called. But the R3 system is behind the firewall and we want to publish this webservice throught the Portal. I have created different iViews calling the R3 wsdl but we can't see any of them from wsnavigator of the portal. (They don't show in the web service container of J2EE engine either). I have created a portal service and also an ear file and deployed them to the portal and also i created just a simple web service iView based on the R3 wsdl (a system was created for this in the portal landscape). But none of them can be accessed.

I would appreciate any help.

[Former Member]

Not solved

[Former Member]

Hi Sophia,

If you say the WSDL can be called, do you mean it can be called from a browser window?

If so, are you able to call the R3 web service from, for instance, the 'Enterprise Portal Web Services Checker' in Netweaver Developer Studio?

<i>I notice when creating web services they don't appear in the list either, but if I enter the WDSL url in the text field in wsnavigator, I can test them as well, however I found the NWDS plugin work much better</i>

[Former Member]

Hi Robin,

Yes. I can call the R3 web service through the browser and also my netweaver studio and it works and also through wasnavigator of the portal when I just put the R3 WSDL and click next. The only problem is when I create a portal web service using that and I upload to the portal I can see the new Portal web service in the wsnaviagtor of the portal and I also can't see it in the web service container of the J2EE engine.

Thanks,

Sophia

[Former Member]

...