Unable to locate the webservice in the navigator after successful deploymen

[Former Member]

I am trying to create a webservice for an EJB under a track.

Issue 1:

I was able to create the Bean Successfully , however when I tried to create a webservice for this bean I gotthis error :

ADD (FAILED: Failed to execute operations. macro execution failed [cause: Communication error [cause: number of bytes written to stream exceeds content length.]]) ws-deployment-descriptor.xml (
cpamhq-fs01\tiwarv$\.dtc\0\DCs\cpchem.com\DC_CPGrp\_comp\META-INF\ws-deployment-descriptor.xml)

Issue 2:

Another issue is that My webservice was deployed correctly but it does not show up in the navigator.

I checked the application status in NWA and it was fine.

I also had it redeployed via SDM and it was successful but still cannot locate the webserivce in navigator

I tried to access the webservice using the WSDl url , I got an error

Cannot download WSDL from http://devportal:80/WS_CPCUserGroups/Config1?wsdl: Invalid Response Code: (404) Not Found. The request URL was:"http://devportal:80/WS_CPCUserGroups/Config1?wsdl". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.

I tried creating a local project for webservice and it worked fine. but with DCs I am facing issues.

The ear file for webservice always deploys correctly but m unable to locate it in Navigator

Experts - Please Suggest

[ErvinSzolke]

one addition: you should also be able to invoke this URL in a browser:

http://devportal:80/WS_CPCUserGroups/Config1?wsdl

If this does not work, then try to use FQDN or IP, and the http port 5<instance number>00 or the corresponding port if this service is an abap webservice. If this is working in any way mentioned above, but still it does not work in wsnavigator, then see my previous response.

[ErvinSzolke]

Hi,

this happens usually if the application to which this ws belongs to is not running on the server which hosts this webservice.

Please try to restart the application on that server. Additionally if this would not help, you can attempt to restart the Webservice container service from the visual administrator.

If this does not help either and you have one of the release and SP mentioned in the below note, then please apply the fix listed there and let me know whether this helps:

#1395019 u2013 Reverse proxy support of Java Web service framework

(we have fixed such a phenomenon many times with this note)

Thank you!

Best Regards,

Ervin

[former_member214355]

Hello Vikas

I see that you have not been able to find a solution for this.

Can you provide some more information which may help the other SDN posters to assist you?

Thanks

Kenny

Moderator