SlideShare a Scribd company logo
1 of 80
Technology options for
building apps with the SAP
Mobile Platform`
RIG - Paul Todd
© 2012 SAP AG. All rights reserved. 2
Agenda
Why we need a platform?
Platform components
MBO SDK
ODP SDK
Agentry platform
REST platform
Review
Deployment options
Technology options for building
applications with the
SAP Mobile Platform
Styles of Mobile Development that are Relevant Today
© 2011 SAP AG. All rights reserved. 4
Mobile application deployment - Checklist
• What is / are the problem(s) that the mobile application is trying to solve ?
• What are the systems involved ?
• What data do you need from the systems ?
• How will you secure your mobile system ?
• What are the mobile devices that will use the application ?
• How will the mobile devices connect ?
• How will you manage / upgrade the application ?
© 2011 SAP AG. All rights reserved. 5
Non-scalable approach to building Mobile Apps
Vendor 1 App
Vendor 2 App
Vendor 3 App
Vendor n App
Vendor 1 Server
Vendor 2 Server
Vendor 3 Server
Vendor n Server
Backend System
1
Backend System
2
Backend System
3
Device T1
Device T2
Device T2
Device T1
Device T2
Device T2
Device T1
Device T2
Device T2
Device T1
Device T2
Device T2
© 2011 SAP AG. All rights reserved. 6
Mobile Enablement Functions
Understanding the total picture
Mobile Enablement
Functions
Represents 80% of the total cost of
implementing your own infrastructure
Costly and time consuming
Requires skill sets which are not core to
business
Secure connectivity to business systems
End to end security and authentication
Application versioning and lifecycle management
Multi-device and multi-OS platform support
Usage analytics and reporting
End to end traceability
Represents 20% of the total cost of deploying a mobile
strategy
Can be accelerated with partners and off-the-shelf
applications
© 2011 SAP AG. All rights reserved. 7
The power of a platform
Optimization, reusability, maintainability, scalability
There is no one-size-fits-all approach, but there are several use cases with different recurring
architecture patterns that must be supported consistently
Services
platform
for mobile
B2E
B2B
B2C
Challenges and requirements Qualities and features
Skill-set diversity
Application diversity
Rapid evolution
Heterogeneous landscape
Enable world-class tools
Reusable platform services
Device/platform agnostic
Embrace open standards
© 2011 SAP AG. All rights reserved. 8
The platform value proposition
Open platform
millions of developers
Flexible framework
native, HTML, or business
analysts
SDK and tools
fast and productive
Reusable services and
frameworks
consistent and extensible
Developer
Open platform
easily extensible
Seamless integration and
centralized management
optimized TCO
Industry standard security
assurance and control
App platform + app mgmt
end-to-end mobile lifecycle
management
Admin
Platform approach
consistent app experience
Self service portal
user empowerment
BYOD enabled
user choice
Enterprise app store
discover new apps and
capabilities
User
© 2011 SAP AG. All rights reserved. 9
Mobile Platform Development Tools / SDK
B2E apps
SAP’s end-to-end solution strategy
A comprehensive enterprise mobile portfolio
SAP/Sybase build Ecosystem
B2C apps
Partner
Banking Retail
Travel &
hospitality
Media &
entertainment
Telco
Automotive
SAP Mobile Platform
Industry LoB Analytics PartnerCustom
Mobile application platform with development tools/SDK and framework
Mobile Enterprise
Application Platform (MEAP)
Mobile Consumer
Application Platform (MCAP)
On-premise SAP HANA Cloud
Sencha
Appcelerator
PhoneGap
© 2011 SAP AG. All rights reserved. 10
SAP Mobile Platform
Master brand for unified platform
In 2013, the SAP Mobile Platform will deliver multiple options for customers:
Deployment
B2E / B2C
App architectures
AgentryMobiliserSUP
SAP Mobile Platform
Native
Hybrid
Metadata driven
SMS-based
Cloud version
On-premise version
Enterprise edition
Consumer editionConsumerEnterprise
SAP Mobile Platform
iOS Android BlackBerry Windows 8
© 2011 SAP AG. All rights reserved. 11
SAP Mobile Platform - Overview
Challenges to mobility solutions
Lack of upfront planning – Inability or high cost to expand
Lack of integrated solutions
Managing and tracking device applications
Reporting and troubleshooting
And more…
SAP Mobile Platform supports…
Supports variety of backend EIS and various device types
Provides different types of authentication modules
Centralized management of device applications
Reporting and troubleshooting
Options for Offline, Hybrid, Online mobile applications
© 2011 SAP AG. All rights reserved. 12
SAP Mobile Platform
Product description
SAP Mobile Platform is a mobile application development platform that enables developers to simply and
quickly build B2E, B2B and B2C applications that connect business data to mobile workers on any device,
at any time
Connect to any SAP or non-SAP data source and
application
Create amazing mobile applications using native and
third-party IDEs and SAP SDKs and libraries:
authentication, data integration, synchronization,
3D visualization, and reusable components
Deploy native, hybrid and metadata driven mobile
applications from the device of their choice:
iOS / Android / BlackBerry / Windows 8 /
Windows Phone 8 / Windows Mobile
SAP Mobile Platform
SAP
HANASAP Systems 3rd Party
Native, Hybrid, Meta-Data Driven, SMS Apps
iOS Android BlackBerry Windows 8
© 2011 SAP AG. All rights reserved. 13
SMP 2.3 Software Architecture
© 2011 SAP AG. All rights reserved. 14
Client Paradigms
Why we support them all?
Player
Native
HWC
SMS
Agentry 6.x
SMP 2.2
Mobiliser 5.x
Agentry
Mobiliser 5.x
Agentry
Mobiliser
SUP SUP
SMP 2.3
Q3 2013
SMP 3.0 RTC
Q4 2013
© 2011 SAP AG. All rights reserved. 15
Architectural Break-down of a Mobile Solution
•Player
•Hybrid Web Container
•Native
•SMS
•Development Tools
•User Onboarding
•Authentication & Authorization
•Connection Management.
•Application Settings
•Resource Bundles
•Encryption Services
•Central Monitoring, Logging,
Tracing
•Web-services
•Synchronization
•SMS
•W3C SOAP
•OData
•JSON
•Mobilink Protocol
•Angel Protocol
•SAP JCO
•JDBC
Mobile
Application
Consumption
Model
Mobile
Enablement
Functions
UI
Implementation
Model
© 2011 SAP AG. All rights reserved. 16
Player Type Applications
Pros:
Design Once Deploy Many
Auto App Updates
Codeless
Offline Capable
Cons:
On Device Complex Calculations
tedious
UI Control Set Limited
Device support limited
Good Use Cases:
Field Force Automation
Sale Force Automations
Bad Use Cases:
Novel UI Requirements
Consumer Oriented
Player
© 2011 SAP AG. All rights reserved. 17
Hybrid Web Container Applications
Pros:
Design Once Deploy Many
Massive Development Community
Large Device Support
Cons:
No implicit Sync Model for Offline
Apple Rules
Resource Intensive - > User XP
Good Use Cases:
Lightweight workflow apps
Online lookup apps
Consumer Oriented
Bad Use Cases:
Heavy process driven apps with
offline requirements
Hybrid Web
Container
© 2011 SAP AG. All rights reserved. 18
Native Applications
Pros:
Maximise Performance
Maximise User XP
Direct Access to Peripherals
Cons:
Expensive
Specialized Skills
Rewrite for each Device Type
Updates require redeploy
Good Use Cases:
Specialized Interfaces (3D)
Process Intensive Apps
UX important
Bad Use Cases:
Consumer oriented (cost)
Native
© 2011 SAP AG. All rights reserved. 19
SMS Applications
Pros:
Large Device Support
No App Deployment
Simple and Intuitive
Cons:
User XP Limited
Spam
Cost to user
Good Use Cases:
mCommerce Apps
Loyalty Apps
Utility Apps
Bad Use Cases:
Complex process driven
SMS
SMP 2.3 Architecture
© 2011 SAP AG. All rights reserved. 21
SMP High Level Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SMS
SMP Platform Components
© 2011 SAP AG. All rights reserved. 22
SMP SDKs and Development Tools
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
Platform Services Mobile SDK’s
Technology Options
© 2011 SAP AG. All rights reserved. 24
SMP Player Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
Platform Services Mobile SDK’s
© 2011 SAP AG. All rights reserved. 25
SMP Player Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
NativeMeta Data
Repository
JCO
JDBC
Agentry Editor
SCC
Java
Integration
Code
Agentry
Runtime
Agentry
Addon
Triggers, Stored Proc
© 2011 SAP AG. All rights reserved. 26
SMP HWC Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
Platform Services Mobile SDK’s
© 2011 SAP AG. All rights reserved. 27
SMP HWC Open Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SCC
NWGW
Any JavaScript UI
Framework
© 2011 SAP AG. All rights reserved. 28
SMP HWC MBO Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SCC
SAP Mobile SDK +
Any UI Framework
Cache
DB
JS API
MBO
Operations
Queries
Load
© 2011 SAP AG. All rights reserved. 29
SMP Native Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
Platform Services Mobile SDK’s
© 2011 SAP AG. All rights reserved. 30
SMP Native Open Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SCC
NWGW
Any Native
Framework
© 2011 SAP AG. All rights reserved. 31
SMP Native ODP Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SCC
SAP Mobile SDK +
Native
ODP API
OData Proxy
NWGW
© 2011 SAP AG. All rights reserved. 32
SMP Native MBO Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SCC
SAP Mobile SDK +
Native Framework
Cache
DB
Object API
MBO
Operations
Queries
Load
Sync
MBO Technology
© 2011 SAP AG. All rights reserved. 34
Mobile Business Object - MBO
Overview
• Form the business logic by defining the data you want to use from your back-
end system and exposing it through your mobile application or Hybrid App.
• MBO development involves defining object data models with back-end EIS
connections, attributes, operations, and relationships that allow filtered data
sets to be synchronized to mobile devices.
• Are built by developers who are familiar with the data and transactional
requirements of the app, and how that app connects to existing data sources.
• An MBO is derived from a data source, such as a database server, Web
service, or SAP® server.
• Are deployed to SAP Mobile Server, and accessed from mobile device
application client code generated from SAP Mobile WorkSpace.
© 2011 SAP AG. All rights reserved. 35
Mobile Business Object - MBO
Overview
• MBOs are created using the SAP
Mobile WorkSpace graphical tools
• Are reusable, allowing you to
leverage business logic or
processes across multiple device
types.
• Future-proof: when new device
types are added, existing MBOs
can be used.
• Provide a layer of abstraction from
the SAP Mobile Server interaction
with heterogeneous back-
ends/devices, as shown in
diagram.
© 2011 SAP AG. All rights reserved. 36
Mobile Business Objects - MBO
Architecture
Device
Business Suite & 3rd Party
Backend
SMP
MBORepository
Device
optimized
MBO
Admin/Config Tool
DevTool for Content
DistributionRules
DataConsolidation
(Native & Container/HTML5)
Synchronization&Messaging
DevTool Apps
© 2011 SAP AG. All rights reserved. 37
SMP MBO-based App Development
Native Object API:
MBO configures server for synchronization, client DB & objects, and generates query
methods in Native Object API
Develop
Mobile
Business
Objects
SMP Development Task Flow
1
Deploy Mobile
Business
Objects to
Unwired Server
2
Generate MBO
API from MBO
Diagram
3 Develop
Native
Application
using MBO
Native SDK
4
Install native
application
and test in
Simulator
5
Install native
application
and test on
Device
6
© 2011 SAP AG. All rights reserved. 38
MBO – When to use
Use the MBO approach when....
The App is mission-critical
The usage scenario is more complex.
Users can work on data while fully-offline
Server and client updates are synchronized
Very good for large data volumes and disconnected environments
The App has to handle data from multiple EIS’s
© 2011 SAP AG. All rights reserved. 39
MBO – When not to use
Do not use the MBO approach when...
Large user base e.g. Consumer Apps
Online Apps – possible but with a lot of overhead
HWC Technology
© 2011 SAP AG. All rights reserved. 41
Hybrid Web Container - HWC
Overview
• Support simple business processes, such as approvals and requests
• Use MBOs to facilitate connection with a variety of enterprise systems
• A hybrid web container is developed and deployed to a device, then one or
more workflows are deployed to the container
• Supports mobile workflow enablement, which enables mobile device users to
operate as workflow participants, allowing the mobile user to start and respond
to back-end enterprise requests within a generic framework
• Data is made available using a request-response pattern, without
synchronization
• Manage a low data volume
• Avoid the need for long-lasting, offline, stateful transactions
© 2011 SAP AG. All rights reserved. 42
Hybrid Web Container - HWC
Architecture
• Is the runtime on the device within which Hybrid Apps are executed.
• Is a native app designed to process generic function calls from a Hybrid App.
• Embeds a browser control supplied by the device OS, which allows you to build
applications with simplicity of Web development but utilize the power of native
device services.
• Allows you to create a single HTML5 application that performs advanced,
device specific operations on all the different devices.
• Write Hybrid Apps in standards-based HTML5, JavaScript and Cascading Style
Sheets (CSS). These are technologies familiar to web developers.
• This enables Web developers to incorporate open source frameworks and also
select their preferred development environment, for example, Sencha and
JQuery Mobile.
© 2011 SAP AG. All rights reserved. 43
Hybrid Web Container - HWC
Architecture
© 2011 SAP AG. All rights reserved. 44
HWC-based Apps Development
HTML5/JS Container API:
MBO configures server mappings, creates HTML5 storage key-value structure, and
generates request methods in JavaScript API
Develop
Mobile
Business
Objects
SMP Development Task Flow
1
Deploy Mobile
Business
Objects to
Unwired Server
2
Generate
JavaScript API
from MBO
Diagram
3
Develop Hybrid
Application in
UI5, JQM or
Sencha Touch
4
Deploy to
SCC and test
in HWC in
Simulator
5
Deploy to
SCC and
test in HWC
on Device
6
© 2011 SAP AG. All rights reserved. 45
HWC– When to use
Use the HWC approach when....
Need to manage a low data volume
Provide a simple user experience
Implement simple business logic
Avoid the need for long-lasting, offline, stateful transactions
Ensure secure and reliable transport of data
© 2011 SAP AG. All rights reserved. 46
HWC– When not to use
Do not use the HWC approach when...
Need large data volumes on the device
Complex workflow
Complex User Interfaces/Experience
Access to native API’s such as NFC
OData Proxy SDK
© 2011 SAP AG. All rights reserved. 48
OData Proxy - ODP
Overview
The SMP OData SDK offers a range of libraries and APIs which you can use to
create and manage applications.
• Supports Android, BlackBerry 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 given platform
• Cache data in native device data stores for better performance
• Works directly with backend so updates work without delay and possible
synchronization issues an no business data on the mobile device.
• Uses SMP Messaging Protocol that always compressed and strongly
encrypted
© 2011 SAP AG. All rights reserved. 49
OData Proxy - ODP
Architecture
SDK native libraries for iOS, Android and Blackberry.
Composed of a number of components:
Connectivity - provides support to connect to SMP server
Parser – provides support for parsing JSON and XML Odata data
Cache – reduce network traffic by caching queries on the device
Supportability – options to integrate with Solution Manager and Afaria
Persistence – allow the storing of data securely on the device.
© 2011 SAP AG. All rights reserved. 50
OData Proxy - ODP
Architecture
Client
Specialized Native Applications
OData SDK
(Persistence, Caching, ODATA parsing)
Messaging
(Secure Connectivity, Reliable Messaging)
SMP Server
Messaging
(Authentication, Mobile Data Delivery(IMO), Push, Message Handlers)
SAP Gateway
Registry
(App, User, Subscription, Configuration)
Http(s) Proxy Connector
(Tunneling & URL Re-write, Subscriptions)
SMP Glue
(Authentication, On-Boarding, Connectivity)
Push Notifications
Requests & Response
© 2011 SAP AG. All rights reserved. 51
ODP-based Apps Development
Native API:
ODP API provides support operations and management functionality to ease
development
Develop
backend
OData
SMP Development Task Flow
1
Create
registration in
SMP
2
Develop
application
3
Test
application
4
Deploy onto
device
5
© 2011 SAP AG. All rights reserved. 52
ODP– When to use
Use the ODP approach when....
No offline synchronization capability is required
Ensure secure and reliable transport of data
Talking to an internal backend OData service
Require enterprise management features
© 2011 SAP AG. All rights reserved. 53
ODP– When not to use
Do not use the ODP approach when...
Offline access is required.
Application uses complex state based transactions
No Application Lifecycle Management is required
No requirement to securely store data and credentials
Player Technology
© 2011 SAP AG. All rights reserved. 55
Agentry Architecture Fundamentals
Agentry ServerAgentry
Development
Server
Application
Definitions
Java Logic
Agentry Server
Administration Client
Server
Port
S
T
E
P
S
Agentry Editor
Eclipse
Publish application into the
Agentry Server
Connection/Steps can be:
Java VM
HTTP XML
SQL Database
File System
Agentry Client
installed on the
mobile device
ATE - Agentry Test
Environment
ANGEL
© 2011 SAP AG. All rights reserved. 56
Agentry Player
Overview - Client
Client Player features
Prebuilt free downloadable binary from app stores.
Blackbox approach, no need to change player or rebuilt it.
Customization only through metadata (No container customization)
Task centric rather than experience centric
Data stored in files
Clients for iOS, Android, Windows Mobile, Blackberry
© 2011 SAP AG. All rights reserved. 57
Agentry Player
Overview - Middleware
Middleware features
Primarily a messaging server , Synchronization is entirely application dependent
No database/caching in middleware,
Custom protocol with device communication on TCP
One server instance hosts exactly one application
Scaling through multiple instances using a load balancer (no clustering)
© 2011 SAP AG. All rights reserved. 58
Agentry Player
Overview - Backend
Backend features
Supports SQL, Java, HTTP-XML backends.
Expects data model to be defined in backend in CRUD pattern.
Expects delta computation to be managed in backend in a predefined way.
© 2011 SAP AG. All rights reserved. 59
Standard
BAPIs
exchange
data
FIREWALL
Bluetooth (PAN)
Network (LAN)
WAN
Wireless LAN
Wireless WAN
Satellite
Dial-Up
Docking Cradle
IRDA
Solution Architecture – SAP
Enterprise Meta-Data Driven Technology
SAP ERP®
SAP CRM®
Configuration
Module
Administration
Module
Namespace
Agentry Editor
Eclipse
FIREW
ALL
METADATA
(Application Definition)
System Connection
Communication
Agentry Development
Server
Enhanced
TCP/IP
Agentry Client
Application Logic
UI
Application Flow
Configuration
Peripheral Integration
Communication
Storage
SAP Add-On
© 2011 SAP AG. All rights reserved. 60
SMP Player-based Apps Development
Player application
Metadata driven solution means faster deployment and testing.
Do backend
customizations
SMP Development Task Flow
1
Build workflow
And screens
2
Deploy to dev
environment
3
Test in dev
environment
with ATE and
Devices
4
Move
application
from dev to
production
5
Roll out to
all users
6
© 2011 SAP AG. All rights reserved. 61
Player– When to use
Use the Player approach when....
User experience is less important
Native look and feel is desired
Desire to scale up the backend and keep the mobile middleware very light.
Coding skills, particularly for mobile are lacking
Well understood processes requiring quick automation
© 2011 SAP AG. All rights reserved. 62
Player– When not to use
Do not use the player approach when...
Workflow and business processes outside of the standard offerings.
Complex User Interfaces/Experience.
Access to API’s outside the documented player API’s is required.
Client OS is not supported by player yet.
REST SDK Technology
© 2011 SAP AG. All rights reserved. 64
REST SDK
Overview
HTTP application management solution for scenarios where there is no
client (yet) available (e.g. Windows 8)
Not an Enterprise OData service or Synchronization solution
Programming Language agnostic
Open standards – uses standards based HTTP
OData like API to SMP server
Per user Registration, Authentication and Configuration
Access backend Odata Feeds through SMP server
© 2011 SAP AG. All rights reserved. 65
REST API
Architecture
The REST API can be found here:
http://tinyurl.com/k78revl
In particular look at the
reference subsection,
most important document for this SDK
The application initially connects to the server, an HTTP header with the connection id is
returned. This ID is stored and reused later on when making any connection to the server.
When accessing any backend data the header is supplied with the request and then the
request is routed through the application definition on the SMP server and so is controlled
both for anonymous connections and for registered connections.
Settings and customizations can also be applied at the user or group level.
© 2011 SAP AG. All rights reserved. 66
REST– When to use
Use the REST approach when....
Need for Application Lifecycle Management
User access control
Reduce exposure of gateway server to internet
Technology solution prevents use of other SMP platform technologies
© 2011 SAP AG. All rights reserved. 67
REST– When not to use
Do not use the REST approach when...
Need a synchronization solution.
No offline support.
No need for ALM.
Backend is already visible to the internet.
© 2011 SAP AG. All rights reserved. 68
SMP REST-based Apps Development
Ensure programming API has access to HTTP headers and cookies
Register
application in
SMP
SMP Development Task Flow
1
Test SMP
Access in
REST testing
tool
2
Integrate into
application
3
Deploy
application to
app stores
4
Review
© 2011 SAP AG. All rights reserved. 70
“Which SMP Technology should I use?”
Review: Evaluate the Use Case
SDK Application
Type
Use Case
Native
Object
API
Native
• iOS
• BlackBerry
• Windows/WM
• Android
Offline applications
• Typically mission-critical and more complex.
• Users can work on data while fully-offline
• Server and client updates are synchronized
• Very good for large data volumes and disconnected environments
OData
SDK
Native
• iOS
• BlackBerry
• Android
Online applications
• Applications targeting SAP Netweaver Gateway
• Very good for ‘lightweight’ services-based development scenarios
in native apps.
• No synchronization or MBOs
Hybrid
Apps
Web
• HTML5/JS/CSS
Native Container
• iOS
• Android
• BlackBerry
• Windows Mobile
Online+, with Push
• Very good for lightweight HTML cross-platform development
scenarios with access to native.
• Contains features that allow server-driven push notifications.
• Allows users to act on approvals while offline, and push those
updates to the server when the device regains connectivity.
• In 2.1, can support Camera; in 2.1.1 can support other device
APIs.
© 2011 SAP AG. All rights reserved. 71
“Which SMP Technology should I use? (Part 2)”
Review: Evaluate the Use Case
SDK Application
Type
Use Case
REST
API
Any Online applications
• Applications targeting SAP Netweaver Gateway
• No synchronization or MBOs
• Focus on Application Management
Player Native
• iOS
• BlackBerry
• Android
• Windows Mobile
Online applications
• Applications based ERP & CRM
• Very good for metadata driven/code less solutions
• Optimized workflow for various device profiles.
SMP 2.3 Deployment Options
© 2011 SAP AG. All rights reserved. 73
Common Deployment Questions
Can you deploy SMP servers on VM infrastructure?
Windows or Linux?
How Many Machines?
What should the Spec Be?
How do we scale?
How do we deal with the DMZ?
What about SSL?
© 2011 SAP AG. All rights reserved. 74
Deployment on a Developer Machine
Laptop Spec:
Mid to High End
Recommended:
Quad Core (64 bit)
8GB Ram
Windows 7 Pro 64bit
40Gb Free
© 2011 SAP AG. All rights reserved. 75
Deployment of a Single Node Development Server
Server Spec:
Mid to High End
Recommended:
Quad Core (64 bit)
8GB Ram
Windows 2008 R2 64bit
40Gb Free
Development Server
© 2011 SAP AG. All rights reserved. 76
Deployment of a Multi Node QA Environment
Quad Core (64 bit)
8GB Ram
Windows 2008 R2
64bit
40Gb Free
Cluster Node 1
Data Tier
Cluster Node 1
Reverse Proxy
Quad Core (64 bit)
8GB Ram
Windows 2008 R2
64bit
100 Gb Free
© 2011 SAP AG. All rights reserved. 77
MS Cluster in Active Active
Deployment of a Multi Tier Production Environment
Quad Core (64 bit)
8GB Ram
Windows 2008 R2
64bit
40Gb FreeCluster
Node 1
RP1
NON VM MS
CLUSTER AA
Quad Core (64 bit)
8GB Ram
Windows 2008 R2
64bit
Cluster
Node 2
Cluster
Node 3
RP2
Load Balancer
© 2011 SAP AG. All rights reserved. 78
Sizing guidelines
Best resource is our Sizing Guide on SDN
http://tinyurl.com/lopygzn
Covers sizing recommendations for:
MBO’s
OData Proxy
Agentry
EIS
Thank You!
Any questions drop me an email
paul.todd@sap.com
© 2011 SAP AG. All rights reserved. 80
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
© 2011 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any
other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP® product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind,
either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct,
special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.

More Related Content

What's hot

Build Multi-Channel Solutions using MDK
Build Multi-Channel Solutions using MDKBuild Multi-Channel Solutions using MDK
Build Multi-Channel Solutions using MDKJitendra Kansal
 
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019Jitendra Kansal
 
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCN
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCNBuild & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCN
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCNJitendra Kansal
 
SAP Cloud Platform SDK for iOS-Latest Updates
SAP Cloud Platform SDK for iOS-Latest UpdatesSAP Cloud Platform SDK for iOS-Latest Updates
SAP Cloud Platform SDK for iOS-Latest UpdatesJitendra Kansal
 
A walkthrough on SAP Cloud Platform Mobile Services
A walkthrough on SAP Cloud Platform Mobile Services A walkthrough on SAP Cloud Platform Mobile Services
A walkthrough on SAP Cloud Platform Mobile Services Jitendra Kansal
 
Sap Mobility Presentation 5 1 2012
Sap Mobility Presentation 5 1 2012Sap Mobility Presentation 5 1 2012
Sap Mobility Presentation 5 1 2012nerb13
 
MADP - Mobile Application Development Platform - CRE8 Brasil MEAP
MADP - Mobile Application Development Platform - CRE8 Brasil MEAPMADP - Mobile Application Development Platform - CRE8 Brasil MEAP
MADP - Mobile Application Development Platform - CRE8 Brasil MEAPVictor Sebastian
 
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0Innovapptive Global Solutions Pvt Ltd.
 
Enterprise mobility MADP MEAP MCAP struggles and approaches
Enterprise mobility MADP MEAP MCAP struggles and approachesEnterprise mobility MADP MEAP MCAP struggles and approaches
Enterprise mobility MADP MEAP MCAP struggles and approachesANOOP KUMAR P
 
Open Source solution for Mobile Enterprise Application System
Open Source solution for Mobile Enterprise Application SystemOpen Source solution for Mobile Enterprise Application System
Open Source solution for Mobile Enterprise Application Systemhearme limited company
 
APIs: State of the Union - Ross Garrett @ AppsWorld 2014
APIs: State of the Union - Ross Garrett @ AppsWorld 2014APIs: State of the Union - Ross Garrett @ AppsWorld 2014
APIs: State of the Union - Ross Garrett @ AppsWorld 2014CA API Management
 
The API Opportunity: Crossing the Digital Divide
The API Opportunity: Crossing the Digital DivideThe API Opportunity: Crossing the Digital Divide
The API Opportunity: Crossing the Digital DivideCA Technologies
 
5 Steps for End-to-End Mobile Security with Consumer Apps
5 Steps for End-to-End Mobile Security with Consumer Apps5 Steps for End-to-End Mobile Security with Consumer Apps
5 Steps for End-to-End Mobile Security with Consumer AppsCA API Management
 
agados app engine platform Intro
agados app engine platform Introagados app engine platform Intro
agados app engine platform IntroYongkyoo Park
 
Sap fiori-ux-architecture-for-s4h
Sap fiori-ux-architecture-for-s4hSap fiori-ux-architecture-for-s4h
Sap fiori-ux-architecture-for-s4hAkhilendra Singh
 

What's hot (20)

Build Multi-Channel Solutions using MDK
Build Multi-Channel Solutions using MDKBuild Multi-Channel Solutions using MDK
Build Multi-Channel Solutions using MDK
 
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019
Build Cross-Platform application using Mobile Development Kit - #sitBCN 2019
 
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCN
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCNBuild & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCN
Build & Operate Cross-Platform Micro Apps with SAP Mobile Cards - #sitBCN
 
SAP Cloud Platform SDK for iOS-Latest Updates
SAP Cloud Platform SDK for iOS-Latest UpdatesSAP Cloud Platform SDK for iOS-Latest Updates
SAP Cloud Platform SDK for iOS-Latest Updates
 
A walkthrough on SAP Cloud Platform Mobile Services
A walkthrough on SAP Cloud Platform Mobile Services A walkthrough on SAP Cloud Platform Mobile Services
A walkthrough on SAP Cloud Platform Mobile Services
 
Sap Mobility Presentation 5 1 2012
Sap Mobility Presentation 5 1 2012Sap Mobility Presentation 5 1 2012
Sap Mobility Presentation 5 1 2012
 
MADP - Mobile Application Development Platform - CRE8 Brasil MEAP
MADP - Mobile Application Development Platform - CRE8 Brasil MEAPMADP - Mobile Application Development Platform - CRE8 Brasil MEAP
MADP - Mobile Application Development Platform - CRE8 Brasil MEAP
 
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0
Innovative mobile apps – migrate MBO apps to SAP Mobile Platform 3.0
 
Enterprise mobility MADP MEAP MCAP struggles and approaches
Enterprise mobility MADP MEAP MCAP struggles and approachesEnterprise mobility MADP MEAP MCAP struggles and approaches
Enterprise mobility MADP MEAP MCAP struggles and approaches
 
SAP and Startup Intro
SAP and Startup Intro SAP and Startup Intro
SAP and Startup Intro
 
Mobile Enterprise Application vision
Mobile Enterprise Application visionMobile Enterprise Application vision
Mobile Enterprise Application vision
 
Mobile Rerence Applications: The end to end Integration
Mobile Rerence Applications: The end to end IntegrationMobile Rerence Applications: The end to end Integration
Mobile Rerence Applications: The end to end Integration
 
Open Source solution for Mobile Enterprise Application System
Open Source solution for Mobile Enterprise Application SystemOpen Source solution for Mobile Enterprise Application System
Open Source solution for Mobile Enterprise Application System
 
CA API Gateway
CA API GatewayCA API Gateway
CA API Gateway
 
Autodesk Technical Webinar: SAP Mobile Platform
Autodesk Technical Webinar: SAP Mobile PlatformAutodesk Technical Webinar: SAP Mobile Platform
Autodesk Technical Webinar: SAP Mobile Platform
 
APIs: State of the Union - Ross Garrett @ AppsWorld 2014
APIs: State of the Union - Ross Garrett @ AppsWorld 2014APIs: State of the Union - Ross Garrett @ AppsWorld 2014
APIs: State of the Union - Ross Garrett @ AppsWorld 2014
 
The API Opportunity: Crossing the Digital Divide
The API Opportunity: Crossing the Digital DivideThe API Opportunity: Crossing the Digital Divide
The API Opportunity: Crossing the Digital Divide
 
5 Steps for End-to-End Mobile Security with Consumer Apps
5 Steps for End-to-End Mobile Security with Consumer Apps5 Steps for End-to-End Mobile Security with Consumer Apps
5 Steps for End-to-End Mobile Security with Consumer Apps
 
agados app engine platform Intro
agados app engine platform Introagados app engine platform Intro
agados app engine platform Intro
 
Sap fiori-ux-architecture-for-s4h
Sap fiori-ux-architecture-for-s4hSap fiori-ux-architecture-for-s4h
Sap fiori-ux-architecture-for-s4h
 

Similar to SAP Mobile Platform: Virtual Bootcamp – How to build your Enterprise Mobile Apps Part 2

How to-choose-the-right-technology-architecture-for-your-mobile-application
How to-choose-the-right-technology-architecture-for-your-mobile-applicationHow to-choose-the-right-technology-architecture-for-your-mobile-application
How to-choose-the-right-technology-architecture-for-your-mobile-applicationlverb
 
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...hpcmitresearch
 
Why an innovative mobile strategy needs a robust API
Why an innovative mobile strategy needs a robust APIWhy an innovative mobile strategy needs a robust API
Why an innovative mobile strategy needs a robust APIManmohan Gupta
 
HTML5 Mobile Web Framework - High Level Design
HTML5 Mobile Web Framework - High Level DesignHTML5 Mobile Web Framework - High Level Design
HTML5 Mobile Web Framework - High Level DesignThanh Nguyen
 
Why an Innovative Mobile Strategy Requires a Robust API
Why an Innovative Mobile Strategy Requires a Robust API Why an Innovative Mobile Strategy Requires a Robust API
Why an Innovative Mobile Strategy Requires a Robust API Software AG
 
Webinar sap mobile apps service2 media
Webinar sap mobile apps   service2 media Webinar sap mobile apps   service2 media
Webinar sap mobile apps service2 media Service2Media
 
Webinar SAP connected mobile apps with the app lifecycle platform
Webinar SAP connected mobile apps with the app lifecycle platformWebinar SAP connected mobile apps with the app lifecycle platform
Webinar SAP connected mobile apps with the app lifecycle platformService2Media
 
App forum2015 London - RhoMobile Update
App forum2015 London - RhoMobile UpdateApp forum2015 London - RhoMobile Update
App forum2015 London - RhoMobile Updaterobgalvinjr
 
Soa architect summit mobile 2013_mar [compatibility mode]
Soa architect summit mobile 2013_mar [compatibility mode]Soa architect summit mobile 2013_mar [compatibility mode]
Soa architect summit mobile 2013_mar [compatibility mode]Sreeni Pamidala
 
IBM MobileFirst Technical Overview
IBM MobileFirst Technical OverviewIBM MobileFirst Technical Overview
IBM MobileFirst Technical Overviewibmmobile
 
Ibm mobile first platform presentation refresh 05 18-mc
Ibm mobile first platform presentation refresh 05 18-mcIbm mobile first platform presentation refresh 05 18-mc
Ibm mobile first platform presentation refresh 05 18-mcSaranga Tripathy
 
Mobility Trends | Customer Conversation Deck
Mobility Trends |  Customer Conversation DeckMobility Trends |  Customer Conversation Deck
Mobility Trends | Customer Conversation DeckSagar Mody
 
Red Hat Mobile
Red Hat MobileRed Hat Mobile
Red Hat MobileRed Hat
 
10 Key Criteria for Mobile Platform Selection
10 Key Criteria for Mobile Platform Selection10 Key Criteria for Mobile Platform Selection
10 Key Criteria for Mobile Platform SelectionJason Haygood
 
A DevOps Approach for Building 100 iOS Apps
A DevOps Approach for Building 100 iOS AppsA DevOps Approach for Building 100 iOS Apps
A DevOps Approach for Building 100 iOS AppsTechWell
 
June 25 webcast adding mobile to power applications
June 25 webcast   adding mobile to power applicationsJune 25 webcast   adding mobile to power applications
June 25 webcast adding mobile to power applicationsLeigh Williamson
 

Similar to SAP Mobile Platform: Virtual Bootcamp – How to build your Enterprise Mobile Apps Part 2 (20)

Android @ Neev
Android @ NeevAndroid @ Neev
Android @ Neev
 
How to-choose-the-right-technology-architecture-for-your-mobile-application
How to-choose-the-right-technology-architecture-for-your-mobile-applicationHow to-choose-the-right-technology-architecture-for-your-mobile-application
How to-choose-the-right-technology-architecture-for-your-mobile-application
 
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...
Rapidvalue whitepaper-howtochoosetherightarchitectureforyourmobileapplication...
 
IBM MobileFirst Platform v7 Tech Overview
IBM MobileFirst Platform v7 Tech OverviewIBM MobileFirst Platform v7 Tech Overview
IBM MobileFirst Platform v7 Tech Overview
 
Why an innovative mobile strategy needs a robust API
Why an innovative mobile strategy needs a robust APIWhy an innovative mobile strategy needs a robust API
Why an innovative mobile strategy needs a robust API
 
HTML5 Mobile Web Framework - High Level Design
HTML5 Mobile Web Framework - High Level DesignHTML5 Mobile Web Framework - High Level Design
HTML5 Mobile Web Framework - High Level Design
 
Why an Innovative Mobile Strategy Requires a Robust API
Why an Innovative Mobile Strategy Requires a Robust API Why an Innovative Mobile Strategy Requires a Robust API
Why an Innovative Mobile Strategy Requires a Robust API
 
Webinar sap mobile apps service2 media
Webinar sap mobile apps   service2 media Webinar sap mobile apps   service2 media
Webinar sap mobile apps service2 media
 
Webinar SAP connected mobile apps with the app lifecycle platform
Webinar SAP connected mobile apps with the app lifecycle platformWebinar SAP connected mobile apps with the app lifecycle platform
Webinar SAP connected mobile apps with the app lifecycle platform
 
App forum2015 London - RhoMobile Update
App forum2015 London - RhoMobile UpdateApp forum2015 London - RhoMobile Update
App forum2015 London - RhoMobile Update
 
Soa architect summit mobile 2013_mar [compatibility mode]
Soa architect summit mobile 2013_mar [compatibility mode]Soa architect summit mobile 2013_mar [compatibility mode]
Soa architect summit mobile 2013_mar [compatibility mode]
 
IBM MobileFirst Technical Overview
IBM MobileFirst Technical OverviewIBM MobileFirst Technical Overview
IBM MobileFirst Technical Overview
 
Ibm mobile first platform presentation refresh 05 18-mc
Ibm mobile first platform presentation refresh 05 18-mcIbm mobile first platform presentation refresh 05 18-mc
Ibm mobile first platform presentation refresh 05 18-mc
 
Mobility Trends | Customer Conversation Deck
Mobility Trends |  Customer Conversation DeckMobility Trends |  Customer Conversation Deck
Mobility Trends | Customer Conversation Deck
 
Red Hat Mobile
Red Hat MobileRed Hat Mobile
Red Hat Mobile
 
10 Key Criteria for Mobile Platform Selection
10 Key Criteria for Mobile Platform Selection10 Key Criteria for Mobile Platform Selection
10 Key Criteria for Mobile Platform Selection
 
Mobile development capability doc
Mobile development capability docMobile development capability doc
Mobile development capability doc
 
Mobile Development Capability
Mobile Development Capability Mobile Development Capability
Mobile Development Capability
 
A DevOps Approach for Building 100 iOS Apps
A DevOps Approach for Building 100 iOS AppsA DevOps Approach for Building 100 iOS Apps
A DevOps Approach for Building 100 iOS Apps
 
June 25 webcast adding mobile to power applications
June 25 webcast   adding mobile to power applicationsJune 25 webcast   adding mobile to power applications
June 25 webcast adding mobile to power applications
 

More from SAP PartnerEdge program for Application Development

More from SAP PartnerEdge program for Application Development (20)

SAP HANA Cloud Platform Expert Session - SAP HANA Cloud Platform Analytics
SAP HANA Cloud Platform Expert Session - SAP HANA Cloud Platform AnalyticsSAP HANA Cloud Platform Expert Session - SAP HANA Cloud Platform Analytics
SAP HANA Cloud Platform Expert Session - SAP HANA Cloud Platform Analytics
 
SUSE Technical Webinar – Get started with creating Lumira CVOM extensions -- ...
SUSE Technical Webinar – Get started with creating Lumira CVOM extensions -- ...SUSE Technical Webinar – Get started with creating Lumira CVOM extensions -- ...
SUSE Technical Webinar – Get started with creating Lumira CVOM extensions -- ...
 
SUSE Technical Webinar – Get started with creating Design Studio extensions -...
SUSE Technical Webinar – Get started with creating Design Studio extensions -...SUSE Technical Webinar – Get started with creating Design Studio extensions -...
SUSE Technical Webinar – Get started with creating Design Studio extensions -...
 
SUSE Technical Webinar: Build HANA Apps in the Framework of the SAP and SUSE ...
SUSE Technical Webinar: Build HANA Apps in the Framework of the SAP and SUSE ...SUSE Technical Webinar: Build HANA Apps in the Framework of the SAP and SUSE ...
SUSE Technical Webinar: Build HANA Apps in the Framework of the SAP and SUSE ...
 
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
 
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
SUSE Technical Webinar: Developing Fiori & GWPAM Apps on HANA (SAP and SUSE C...
 
SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Ca...
SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Ca...SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Ca...
SUSE Technical Webinar: Build B1 apps in the Framework of the SAP and SUSE Ca...
 
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
 
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
Google Technical Webinar - Building Mashups with Google Apps and SAP, using S...
 
SUSE Technical Webinar: Introduction to Business Intelligence - the SAP and S...
SUSE Technical Webinar: Introduction to Business Intelligence - the SAP and S...SUSE Technical Webinar: Introduction to Business Intelligence - the SAP and S...
SUSE Technical Webinar: Introduction to Business Intelligence - the SAP and S...
 
SUSE Technical Webinar: Build Cloud Apps with SAP HANA Cloud Platform
SUSE Technical Webinar: Build Cloud Apps with SAP HANA Cloud PlatformSUSE Technical Webinar: Build Cloud Apps with SAP HANA Cloud Platform
SUSE Technical Webinar: Build Cloud Apps with SAP HANA Cloud Platform
 
Partner with SAP to Develop Mobile apps and capture the Mobile Market Opportu...
Partner with SAP to Develop Mobile apps and capture the Mobile Market Opportu...Partner with SAP to Develop Mobile apps and capture the Mobile Market Opportu...
Partner with SAP to Develop Mobile apps and capture the Mobile Market Opportu...
 
Microsoft Technical Webinar - New devices for Windows 8 and Windows Phone 8, ...
Microsoft Technical Webinar - New devices for Windows 8 and Windows Phone 8, ...Microsoft Technical Webinar - New devices for Windows 8 and Windows Phone 8, ...
Microsoft Technical Webinar - New devices for Windows 8 and Windows Phone 8, ...
 
Autodesk Technical Webinar: SAP Business One
Autodesk Technical Webinar: SAP Business OneAutodesk Technical Webinar: SAP Business One
Autodesk Technical Webinar: SAP Business One
 
Microsoft Technical Webinar: Doing more with MS Office, SharePoint and Visual...
Microsoft Technical Webinar: Doing more with MS Office, SharePoint and Visual...Microsoft Technical Webinar: Doing more with MS Office, SharePoint and Visual...
Microsoft Technical Webinar: Doing more with MS Office, SharePoint and Visual...
 
Mobile Apps 4 Charity
Mobile Apps 4 CharityMobile Apps 4 Charity
Mobile Apps 4 Charity
 
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - S...
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - S...Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - S...
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - S...
 
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - P...
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - P...Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - P...
Microsoft Technical Webinar: UX/UI Design for Windows 8 & Windows Phone 8 - P...
 
Autodesk Technical Webinar: SAP HANA in-memory database
Autodesk Technical Webinar: SAP HANA in-memory databaseAutodesk Technical Webinar: SAP HANA in-memory database
Autodesk Technical Webinar: SAP HANA in-memory database
 
Autodesk Technical Webinar: SAP NetWeaver Gateway Part 3
Autodesk Technical Webinar: SAP NetWeaver Gateway Part 3Autodesk Technical Webinar: SAP NetWeaver Gateway Part 3
Autodesk Technical Webinar: SAP NetWeaver Gateway Part 3
 

Recently uploaded

GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxNeo4j
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FESTBillieHyde
 
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechWebinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechProduct School
 
Graphene Quantum Dots-Based Composites for Biomedical Applications
Graphene Quantum Dots-Based Composites for  Biomedical ApplicationsGraphene Quantum Dots-Based Composites for  Biomedical Applications
Graphene Quantum Dots-Based Composites for Biomedical Applicationsnooralam814309
 
My key hands-on projects in Quantum, and QAI
My key hands-on projects in Quantum, and QAIMy key hands-on projects in Quantum, and QAI
My key hands-on projects in Quantum, and QAIVijayananda Mohire
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxSatishbabu Gunukula
 
EMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarEMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarThousandEyes
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsDianaGray10
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and businessFrancesco Corti
 
UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1DianaGray10
 
Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosErol GIRAUDY
 
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInOutage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInThousandEyes
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptxHansamali Gamage
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc
 
Where developers are challenged, what developers want and where DevEx is going
Where developers are challenged, what developers want and where DevEx is goingWhere developers are challenged, what developers want and where DevEx is going
Where developers are challenged, what developers want and where DevEx is goingFrancesco Corti
 
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdf
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdfQ4 2023 Quarterly Investor Presentation - FINAL - v1.pdf
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdfTejal81
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveIES VE
 
The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)IES VE
 

Recently uploaded (20)

GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FEST
 
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechWebinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
 
Graphene Quantum Dots-Based Composites for Biomedical Applications
Graphene Quantum Dots-Based Composites for  Biomedical ApplicationsGraphene Quantum Dots-Based Composites for  Biomedical Applications
Graphene Quantum Dots-Based Composites for Biomedical Applications
 
My key hands-on projects in Quantum, and QAI
My key hands-on projects in Quantum, and QAIMy key hands-on projects in Quantum, and QAI
My key hands-on projects in Quantum, and QAI
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptx
 
EMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarEMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? Webinar
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projects
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and business
 
UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1
 
Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenarios
 
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInOutage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx
 
SheDev 2024
SheDev 2024SheDev 2024
SheDev 2024
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
 
Where developers are challenged, what developers want and where DevEx is going
Where developers are challenged, what developers want and where DevEx is goingWhere developers are challenged, what developers want and where DevEx is going
Where developers are challenged, what developers want and where DevEx is going
 
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdf
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdfQ4 2023 Quarterly Investor Presentation - FINAL - v1.pdf
Q4 2023 Quarterly Investor Presentation - FINAL - v1.pdf
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
 
The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)
 

SAP Mobile Platform: Virtual Bootcamp – How to build your Enterprise Mobile Apps Part 2

  • 1. Technology options for building apps with the SAP Mobile Platform` RIG - Paul Todd
  • 2. © 2012 SAP AG. All rights reserved. 2 Agenda Why we need a platform? Platform components MBO SDK ODP SDK Agentry platform REST platform Review Deployment options
  • 3. Technology options for building applications with the SAP Mobile Platform Styles of Mobile Development that are Relevant Today
  • 4. © 2011 SAP AG. All rights reserved. 4 Mobile application deployment - Checklist • What is / are the problem(s) that the mobile application is trying to solve ? • What are the systems involved ? • What data do you need from the systems ? • How will you secure your mobile system ? • What are the mobile devices that will use the application ? • How will the mobile devices connect ? • How will you manage / upgrade the application ?
  • 5. © 2011 SAP AG. All rights reserved. 5 Non-scalable approach to building Mobile Apps Vendor 1 App Vendor 2 App Vendor 3 App Vendor n App Vendor 1 Server Vendor 2 Server Vendor 3 Server Vendor n Server Backend System 1 Backend System 2 Backend System 3 Device T1 Device T2 Device T2 Device T1 Device T2 Device T2 Device T1 Device T2 Device T2 Device T1 Device T2 Device T2
  • 6. © 2011 SAP AG. All rights reserved. 6 Mobile Enablement Functions Understanding the total picture Mobile Enablement Functions Represents 80% of the total cost of implementing your own infrastructure Costly and time consuming Requires skill sets which are not core to business Secure connectivity to business systems End to end security and authentication Application versioning and lifecycle management Multi-device and multi-OS platform support Usage analytics and reporting End to end traceability Represents 20% of the total cost of deploying a mobile strategy Can be accelerated with partners and off-the-shelf applications
  • 7. © 2011 SAP AG. All rights reserved. 7 The power of a platform Optimization, reusability, maintainability, scalability There is no one-size-fits-all approach, but there are several use cases with different recurring architecture patterns that must be supported consistently Services platform for mobile B2E B2B B2C Challenges and requirements Qualities and features Skill-set diversity Application diversity Rapid evolution Heterogeneous landscape Enable world-class tools Reusable platform services Device/platform agnostic Embrace open standards
  • 8. © 2011 SAP AG. All rights reserved. 8 The platform value proposition Open platform millions of developers Flexible framework native, HTML, or business analysts SDK and tools fast and productive Reusable services and frameworks consistent and extensible Developer Open platform easily extensible Seamless integration and centralized management optimized TCO Industry standard security assurance and control App platform + app mgmt end-to-end mobile lifecycle management Admin Platform approach consistent app experience Self service portal user empowerment BYOD enabled user choice Enterprise app store discover new apps and capabilities User
  • 9. © 2011 SAP AG. All rights reserved. 9 Mobile Platform Development Tools / SDK B2E apps SAP’s end-to-end solution strategy A comprehensive enterprise mobile portfolio SAP/Sybase build Ecosystem B2C apps Partner Banking Retail Travel & hospitality Media & entertainment Telco Automotive SAP Mobile Platform Industry LoB Analytics PartnerCustom Mobile application platform with development tools/SDK and framework Mobile Enterprise Application Platform (MEAP) Mobile Consumer Application Platform (MCAP) On-premise SAP HANA Cloud Sencha Appcelerator PhoneGap
  • 10. © 2011 SAP AG. All rights reserved. 10 SAP Mobile Platform Master brand for unified platform In 2013, the SAP Mobile Platform will deliver multiple options for customers: Deployment B2E / B2C App architectures AgentryMobiliserSUP SAP Mobile Platform Native Hybrid Metadata driven SMS-based Cloud version On-premise version Enterprise edition Consumer editionConsumerEnterprise SAP Mobile Platform iOS Android BlackBerry Windows 8
  • 11. © 2011 SAP AG. All rights reserved. 11 SAP Mobile Platform - Overview Challenges to mobility solutions Lack of upfront planning – Inability or high cost to expand Lack of integrated solutions Managing and tracking device applications Reporting and troubleshooting And more… SAP Mobile Platform supports… Supports variety of backend EIS and various device types Provides different types of authentication modules Centralized management of device applications Reporting and troubleshooting Options for Offline, Hybrid, Online mobile applications
  • 12. © 2011 SAP AG. All rights reserved. 12 SAP Mobile Platform Product description SAP Mobile Platform is a mobile application development platform that enables developers to simply and quickly build B2E, B2B and B2C applications that connect business data to mobile workers on any device, at any time Connect to any SAP or non-SAP data source and application Create amazing mobile applications using native and third-party IDEs and SAP SDKs and libraries: authentication, data integration, synchronization, 3D visualization, and reusable components Deploy native, hybrid and metadata driven mobile applications from the device of their choice: iOS / Android / BlackBerry / Windows 8 / Windows Phone 8 / Windows Mobile SAP Mobile Platform SAP HANASAP Systems 3rd Party Native, Hybrid, Meta-Data Driven, SMS Apps iOS Android BlackBerry Windows 8
  • 13. © 2011 SAP AG. All rights reserved. 13 SMP 2.3 Software Architecture
  • 14. © 2011 SAP AG. All rights reserved. 14 Client Paradigms Why we support them all? Player Native HWC SMS Agentry 6.x SMP 2.2 Mobiliser 5.x Agentry Mobiliser 5.x Agentry Mobiliser SUP SUP SMP 2.3 Q3 2013 SMP 3.0 RTC Q4 2013
  • 15. © 2011 SAP AG. All rights reserved. 15 Architectural Break-down of a Mobile Solution •Player •Hybrid Web Container •Native •SMS •Development Tools •User Onboarding •Authentication & Authorization •Connection Management. •Application Settings •Resource Bundles •Encryption Services •Central Monitoring, Logging, Tracing •Web-services •Synchronization •SMS •W3C SOAP •OData •JSON •Mobilink Protocol •Angel Protocol •SAP JCO •JDBC Mobile Application Consumption Model Mobile Enablement Functions UI Implementation Model
  • 16. © 2011 SAP AG. All rights reserved. 16 Player Type Applications Pros: Design Once Deploy Many Auto App Updates Codeless Offline Capable Cons: On Device Complex Calculations tedious UI Control Set Limited Device support limited Good Use Cases: Field Force Automation Sale Force Automations Bad Use Cases: Novel UI Requirements Consumer Oriented Player
  • 17. © 2011 SAP AG. All rights reserved. 17 Hybrid Web Container Applications Pros: Design Once Deploy Many Massive Development Community Large Device Support Cons: No implicit Sync Model for Offline Apple Rules Resource Intensive - > User XP Good Use Cases: Lightweight workflow apps Online lookup apps Consumer Oriented Bad Use Cases: Heavy process driven apps with offline requirements Hybrid Web Container
  • 18. © 2011 SAP AG. All rights reserved. 18 Native Applications Pros: Maximise Performance Maximise User XP Direct Access to Peripherals Cons: Expensive Specialized Skills Rewrite for each Device Type Updates require redeploy Good Use Cases: Specialized Interfaces (3D) Process Intensive Apps UX important Bad Use Cases: Consumer oriented (cost) Native
  • 19. © 2011 SAP AG. All rights reserved. 19 SMS Applications Pros: Large Device Support No App Deployment Simple and Intuitive Cons: User XP Limited Spam Cost to user Good Use Cases: mCommerce Apps Loyalty Apps Utility Apps Bad Use Cases: Complex process driven SMS
  • 21. © 2011 SAP AG. All rights reserved. 21 SMP High Level Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SMS SMP Platform Components
  • 22. © 2011 SAP AG. All rights reserved. 22 SMP SDKs and Development Tools DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native Platform Services Mobile SDK’s
  • 24. © 2011 SAP AG. All rights reserved. 24 SMP Player Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native Platform Services Mobile SDK’s
  • 25. © 2011 SAP AG. All rights reserved. 25 SMP Player Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container NativeMeta Data Repository JCO JDBC Agentry Editor SCC Java Integration Code Agentry Runtime Agentry Addon Triggers, Stored Proc
  • 26. © 2011 SAP AG. All rights reserved. 26 SMP HWC Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native Platform Services Mobile SDK’s
  • 27. © 2011 SAP AG. All rights reserved. 27 SMP HWC Open Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SCC NWGW Any JavaScript UI Framework
  • 28. © 2011 SAP AG. All rights reserved. 28 SMP HWC MBO Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SCC SAP Mobile SDK + Any UI Framework Cache DB JS API MBO Operations Queries Load
  • 29. © 2011 SAP AG. All rights reserved. 29 SMP Native Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native Platform Services Mobile SDK’s
  • 30. © 2011 SAP AG. All rights reserved. 30 SMP Native Open Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SCC NWGW Any Native Framework
  • 31. © 2011 SAP AG. All rights reserved. 31 SMP Native ODP Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SCC SAP Mobile SDK + Native ODP API OData Proxy NWGW
  • 32. © 2011 SAP AG. All rights reserved. 32 SMP Native MBO Application Software Architecture DB ERP RFC SOAP WS RESTful WS OData WS Player Hybrid Web Container Native SCC SAP Mobile SDK + Native Framework Cache DB Object API MBO Operations Queries Load Sync
  • 34. © 2011 SAP AG. All rights reserved. 34 Mobile Business Object - MBO Overview • Form the business logic by defining the data you want to use from your back- end system and exposing it through your mobile application or Hybrid App. • MBO development involves defining object data models with back-end EIS connections, attributes, operations, and relationships that allow filtered data sets to be synchronized to mobile devices. • Are built by developers who are familiar with the data and transactional requirements of the app, and how that app connects to existing data sources. • An MBO is derived from a data source, such as a database server, Web service, or SAP® server. • Are deployed to SAP Mobile Server, and accessed from mobile device application client code generated from SAP Mobile WorkSpace.
  • 35. © 2011 SAP AG. All rights reserved. 35 Mobile Business Object - MBO Overview • MBOs are created using the SAP Mobile WorkSpace graphical tools • Are reusable, allowing you to leverage business logic or processes across multiple device types. • Future-proof: when new device types are added, existing MBOs can be used. • Provide a layer of abstraction from the SAP Mobile Server interaction with heterogeneous back- ends/devices, as shown in diagram.
  • 36. © 2011 SAP AG. All rights reserved. 36 Mobile Business Objects - MBO Architecture Device Business Suite & 3rd Party Backend SMP MBORepository Device optimized MBO Admin/Config Tool DevTool for Content DistributionRules DataConsolidation (Native & Container/HTML5) Synchronization&Messaging DevTool Apps
  • 37. © 2011 SAP AG. All rights reserved. 37 SMP MBO-based App Development Native Object API: MBO configures server for synchronization, client DB & objects, and generates query methods in Native Object API Develop Mobile Business Objects SMP Development Task Flow 1 Deploy Mobile Business Objects to Unwired Server 2 Generate MBO API from MBO Diagram 3 Develop Native Application using MBO Native SDK 4 Install native application and test in Simulator 5 Install native application and test on Device 6
  • 38. © 2011 SAP AG. All rights reserved. 38 MBO – When to use Use the MBO approach when.... The App is mission-critical The usage scenario is more complex. Users can work on data while fully-offline Server and client updates are synchronized Very good for large data volumes and disconnected environments The App has to handle data from multiple EIS’s
  • 39. © 2011 SAP AG. All rights reserved. 39 MBO – When not to use Do not use the MBO approach when... Large user base e.g. Consumer Apps Online Apps – possible but with a lot of overhead
  • 41. © 2011 SAP AG. All rights reserved. 41 Hybrid Web Container - HWC Overview • Support simple business processes, such as approvals and requests • Use MBOs to facilitate connection with a variety of enterprise systems • A hybrid web container is developed and deployed to a device, then one or more workflows are deployed to the container • Supports mobile workflow enablement, which enables mobile device users to operate as workflow participants, allowing the mobile user to start and respond to back-end enterprise requests within a generic framework • Data is made available using a request-response pattern, without synchronization • Manage a low data volume • Avoid the need for long-lasting, offline, stateful transactions
  • 42. © 2011 SAP AG. All rights reserved. 42 Hybrid Web Container - HWC Architecture • Is the runtime on the device within which Hybrid Apps are executed. • Is a native app designed to process generic function calls from a Hybrid App. • Embeds a browser control supplied by the device OS, which allows you to build applications with simplicity of Web development but utilize the power of native device services. • Allows you to create a single HTML5 application that performs advanced, device specific operations on all the different devices. • Write Hybrid Apps in standards-based HTML5, JavaScript and Cascading Style Sheets (CSS). These are technologies familiar to web developers. • This enables Web developers to incorporate open source frameworks and also select their preferred development environment, for example, Sencha and JQuery Mobile.
  • 43. © 2011 SAP AG. All rights reserved. 43 Hybrid Web Container - HWC Architecture
  • 44. © 2011 SAP AG. All rights reserved. 44 HWC-based Apps Development HTML5/JS Container API: MBO configures server mappings, creates HTML5 storage key-value structure, and generates request methods in JavaScript API Develop Mobile Business Objects SMP Development Task Flow 1 Deploy Mobile Business Objects to Unwired Server 2 Generate JavaScript API from MBO Diagram 3 Develop Hybrid Application in UI5, JQM or Sencha Touch 4 Deploy to SCC and test in HWC in Simulator 5 Deploy to SCC and test in HWC on Device 6
  • 45. © 2011 SAP AG. All rights reserved. 45 HWC– When to use Use the HWC approach when.... Need to manage a low data volume Provide a simple user experience Implement simple business logic Avoid the need for long-lasting, offline, stateful transactions Ensure secure and reliable transport of data
  • 46. © 2011 SAP AG. All rights reserved. 46 HWC– When not to use Do not use the HWC approach when... Need large data volumes on the device Complex workflow Complex User Interfaces/Experience Access to native API’s such as NFC
  • 48. © 2011 SAP AG. All rights reserved. 48 OData Proxy - ODP Overview The SMP OData SDK offers a range of libraries and APIs which you can use to create and manage applications. • Supports Android, BlackBerry 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 given platform • Cache data in native device data stores for better performance • Works directly with backend so updates work without delay and possible synchronization issues an no business data on the mobile device. • Uses SMP Messaging Protocol that always compressed and strongly encrypted
  • 49. © 2011 SAP AG. All rights reserved. 49 OData Proxy - ODP Architecture SDK native libraries for iOS, Android and Blackberry. Composed of a number of components: Connectivity - provides support to connect to SMP server Parser – provides support for parsing JSON and XML Odata data Cache – reduce network traffic by caching queries on the device Supportability – options to integrate with Solution Manager and Afaria Persistence – allow the storing of data securely on the device.
  • 50. © 2011 SAP AG. All rights reserved. 50 OData Proxy - ODP Architecture Client Specialized Native Applications OData SDK (Persistence, Caching, ODATA parsing) Messaging (Secure Connectivity, Reliable Messaging) SMP Server Messaging (Authentication, Mobile Data Delivery(IMO), Push, Message Handlers) SAP Gateway Registry (App, User, Subscription, Configuration) Http(s) Proxy Connector (Tunneling & URL Re-write, Subscriptions) SMP Glue (Authentication, On-Boarding, Connectivity) Push Notifications Requests & Response
  • 51. © 2011 SAP AG. All rights reserved. 51 ODP-based Apps Development Native API: ODP API provides support operations and management functionality to ease development Develop backend OData SMP Development Task Flow 1 Create registration in SMP 2 Develop application 3 Test application 4 Deploy onto device 5
  • 52. © 2011 SAP AG. All rights reserved. 52 ODP– When to use Use the ODP approach when.... No offline synchronization capability is required Ensure secure and reliable transport of data Talking to an internal backend OData service Require enterprise management features
  • 53. © 2011 SAP AG. All rights reserved. 53 ODP– When not to use Do not use the ODP approach when... Offline access is required. Application uses complex state based transactions No Application Lifecycle Management is required No requirement to securely store data and credentials
  • 55. © 2011 SAP AG. All rights reserved. 55 Agentry Architecture Fundamentals Agentry ServerAgentry Development Server Application Definitions Java Logic Agentry Server Administration Client Server Port S T E P S Agentry Editor Eclipse Publish application into the Agentry Server Connection/Steps can be: Java VM HTTP XML SQL Database File System Agentry Client installed on the mobile device ATE - Agentry Test Environment ANGEL
  • 56. © 2011 SAP AG. All rights reserved. 56 Agentry Player Overview - Client Client Player features Prebuilt free downloadable binary from app stores. Blackbox approach, no need to change player or rebuilt it. Customization only through metadata (No container customization) Task centric rather than experience centric Data stored in files Clients for iOS, Android, Windows Mobile, Blackberry
  • 57. © 2011 SAP AG. All rights reserved. 57 Agentry Player Overview - Middleware Middleware features Primarily a messaging server , Synchronization is entirely application dependent No database/caching in middleware, Custom protocol with device communication on TCP One server instance hosts exactly one application Scaling through multiple instances using a load balancer (no clustering)
  • 58. © 2011 SAP AG. All rights reserved. 58 Agentry Player Overview - Backend Backend features Supports SQL, Java, HTTP-XML backends. Expects data model to be defined in backend in CRUD pattern. Expects delta computation to be managed in backend in a predefined way.
  • 59. © 2011 SAP AG. All rights reserved. 59 Standard BAPIs exchange data FIREWALL Bluetooth (PAN) Network (LAN) WAN Wireless LAN Wireless WAN Satellite Dial-Up Docking Cradle IRDA Solution Architecture – SAP Enterprise Meta-Data Driven Technology SAP ERP® SAP CRM® Configuration Module Administration Module Namespace Agentry Editor Eclipse FIREW ALL METADATA (Application Definition) System Connection Communication Agentry Development Server Enhanced TCP/IP Agentry Client Application Logic UI Application Flow Configuration Peripheral Integration Communication Storage SAP Add-On
  • 60. © 2011 SAP AG. All rights reserved. 60 SMP Player-based Apps Development Player application Metadata driven solution means faster deployment and testing. Do backend customizations SMP Development Task Flow 1 Build workflow And screens 2 Deploy to dev environment 3 Test in dev environment with ATE and Devices 4 Move application from dev to production 5 Roll out to all users 6
  • 61. © 2011 SAP AG. All rights reserved. 61 Player– When to use Use the Player approach when.... User experience is less important Native look and feel is desired Desire to scale up the backend and keep the mobile middleware very light. Coding skills, particularly for mobile are lacking Well understood processes requiring quick automation
  • 62. © 2011 SAP AG. All rights reserved. 62 Player– When not to use Do not use the player approach when... Workflow and business processes outside of the standard offerings. Complex User Interfaces/Experience. Access to API’s outside the documented player API’s is required. Client OS is not supported by player yet.
  • 64. © 2011 SAP AG. All rights reserved. 64 REST SDK Overview HTTP application management solution for scenarios where there is no client (yet) available (e.g. Windows 8) Not an Enterprise OData service or Synchronization solution Programming Language agnostic Open standards – uses standards based HTTP OData like API to SMP server Per user Registration, Authentication and Configuration Access backend Odata Feeds through SMP server
  • 65. © 2011 SAP AG. All rights reserved. 65 REST API Architecture The REST API can be found here: http://tinyurl.com/k78revl In particular look at the reference subsection, most important document for this SDK The application initially connects to the server, an HTTP header with the connection id is returned. This ID is stored and reused later on when making any connection to the server. When accessing any backend data the header is supplied with the request and then the request is routed through the application definition on the SMP server and so is controlled both for anonymous connections and for registered connections. Settings and customizations can also be applied at the user or group level.
  • 66. © 2011 SAP AG. All rights reserved. 66 REST– When to use Use the REST approach when.... Need for Application Lifecycle Management User access control Reduce exposure of gateway server to internet Technology solution prevents use of other SMP platform technologies
  • 67. © 2011 SAP AG. All rights reserved. 67 REST– When not to use Do not use the REST approach when... Need a synchronization solution. No offline support. No need for ALM. Backend is already visible to the internet.
  • 68. © 2011 SAP AG. All rights reserved. 68 SMP REST-based Apps Development Ensure programming API has access to HTTP headers and cookies Register application in SMP SMP Development Task Flow 1 Test SMP Access in REST testing tool 2 Integrate into application 3 Deploy application to app stores 4
  • 70. © 2011 SAP AG. All rights reserved. 70 “Which SMP Technology should I use?” Review: Evaluate the Use Case SDK Application Type Use Case Native Object API Native • iOS • BlackBerry • Windows/WM • Android Offline applications • Typically mission-critical and more complex. • Users can work on data while fully-offline • Server and client updates are synchronized • Very good for large data volumes and disconnected environments OData SDK Native • iOS • BlackBerry • Android Online applications • Applications targeting SAP Netweaver Gateway • Very good for ‘lightweight’ services-based development scenarios in native apps. • No synchronization or MBOs Hybrid Apps Web • HTML5/JS/CSS Native Container • iOS • Android • BlackBerry • Windows Mobile Online+, with Push • Very good for lightweight HTML cross-platform development scenarios with access to native. • Contains features that allow server-driven push notifications. • Allows users to act on approvals while offline, and push those updates to the server when the device regains connectivity. • In 2.1, can support Camera; in 2.1.1 can support other device APIs.
  • 71. © 2011 SAP AG. All rights reserved. 71 “Which SMP Technology should I use? (Part 2)” Review: Evaluate the Use Case SDK Application Type Use Case REST API Any Online applications • Applications targeting SAP Netweaver Gateway • No synchronization or MBOs • Focus on Application Management Player Native • iOS • BlackBerry • Android • Windows Mobile Online applications • Applications based ERP & CRM • Very good for metadata driven/code less solutions • Optimized workflow for various device profiles.
  • 73. © 2011 SAP AG. All rights reserved. 73 Common Deployment Questions Can you deploy SMP servers on VM infrastructure? Windows or Linux? How Many Machines? What should the Spec Be? How do we scale? How do we deal with the DMZ? What about SSL?
  • 74. © 2011 SAP AG. All rights reserved. 74 Deployment on a Developer Machine Laptop Spec: Mid to High End Recommended: Quad Core (64 bit) 8GB Ram Windows 7 Pro 64bit 40Gb Free
  • 75. © 2011 SAP AG. All rights reserved. 75 Deployment of a Single Node Development Server Server Spec: Mid to High End Recommended: Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 40Gb Free Development Server
  • 76. © 2011 SAP AG. All rights reserved. 76 Deployment of a Multi Node QA Environment Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 40Gb Free Cluster Node 1 Data Tier Cluster Node 1 Reverse Proxy Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 100 Gb Free
  • 77. © 2011 SAP AG. All rights reserved. 77 MS Cluster in Active Active Deployment of a Multi Tier Production Environment Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 40Gb FreeCluster Node 1 RP1 NON VM MS CLUSTER AA Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit Cluster Node 2 Cluster Node 3 RP2 Load Balancer
  • 78. © 2011 SAP AG. All rights reserved. 78 Sizing guidelines Best resource is our Sizing Guide on SDN http://tinyurl.com/lopygzn Covers sizing recommendations for: MBO’s OData Proxy Agentry EIS
  • 79. Thank You! Any questions drop me an email paul.todd@sap.com
  • 80. © 2011 SAP AG. All rights reserved. 80 No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. © 2011 SAP AG. All rights reserved Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.