client provided wsdl, but said not to use endpoint in wsdl. He provided a text string for the substitute endpoint.
I created a project from the wsdl, then edited the endpoint to be the new endpoint. When i submit/execute the request for testing, there is no response, no log, etc.
When i run the test case , it says it failed, but i can find no detail as to why.
I suppose the end point i edited in is defective, but how can i get the feedback that will tell me why it is invalid;
thanks for any feedback
Erm.....if I understand correctly I think you're looking at this from the wrong perspective.
I don't believe this is a SoapUI issue.
SoapUI is only going to be able to provide any workable status response if the endpoint you have specified is correct. If it is correct then you need to consider logs, look at the RAW request and response etc. to work out what's going on.
SoapUI nor any tool I wouldn't have thought would be able to give you info indicating what is wrong with your endpoint if it is incorrect.
I'd double and triple check the endpoint is correct relative to what the client provided (as well as the security/authorization options) and if you're duplicating what was supplied, you need to go back to the client who setup the endpoint for you to ensure the endpoint is correct, message body is correct (if a POST/PATCH etc.) and the security creds/Authorization settings are correct.
I'd suggest checking your network settings - are you behind a firewall? can you only connect to the endpoint from within a specific domain? etc. - but I'd expect that you'd get something in your logs (destination host unreachable or permission denied etc.) if this was the case - hence the reason I'm leaning towards confirming the endpoint details with the 3rd party (but double check your settings first though!)
Perhaps someone else has some whizzy ideas to help - but I've got nothing!
Sorry I can't be of more help,
As an addition to what @richie said you can also try to look up in the logs from the bottom left of your ReadyAPI screen.
Something must pop-up. A status code, an error, a timeout or something...
this is the only message/error i am seeing
That error indicates you might not have the keystore set up for that endpoint.
You will need the private key and certificate of the endpoint and create a keystore - there are a lot of references and I forgot the one I used but I found one site
Once you make a keystore file you have to make ReadyAPI know about it. Here is a link for that
okay, i was not aware of that. The client was sent our certificate, port info, etc, (everything needed to get through their firewall) but you are saying i still need to do that on my end??
When you say "client" it's sort of confusing because I'm used to client/server in the sense the client sends a REST request or SOAP request to a server. So I hope I am understanding you write.
I don't work with WSDL, so my advice might be totally off. But your own title of the problem is the person who sent you the endpoint does not want you to use the endpoint. The SSL-related error message you got indicated you attempted to use that endpoint. And that got my attention.
Back to your original question, I would not know how to validate their endpoint except with a ping command, since you are not supposed to use their endpoint!
Ha, sorry for the confusion, i meant a business client. So this keystone would need their certificate info, or mine. They had us provide our certificate, port info, IP, etc. They use that to let us through their firewall.
So does a keystone file typically have your own info, or the info for the firewall you are trying to get through??
Again I caution you about my lack of knowledge of working with WSDL. But yes the keystore will need their certificate info. That is, they would have to provide you a certificate and a private key fort the activity that caused you to get the SSL exception. Normally they would name the two blobs something like client.crt and client.key. At least that is what my developers give me whenever I need to test their endpoint's REST API. And your role in this case is client.
I normally combine the certificate and key into a p12-format file I think using openssl commands. Then from there use the keytool linux command to go from p12 to the keystore file.
And yes the keystore file typically has the info that your :"business client" must provide for you so that you can get through their firewall.
no worries, you're way beyond me. What you explain is interesting, because this business client had us supply them with OUR certificate, etc. So you're saying i need THEIR info as well??
The WSDL is defined with no authentication, so my understanding is that by providing them with our certificate, port info, etc, this is how they "vet" us and allow us to go through their firewall and consume their web service....