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

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

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 ?

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

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

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

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

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

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

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

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

SMP 2.3 Software Architecture

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

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

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

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

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

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 High Level Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
SMS
SMP Platform Components

SMP SDKs and Development Tools
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native
Platform Services Mobile SDK’s

SMP Player Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native

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

SMP HWC Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native

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

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

SMP Native Application Software Architecture
DB
ERP
RFC
SOAP
WS
RESTful
WS
OData
WS
Player
Hybrid Web
Container
Native

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

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

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

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.

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.

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

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

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

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

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

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.

Architecture

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
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

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

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 - 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

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.

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

ODP-based Apps Development
Native API:
ODP API provides support operations and management functionality to ease
development
Develop
backend
OData
1
Create
registration in
SMP
2
Develop
application
3
Test
application
4
Deploy onto
device
5

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

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

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

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

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)

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.

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

SMP Player-based Apps Development
Player application
Metadata driven solution means faster deployment and testing.
Do backend
customizations
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

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

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
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

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.

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

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.

SMP REST-based Apps Development
Ensure programming API has access to HTTP headers and cookies
Register
application in
SMP
1
Test SMP
Access in
REST testing
tool
2
Integrate into
application
3
Deploy
application to
app stores
4

“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.

“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.

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?

Deployment on a Developer Machine
Laptop Spec:
Mid to High End
Recommended:
Quad Core (64 bit)
8GB Ram
Windows 7 Pro 64bit
40Gb Free

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

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

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

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

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.

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

More Related Content

What's hot (20)

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

More from SAP PartnerEdge program for Application Development (20)

Recently uploaded (20)

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