Okay, leave the last article in this series to the sup odata SDK. As there is no ready-made development environment in hand, and this is quite simple, I will be so lazy and will not do it as an example :)
Let's talk about the main idea. The general architecture is to use SAP NetWeaver gateway to convert the bapi/RFC in the SAP system background to the restfull service of odata. The next step is simple, sup provides the odata SDK. We will introduce these libs to the specific mobile development environment. The next step is to compileCodeTo call these services. :
The general development process is also clear as follows:
We can see that using the sup odata SDK for development has the following advantages:
1) Better integration with the SAP system through Gateway
2) Make full use of the platform features of sup, including management and security.
In the latest sup Version 2.2, HWC provides the odata javascript API. We can also directly call the odata service in the HWC application :)