Most Read This Week
A Comparison of the Programming APIs Available in SAP Mobile Platform 2.3
By: Paul Horan
Sep. 22, 2013 07:45 AM
When Sybase first released the Unwired Platform in 2008, it was intended to be a complete end-to-end development environment for mobile applications. SUP developers would create the middle tier components (a.k.a. Mobile Business Objects), and the client application executables from a single, integrated Eclipse-based toolset. There was a "PowerBuilder-like" 4GL screen painter, called the Device Application Designer (or DAD), that compiled down to native Blackberry 5/6 or Windows Mobile 6.5 applications. (Yes, it's hard to imagine, but there was a time when iOS devices were not allowed to play in the Enterprise Mobile Application playground...)
Several market forces emerged around that time and started to cast doubts on the wisdom of the "complete end-to-end" strategy. Those were (in no particular order or importance):
It became fairly evident that the DAD was very dependent upon market trends and an ever-expanding variety of mobile platforms that were outside SAP's control, and was not the best long-term direction for UI tooling. As a result, the DAD got sent straight to the bit bucket with the release of SUP 2.0. The direction then became one of "openness", and embracing alternative development platforms and open industry standards.
This blog post will cover the four major API's that have been released into SMP since then. We'll cover how to generate them, what their characteristics are, when to use them (and when not to). The API's we'll cover here are:
Note: There is a 4GL programming tool for HTML5 development in SUP/SMP, called the Hybrid App Designer. I'm not discussing that tool here, because it's integrated with the platform and doesn't require the specific generation of the API libraries. And developers are hard at work crafting a new HTML5/UI5 programming tool for SMP 3.0 that will deploy hybrid apps into the Kapsel container. This tool will be called AppBuilder.
Hybrid App API
To generate the Hybrid App API from an MBO diagram, right-click the top level folder in the Workspace Navigator, and select "Generate Hybrid App API...". Figure 1 below shows where this option is located.
This opens a wizard which has two panels. The first prompts for the MBOs to include in the generation, and the second allows you to construct the message template for any Server-initiated start point.
Native Object API
To generate the Object API for a specific language and platform, right-click the Mobile Business Objects folder in the Workspace Explorer, and select "Generate Code...". This opens a wizard with three panels. The first prompts for a saved configuration profile (if there is one). The second prompts for the MBOs to include in the generated code. The final panel is the important one, and is shown below.
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads