SAP and Mobility 2012 - A Developer's Perspective
-
date post
19-Oct-2014 -
Category
Technology
-
view
3.156 -
download
1
description
Transcript of SAP and Mobility 2012 - A Developer's Perspective
Mobility and SAP – A Developer’s
PerspectiveJohn Moy
March 2012
John Moy 2
Firstly, a disclaimer …
Thoughts and opinions expressed here represent my own and not those of SAP or my employer
All content provided in this presentation is for informational purposes only. The author makes no representations as to the accuracy or completeness of any information in this presentation. The author will not be liable for any errors or omissions in this presentation nor for the availability of this information.
John Moy 3
A little bit about me …
Earlier years as ABAPer, Java & Web developer, SAP Portals consultant
Worked in professional services for 15 years, now working for a large SAP customer
Current SAP UI & Mobility Architect (with SAP customer)
SCN Contributer, SAP Mentor
John Moy 4
Personal forays into Mobile …
20102009 2011 2012
My first realSmartphoneiPhone 3GS
Reading, Tutorials,Prototypes(night hours)
Uber GeekNativeiOS App
myHelp iOS App
ParcelTrack iOSNative App(prototypeonly, neverpublished)
myHelpNativeAndroidApp
Co-authorSAP MentorsOutreach iOS iPhone +iPad edition(with Bjorn Weigandand John Astill)
jQueryMobile, HTML5,PhoneGapprototypes
Experimentswith latest SUP 2.1.2using SUP DeveloperCenter (on CloudShare)
SAUGSummitPresentation(MAM, Blackbay etc.)
TechEd 2011Las Vegasco-presenter& demo(with Sascha Wenninger)
SUP 2.0 trial
John Moy 5
But …. I am not an expert!
Mobile technology is evolving so quickly that mobile developer skills and expertise depreciates at an alarming rate
John Moy 6
Mobile UI technologies, SDKs & Devices (FASTEST)
Mobile Abstraction & ManagementMiddleware (eg. SUP + Afaria)
Mobility in the context of Pace Layering
Core SAP (SLOWEST)
REST enablement (eg. NW Gateway)
Pace of mobile evolution presents an enormous challenge for SAP product development, and for mobile developers.
John Moy 7
Deconstructing SAP’s Mobile Architecture …
Core SAP BusinessSuite
SAP NetWeaverGateway
SybaseAfaria
(Mobile Device Management)
Sybase Unwired Platform
Sybase RelayServer
Other Data Sources- JDBC (Databases)- Web Services- REST Services- SAP RFC
Devices
(As at 1 March 2012)
John Moy 8
Option #1: Using MBOs + Native Clients
Core SAP BusinessSuite
SybaseAfaria
(Mobile Device Management)
Sybase Unwired Platform
Sybase RelayServer
Other Data Sources- JDBC (Databases)- Web Services- REST Services- SAP RFC
Devices
(As at 1 March 2012)Native development
using Client Object APIs
(optional) developmentin Unwired Server- Result set filters- Result checkers
- Custom transforms- Data change notifications
Design time: Generatebaseline native app code
Design time: Model mobile business objects
John Moy 9
Option #2: Using MBOs + Hybrid Web Container
Core SAP BusinessSuite
SybaseAfaria
(Mobile Device Management)
Sybase Unwired Platform
Sybase RelayServer
Other Data Sources- JDBC (Databases)- Web Services- REST Services- SAP RFC
Devices
(As at 1 March 2012)Mobile Workflow Package
Customize with HTML/CSS/Javascript
(optional) developmentin Unwired Server- Result set filters- Result checkers
- Custom transforms- Data change notifications
Design time: Model mobile business objects anddefine form layouts
John Moy 10
Option #3: Using NW Gateway + OData Channel*
Core SAP BusinessSuite
SAP NetWeaverGateway
SybaseAfaria
(Mobile Device Management)
Sybase Unwired Platform (lite)
Sybase RelayServer
Devices
(As at 1 March 2012)Native OData SDK
(iOS/Android/Blackberry)
NW Gateway Config+ ABAP (if necessary)
SUP serves as on-line data proxy
* This architecture currentlysupported only for on-line apps
Find me on Twitter@jhmoy