Generally to download a wsdl file I would do it by displaying the wsdl in the browser.
e.g.: to download the wsdl endpoint - http://wsf.cdyne.com/WeatherWS/Weather.asmx
step 1: append the endpoint with '?wsdl' and paste the url in a browser
http://wsf.cdyne.com/WeatherWS/Weather.asmx?wsdl
step 2: save as the wsdl file shown in the local file system.
But in this case I have a secured web service, and they have provided me with the endpoint, certificates and the private keys.
If i just do the steps above I am egtting the error below
502 Bad Gateway
This server received an invalid response from a server it consulted
when acting as a proxy or gateway.
How do I download the wsdl. Please help.
Related
I am trying to use Google Cloud Endpoints as a API Gateway. For the same I created the endpoint and deployed it in a Google Run Container. When I call the url on the browser: https://... it works. However, when I try to call the same from Postman I get a 400 Bad Request error. I notice that from Postman when I try using http://... instead of https it works.
From this I concluded that perhaps this has something got to do with the SSL certificate. When I checked the certificate on the browser (by clicking on the lock icon), it shows *.a.run.app issued by GTS CA 1O1.
Then, I tried to add a Certificate in Postman (I am not sure about this). I opened Settings and tried to add a certificate by adding: *.a.run.app under host, but it did not work. I am not sure if that is the correct way to add a certificate.
Anyone can suggest what is the way to get the endpoint tested in Postman? Thanks
I have a web service(asmx) and it has a certificate for SSL. I can access this web service and see whole methods. I want to create a proxy by command prompt and I am using below code.
wsdl MyServiceAdres?wsdl
and this is the error message:
There was an error downloading 'MyServiceAdres?wsdl'.
The request was aborted: Could not create SSL/TLS secure channel.
I solved this problem. You have to save wsdl file to your local and use below code.
wsdl.exe myWebService.wsdl myXsd1.xsd myType1.xsd myXsd2.xsd ...
I am using a wsdl file sent to me via email to generate a WS client application but I wonder if it is better to have the WSDL hosted on a server and to use an URL to request it.
Actually, I requested the URL but apparently this WSDL don't have one and I can ask to create an Url for the wsdl if it is really necessary.
Can you tell me please what are the benefits of using the WSDL Url to create a WS client ?
There is not difference for you how to generate WS client. In both cases this is just WSDL document, no matter where it located is.
I see only one benefit direct accessible WSDL against WSDL file - WSDL will be always actual and and all web service changes will be reflected to WSDL document.
If you using axis 2, you can try call your webservice with ?wsdl suffix to get WSDL document
if this your webservice url
http://localhost:8080/axis2/services/StockQuoteService
This is wsdl location
http://localhost:8080/axis2/services/StockQuoteService?wsdl
I am getting the below exception when I invoke a jax ws webservice from my application deployed in WebSphere Application Server 6.1
SSL HANDSHAKE FAILURE: A signer with SubjectDN "CN=yyy.com, OU=For Intranet Use Only, OU=Web Hosting, O=xx, L=xx, ST=xx, C=xx" was sent from target host:port "*:9445". The signer may need to be added to local trust store "F://../trust.p12" . The extended error message from the SSL handshake exception is: "No trusted certificate found".
The enpoint url has https.
With the same enpoint url I am able to get a response from SOAP UI(Tool) without any certificate configuration etc..
Could you help me on this ?
I finally was able to fix this small issue.The Server certificate needs to be added to the websphere appserver truststore.This can be done from the admin console of websphere by providing the server domain and port.
I have created an Axis2 web service from Netbeans and deployed it successfully in Tomcat 6 on my web server.
When I use for instance SoapUI or Taverna to consume the web service, the server offers both HTTP and HTTPS methods to invoke it. However, using the HTTPS method renders a 404 error. (Probably because there is a server admin panel running on port 8443, but that doesn't matter right now.)
The problem is that my web service clients default to using the HTTPS service. I figured the simplest thing I could do to get the basic service to work, would be to disable the HTTPS endpoint, as the HTTP version runs flawlessly and I don't need the added security. But now I've spent hours on finding out how to do that, without success. The WSDL returned by Axis2 contains entries for HttpsSoap11Endpoint but the WSDL that's bundled in my .AAR file after the build does not.
Does anybody know how to make Axis2 offer just HTTP endpoints?
In axis2.xml, comment out the https transport receiver to disable the HTTPS endpoint.