When I am trying to import any 3rd party WSDL from the URL, for example : http://www.webservicex.net/currencyconvertor.asmx?wsdl , into a Web Service Execution(XML) step, I am getting the following error message :" org.apache.http.conn.ConnectTimeoutException: Connect to www.webservicex.com:80 timed out."
I tried editing the "HTTP Proxy Server Settings" in "local.properties" file by making the following changes after creating a copy of the _local file.
lisa.http.webProxy.host: My Machine IP
lisa.http.webProxy.port: the port my server listens to.
Also I have made changes in the following-
lisa.http.domain= Domain where DevTest Registry is configured
lisa.http.user= Server Username
After making these changes I am still unable to import the WSDL via URL. Kindly help.
Are you able to reach this WSDL from browser in the workstation machine?
Sorry, I am not on a network that requires a proxy server to access the internet; however, the lisa.http.webProxy.host and lisa.http.webProxy.port properties should point to your corporate proxy server hostname or IP, not your local machine IP. Similarly, the lisa.http.webProxy.ssl.host and port properties determine where the proxy server is expecting HTTPS traffic to route.
As Mohammed said, try accessing the endpoint from a browser on the machine running Workstation. If this works determine what the proxy server name/port is and configure your local.properties according to those settings. If you cannot see this from browser settings, you might run something like Wireshark to sniff the name of the proxy server when you access the wsdl from a browser.
Once you get the proxy server configured, try to access the WSDL from an HTTP/HTML step.
The output from the above execution (with no proxy) gets the wsdl.
The output from a Web Service XML step (with no proxy) also gets the wsdl.
The wsdl is being blocked by the Web Browser too, in the server machine.
Thank you. I will let you know once this is resolved.
any update on this Soumya?
Yes the issue was with our Corporate firewall which was blocking this endpoint. We had the open the port to resolve the issue. Thanks.