Looking for a good standard web API to use? Here is a detailed feature-comparison for the most common free API standards. See if features important for your project are built-in or if you will need to invent your own specification for them.
Most enterprise applications require a web service interface sooner or later. The official requirements are mostly pretty straightforward: state-of-the-art, easy-to-use, wide-spread format, easy-to-maintain (= cheap) and ideally generic. But in the past couple years, I found myself often in search for a good list of common technical requirements to pick from for a specific project. In other words, a check-list to compare different approaches. So here it goes...
Did you know, there is a 100%-native web service built into SAP NetWeaver, that performs any read-only OpenSQL statement provided? Build SQL-based data extractors, ETL-process, do rapid prototyping for UI5 apps - all without a single line of ABAP code! Here is how...
OData Services and other web services running on SAP NetWeaver use so-called CSRF tokens to secure requests, that can potentially modify data (i.e. POST, PUT, DELETE, etc.). Here is how to handle them in non-SAP applications.