In addition, i am invoking the Login method and i am getting the “HTTP/1.1 404 not found” error message. my code in Java is (see image 1) and the packets on wireshar are the following (see image 2). Also, the Milestone VMS has installed the follwoing endpoing (see image 3).
I don’t know why didn’t find the method.
Please let me know if you need more information.
As I mentioned that ASMX is deprecated (can still be used) and the SVC is the path we recommend.
Also I talked with Milestone Development saying that singleWsdl could work so can you please try to test with it?
http://{host:port}/ManagementServer/ServerCommandService.svc?singleWsdl
BTW I ran into this question, it might contain valuable information here in the question, please see this -
https://developer.milestonesys.com/s/question/0D53X000067shGUSAY/generating-code-from-wsdl
Hi, when i invoke to the login method (you can see the code snippet above), I am getting the following error: “The server sent HTTP status code 415: Cannot process the message because the content type ‘text/xml;charset=“utf-8”’ was not the expected type ‘application/soap+xml; charset=utf-8’”. Also, could you please tell me how can i test the web service SOAP (some software client like SOAPUI or Postman) ??? thanks.
Please, we need to support about that. we are developing an integration between our SCADA and Milestone and we want to know if there is a flow directly through SOAP protocol, can you please send me the flow of the connection for SOAP protocol?? we have seen many documentation on it however we didn’t see nothing specificly for that. (we are implementing on Java lenguage). we don’t want to lost another day.
It might help if you responded to what is suggested and tell what you have changed. You are now getting another status code, so obviously something has changed and it is hard to provide suggestions based on unknown code.
That said, there is plenty of documentation on SOAP out there and it would not make sense to describe the protocol here, but the error you get quite clearly indicates that your HTTP header is not correct.
If you have access to a Windows machine the easiest would be to run one of our samples and the use wireshark to compare the SOAP data with what you are sending. I did this and this is the header of the request:
POST /ManagementServer/ServerCommandService.svc HTTP/1.1
Content-Type: application/soap+xml; charset=utf-8
Host: dkws-ba-03
Content-Length: 1568
Expect: 100-continue
Accept-Encoding: gzip, deflate
The easiest, though, is to find a tool that can generate a client proxy for you based on the WSDL. I am not working in Java, so unfortunately I cannot name a tool, but a quick search should easily find a few. In the past we have heard from others that some of the Java tools are having problems with WSDL referring to other WSDL and thus it might be an idea to use the singleWsdl option as suggested by Rie above, as that will give you the entire WSDL in one without any dependencies.
