Skip to Content

I am attending the SAP TechEd in Las Vegas this week and I did also book myself into the ASUG Pre Conference session on SAP Mobility titled, ‘SAP Mobile Platform 3.0 – Deep Dive into the Next Generation of the Mobile Platform’.

In this blog, I will share some of the notes I made today during the All Day session which I hope will be a quick read providing the audience with insights into what SMP 3.0 is all about.

Key Message: SAP has made the first clear step towards consolidating on the mobile technology. With SMP 3.0, all the mobile features (native, agentry, mobilizer etc) are now executed on a single runtime.

1. The interesting addition I noticed was the launch of Gateway Java. With Gateway Java, now non-SAP data can be OData enabled. There was a comment that Gateway Java will be delivered on HANA Cloud Integration, SAP Process Orchestration and SMP.

There will be plugins in Eclipse for the Gateway Java (GWJ) to help speed the service implementation.

Note: For OData enabling SAP backend, the ABAP Add on, SAP Netweaver Gateway will continue to be used.

2. Everything is OData? – There was a lot of talk about OData. The message, I guess was that SAP seems to be pushing for a strong adoption of OData for most of the mobile needs.

3. Kapsel = Cordova + SAP Plugins. No offline SDK for Kapsel yet. Secure storage is a key feature that comes with Kapsel.

4. JSON is now finally supported on the OData SDK. Recommendation is to use JSON as a best practice instead of XML.

5. One SDK for all platforms. Application are clearly 3 types – Native, Hybrid and Agentry (not to forget Web)

6. Mobile Application Framework (MAF) – Provides a set of reusable components for;

a. AppUpdate

b. AuthProxy

c. EncryptedStorage

d. Logon

e. Logger

f.  Push

g. Settings

7. Client hub – Mocks Afaria like features.

8. Agentry goes OpenUI. Now make your Agentry screens skinable.

9. Death of an ‘angel’ – Agentry communication can now be HTTPs/sockets

10. Offline OData – Offline OData processing possible with the SDK. No caching on the middleware, moving to client caching.

11. MBO still supported. But recommendation is to migrate. Surely we will see the MBO concept being deprecated. New Apps to avoid MBO based approach.

12. As of today no clustering for SMP 3.0. Will be supported later.

13. CTS+ not integrated yet

14. SCC makes way for Admin logon page. Looks very familiar to the cloud version of SMP that was used on the OpenSAP course recently.

15. Gateway SP7 offers delta querying

16. Fiori from being a web app, will soon get its hybrid version via the SMP 3.0 platform.

17. AppBuilder – Now this was again very interesting. It is a Browser-based development tool for easily and quickly building SAP UI5 (HTML5/JavaScript/CSS) mobile applications.It provides designers, easy drag and drop features for development and uses the Kapsel framework for hybrid app packaging. One can also work with charts.

Hope these notes provide at a high level, features that you would see in the SMP 3.0 platform. I will update more about the platform in detail, as I get into sessions and hands on in the coming days.

You can also follow me on twitter ( @shabarishv ) as I would be tweeting during the course of this TechEd.

Feel free to post comments on your thoughts about this blog and hope this made a short but interesting read.

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Tahir Öz

    Thank you for sharing valuable information Shabarish Vijayakumar.

    A lot of changes i see 🙂 The interesting and suprise is Gateway Java (GWJ) for me. After all talk about deprecating MBO made me think of integration to non-SAP systems. Is that going to be part of SMP or a single platform as GWPA.

    Is Appbuilder going to be replacement of Hybrid app builder or it will also be a choice for hybrid apps development.

    Regards

    Tahir

    (0) 
    1. Shabarish Vijayakumar Post author

      GWJ is going to be part of the SMP 3.0 stack providing you thus an Odata enablement framework. Your mobile application will use the OData SDK, as is the case today, to work with the metadata model. Productivity accelerators (or rather the best word i think will be an eclipse plugin) will be used to model, map, implement and deploy the service.

      As for AppBuilder, it is nothing but a Wizard for creating apps with drag and drop features.

      (0) 
      1. Nagesh Caparthy

        We are really looking forward for a new world of Mobility with SAP and waiting to get the updates on SMP 3.0 in TechEd and from Ramp Up Workshops…

        -Regards,

        Nagesh

        (0) 
      1. Jose Manuel Puche

        On the other hand,

             – any news about how is the grade of decoupling between OData SDK and SMP? 

             – Could we use OData SDK to consume directly SAP Netweaver Gateway or GWJ?

             – Could OData SDK evolve independently of the SMP in order to support more devices or to include more feature and functionality without having to upgrade the platform?

        Regards,

        (0) 
  2. Krishnakumar Ramamoorthy

    Nice summary. Death of Angel is overrated 🙂 Angel has been wrapped with a web socket to provide HTTP/HTTPS capabilities. Also, I think from GW 2.0, SP5 JSON has been supported.

    Thanks for this blog

    (0) 

Leave a Reply