SAP interface testing Web Services, REST JSON, ODATA
Actual projects often call other system interfaces, commonly used Web Services, REST JSON, ODATA and so on.
How straightforward to determine the SAP system is not able to successfully call it?
Hard to write the code and found nowhere tone, or a variety of error.
Toss several times did not succeed, the two sides do not want to buck-passing, or PK?
In the end there is the other problem is the interface to write their own code problems, SAP can not even call?
Call failed in the end what is the reason? All kinds of speculation, can not find north ... ...
WebXml.com.cn train schedules WEB Service Provider: station information; trips inquiries; stop all trips inquiries. Train schedule data for this train schedules WEB services provided for informational purposes only, if any objection to the local railway departments have promulgated shall prevail.
WEB services using this site, please indicate the link or site: http://www.webxml.com.cn/zh_cn/index.aspx thank you for your support!
In fact, SAP has a standard test tool, as shown below
Other commonly used tools, SoapUI , Postman , XMLSpy , etc.
~status_code 200
~status_reason OK
content-type text/xml; charset=utf-8
~server_protocol HTTP/1.1
cache-control private, max-age=0
content-length 18217
server Microsoft-IIS/7.5
x-aspnet-version 2.0.50727
x-powered-by ASP.NET
date Sun, 13 Oct 2019 13:09:36 GMT
connection close
~remote_addr
~uri_scheme_expanded NONE