I created and deployed a web services on my local server and able to get that wsdl file by calling URL http://localhost:8084/CPService?wsdl.
But the problem is when i tried to get this file via ftp from remote server it returns me time out error. However i am able to GET the default file if i issue command like "GET http://localhost:8084/CPService". So please let me know if i am able to get later file than why its giving time out error if tried to fetch "http://localhost:8084/CPService?wsdl".
means we can not get this ?wsdl file via ftp as like any other http resource. So, how can i confirm to my client that my web service is up and running. Basically our client is a telecom operator and they provides us "Delivery Notification" and we need to give them some wsdl url to which they can call and hence we can get that notification. According to them their system is not able to recall our web service. Do not know what could be the problem. Do we require any type of configuration at either side?
Is the machine where the service runs accessible from wherever the client is trying to access it? "localhost" generally indicates your own machine, which in all likelihood is not accessible from the outside (which is just as well, since it's bound to be down at random times).
Which URL did you give them? Can YOU access that URL from outside of your company network?
Yes, client is able to access that service and application is running on production server at our end. I am also able to call that service url from outside of my company network. There is no restriction at firewall also.
I have given them this URL- http://172.27.105.79:80/AstroPTCPA/PTInterface?wsdl
One more thing I have built this application using NetBeans 5.5 IDE and deployed .war file created by it on my production server. We have tomcat server running over there.
Yes, client is able to access that service and application is running on production server at our end.
That being the case, I don't understand what you mean by "how can i confirm to my client that my web service is up and running" and "According to them their system is not able to recall our web service." If the client is able to access the service, then that confirms that it is up and running, no?
Oops, sorry i wanted to say that client is able to access the machine on which service is running. And not able to access that service URL. sincere apologies