Testing Webservice

[Former Member]

Hello,

We are facing an issue while testing a webservice in "SOAMANAGER".

When click on Open Web Service navigator for selected binding

we are getting the following error.

Cannot download WSDL from http://XXXXXX:8030/sap/bc/srt/wsdl/bndg_DDC2B08CD6C530F1BAB1001E4FBEDA05/wsdl11/allinone/ws_policy/d...

It is not allowed to access this service. If you believe you should be able to, please contact your system administrator

But Open porttype WSDL document

Open WSDL document for selected binding options are working fine.

[Former Member]

It is not allowed to access this service. If you believe you should be able to, please contact your system administrator

This error message can appear when the host on which the tested Web service resides is not listed in the WS Navigator white list. Just add the host to the white list as described in [Configuring Web Services Navigator White List|http://help.sap.com/saphelp_nwce711/helpdata/en/30/2b552f20da49e291c9d26b675f9019/frameset.htm]

[Former Member]

Thanks very much Rossen.

I also raised a ticket with SAP, and it is also possible to set this "Web Service Navigator White List" via Visual Admin. Refer step 5 on

http://help.sap.com/saphelp_nw04/helpdata/en/7c/f257422d095542e10000000a1550b0/frameset.htm

Thanks, Matt.

[Former Member]

Matt,

Did you get any solution.

I am also in same boat.

Please reply

Thanks

JS

[Former Member]

As far as I know, by default WS Navigator can access only Web services on the local system, that is, localhost. Have you tried to add the host you are testing to the white list as described in the two links above? I think you can use wildcards for the white list, for example: 192.*

Hope this helps,

Rossen

[Former Member]

Hi Jarnail,

Yes - this started working when we ran step 5 via Visual Admin > Web Services Container > Runtime > Settings http://help.sap.com/saphelp_nw04/helpdata/en/7c/f257422d095542e10000000a1550b0/frameset.htm

5. To configure Web Service Navigator White List, in the Allowed Hosts field, enter hostnames or parts of hostnames of remote systems, to which you are allowed to connect via Web Services Navigator. To separate entries, use semicolons (, you can use an asterisk (), or a question mark (?), as wildcards. For example, if you want to enable connection to all remote systems, in the Allowed Hosts field, enter an asterisk ().

We are using our Portal as the J2EE engine for our ERP environments.

I tried using the wildcards but for some reason it did not work, so I just entered the host name of our ERP environment in the "Allowed Hosts" section.

Note also, with SPS14 an authentication check was introduced at the access of webservices, see note #1020365:

- Authentication of WS Navigator has been changed for more security. By default, it will ask for authentication (e.g. user/password). This behavior can be changed in the Visual Administrator. For more information about how to do this, please read the documentation on:

http://help.sap.com/saphelp_nw70/helpdata/EN/b7/d7baaf1481a349ab723e3acd7334b3/frameset.htm

Thanks, Matt.

[Former Member]

Thanks a lot Matt & Rossen,

My problem has been solved by entering the * in the Web service navigator list.

Thanks

Jarnail

[Former Member]

resolved the issue

[Former Member]

it seems that i have the same problem. please describe how to resolve the issue.

looking forward to your post

thnx

vasyl

[Former Member]

Hi sapuser Basis and Vasyl,

I have the same problem. Do you come up with a resolution?

We have an ERP (ABAP) system running ERP 6.0 SPS14.

I have populated the J2EE Server Access Information to use our Portal environment NW 7.0 / SPS 17, as our ERP is ABAP only.

Thanks, Matt.

[Former Member]

Hi Matt,

i didn't succeed using the Web Service Navigator, but i did successfully tested the Web Service with AltovaXML and oXygen. I personally consider this approach to be more usefull, because in this case you'll have a possibility to debug raw-SOAP-Messages.

Since you are able to "download the WSDL for the selected binding", you shouldn't experience any problem using a XML-Debugger. Try also SOAPUI, it is free.

Unfortunately i do not have any other solution for you

Regards

Vasyl