This question was originally posted on DCIM Support by jean-pierre.kull on 2018-04-19
I want to create a new Project in the SoapUI and when I click to OK i get the followi message:
What is the Problem? why I get this message?
I use SoapUI 5.2.1 and DCO 8.2.2 : are they two versions compatible?
Thanks alot or help
This comment was originally posted on DCIM Support by jean-pierre.kull on 2018-04-23
nobody has any idea what is the Problem???
This answer was originally posted on DCIM Support by Benjamin Bjørn Larsen on 2018-04-23
It would seem that you do not have access to the wsdl document, without using credentials. As Soap UI usually do not use credentials as default, you might have to use credentials for the initial setup. I do, unfortunately, not know how to do this.
I have tried to, and succeeded, in replicating your issue with the free version of SoapUI 5.3.0. However, investigating a bit through search engines, it might seem like a feature, which should be part of the Paid (Pro) version of soapUI. I cannot find information regarding, if it is limited to the Pro version or not.
Two examples of the discussion I found are:
If you don't need to send request, but, only want to view the methods in a more readable way than plain xml, you could download the wsdl and save it to a file on your own machine. Then when importing the WSDL document into SoapUI, you'll point to the file on your machine, which shouldn't be authentication protected.
You may also try to download all the XML Schema Definitions needed, add it all from you local machine, and redirect all the outgoing request to the server you need. I am unable to get this working, but, you might be better at using SoapUI than I am.
I did in addition try a workaround, of passing the username:password as part of the wsdl's url, which doesn't work either. For example by: https://username:password@serveradress/isxo/webservices/customerrelation/CustomerWebService?wsdl
In a development environment, without HTTPS, I was able to import the wsdl, and use the defined methods. If you do not need HTTPS on your DCO server, you would probably be able to reach your goal. However, this is not something we will recommend. You should not consider it, unless your are absolutely sure, that security is in place for your DCO sever, including all communication with it.
The last checks I did, was trying some of the steps commented in the following stackoverflow-thread: https://stackoverflow.com/questions/11088483/soapui-failed-to-load-url-error-when-loading-wsdl
I've been unsuccesful in my exploration, but, have tried enabling TLS, as well as looking into what the system actually outputs behind the scenes, when invoking the import of the WDSL, which results in a I/O error after a handshake_failure.
When importing it as I proposed, I am getting connection refused, probably also due to handshake_failure.
It would seem like a specific issue regarding the SoapUI tool, of which I am no power user. I do hope at least this answer will help you in your further endavours, otherwise, please feel free to reach out to us again, and I will see if I can find an expert on SoapUI.
As per my curiosity, if you'd humor me, what is the reason for using our legacy SOAP web-services, instead of our current REST API? (found at: serveraddress/api/current/)
Benjamin Bjørn Larsen
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!