Xamarin and SAP Mobile Platform for Mobile Enterprise Success - SAP Slides


Published on

Xamarin and SAP have collaborated to help developers build performant, native mobile enterprise apps. Using the new Xamarin SDK for SAP Mobile Platform, businesses gain secure access to on-premise and cloud-based data in Xamarin apps.

Bill Clark, Global Vice President of Mobile Strategy at SAP, Kiran Karunakaran, Director of Product Management at SAP, and Zack Gramana, Technical Marketing Manager at Xamarin, as they discuss the collaboration between Xamarin and SAP, demo the Xamarin Test Cloud and SAP .NET SDK from Xamarin, and walkthrough the SAP Mobile Platform.

Watch the webinar recording at:

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The OData SDK provides an open and flexible framework for native OData application development for both online and offline applications. The different components of the OData SDK are implemented as static runtime libraries and each component can be used independently.The OData SDK is used for building native mobile applications. It consists of a collection of runtime libraries and classes. The OData SDK supports Android and iOS platforms and it is based on the native device SDKs of the platforms. There is an implementation for each platform. Native applications installed on the devices allow the client application to leverage the support provided by the platform, for example:Adapt to each device’s form factor (for example, automatic layout)Exploit different input methods (for example, touch screen, keyboard or trackball)Cache data in native device data stores for better performanceTightly integrate with the features of the device
  • Xamarin and SAP Mobile Platform for Mobile Enterprise Success - SAP Slides

    1. 1. SMP 3.0 Platform Overview Kiran Karunakaran , Director, Product Management March13, 2014
    2. 2. © 2013 SAP AG. All rights reserved. 2 What is in SAP Mobile Platform v3.0 Industry’s Broadest Set of Platform Services  Core Services for enterprise-grade mobile apps  App Services for B2E, B2B and B2C mobile apps – Coupons – Banking – Loyalty  Native, hybrid, meta-data driven, mobile web and SMS app architectures  Extensible platform architecture Dramatic Developer Productivity Improvements  Common SDK for both on-premise and cloud mobile apps  WYSIWYG development environment for HTML5 apps  Bring Your Own Tools (BYOT) Support  Standards-based data integration  Robust offline/synchronization support Industry’s Most Open Platform  OData with offline support  OSGi Spring architecture  Apache Cordova hybrid container with platform services available as plug-ins  HTML5 support  HTTP REST
    3. 3. © 2013 SAP AG. All rights reserved. 3 SAP Mobile Platform v3.0 – Architecture Key Points: • No State in Mid-tier • OSGi based • Standards based protocol (OData/HTTP/s) • Single entry point • Supports most IDM providers (via extensible CSI module) • Centralized App management • Life Cycle support • Modular (supports custom extensions) • One model (OData) across entire landscape
    4. 4. © 2013 SAP AG. All rights reserved. 4 SMP server services to build apps Lean Java Server (LJS)*  E2E trace  Onboarding  Authentication/SSO  Lifecycle management  Usage reporting  Performance metrics Core Services  Coupons  Payments  Geo-location  SMS services  Push  Sync/offline  Customer and partner developed App Services Value Add to DeveloperValue Add to Administrator *SAP’s Tomcat
    5. 5. © 2013 SAP AG. All rights reserved. 5 Overview of the OData SDK
    6. 6. © 2013 SAP AG. All rights reserved. 6 Developing apps using Rest in SMP 3.0 http://infocenter.sybase.com/help/index.jsp?docset=/com.sybase.infocenter.pubs.docset-SMP-SDK- 3.0.0/doc/html/title.html&docSetID=2000 SAP Mobile Platform Server provides REST services so that applications can be built as any standard HTTP application to leverage SAP Mobile Platform Server for security and push features among others. This development approach has the following elements: • Configuring the application. • Registration (creating an application connection) • Authentication • Data consumption