SAP Mobile Platform Architecture and Strategy

A Look at SAP's Mobile Platform
Components
A Branded Service Delivered by Customer Solution Adoption
June, 2012

Disclaimer

This presentation outlines our general product direction and should not be relied on in
making a purchase decision. This presentation is not subject to your license
agreement or any other agreement with SAP. SAP has no obligation to pursue any
course of business outlined in this presentation or to develop or release any
functionality mentioned in this presentation. This presentation and SAP's strategy and
possible future developments are subject to change and may be changed by SAP at
any time for any reason without notice. 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 assumes no responsibility for errors or omissions in this document, except if
such damages were caused by SAP intentionally or grossly negligent.

©  2011 SAP AG. All rights reserved. 2

Agenda

u  SAP’s Mobility Strategy

u  Afaria Platform and Architecture

u  Sybase Unwired Platform Architecture

u  NetWeaver Gateway Architecture

u  Summary


Objectives

At the end of this Session, you will be able to understand:
Ÿ  SAP’s mobile platform strategy
Ÿ  The architecture and uses of Afaria
Ÿ  The architecture and uses of Sybase Unwired Platform
Ÿ  The architecture and uses of SAP NetWeaver Gateway


Agenda





u  Summary


Planned SAP Mobility Platform

Apps (native, container)

Reusable libraries

Sybase development
tools and lifecycle
SDK* on SUP online-offline / OData**
Afaria

SUP protocols

Sybase Unwired Platform 2.x
Onboarding,
Data
Other connector Notifications and OData monitoring
consolidation and
technologies subscriptions connector lifecycle, and
distribution
administration

Web service Web service BAPI
Web service OData
JDBC Rest Wrapper
Rest (Suite)
SAP NetWeaver SAP NetWeaver
Mobile Gateway
Third-party services
Back ends running SAP software

SAP Business Suite SAP Business ByDesign SAP BusinessObjects solutions

*Software development kit ** Mobile business object +Open Data Protocol

This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. 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


Agenda





u  Summary


Afaria – Mobile Device Management

Afaria enables IT to centrally manage mobile
devices and security of enterprise mobile
environment throughout the device lifecycle.

With Integrated device and security management
from single point of view and web browser based
console, Afaria becomes single stop for IT to keep
mobile devices running, deploy applications, check
inventory, and provide automated updates.

Afaria:
u  Award winning MDM
u  Transforming the category
u  Legacy, heritage of leadership


Our Simplified Solution to Mobility Management


New Features in Afaria 7.0

Simplified Administration App Management Personal to Enterprise Ready

New Interface and Analytics App portal and config User configured

Workflows for policy creation User controlled App Minutes to enterprise ready:
(Simple, Quick) EUSSP
Browser Independent Distribution Security by default: certificates,
power-on-password, VPN
Simplified installation: Software “No Touch” App Configuration App portal for simplified app
appliance and enterprise grade deployment
installation
New Reporting and analytics App deployment statistics Excessive device cost prevention
Webservice API layer for App integration with SUP
automation of common tasks
Build to handle various Certificate delivery for App SSO
administrative roles
Administrate on-the-go App logging


Afaria 7.0
Main Page


Afaria 7.0
Device View


Afaria Physical Architecture
Example of System Landscape – Single Server Solution

Afaria Server

Mobile Afaria
Device Administrator
Management 2.5G Networks
Sybase Relay GSM/GPRS
Server
Afaria
Database
iPhone/iPad,
3G/4G
Blackberry or
Networks
Android device

Wi-Fi

Internal External
Firewall Firewall

Administra*ve

DMZ
Console
Browser


Afaria Physical Architecture
Example of System Landscape

Afaria Certificate
Database Authority

2.5G Networks
Sybase Relay GSM/GPRS
Server

iPhone/iPad,
3G/4G
Blackberry or
Networks
Android device

IIS
Server Wi-Fi

Internal External
Firewall Firewall

Afaria
Server
Administra*ve

Console
Browser

Domain DMZ
Controller

A - Certificate Request and Delivery C - User Authentication
B - Certificate Authentication D - Configurations Delivered


Agenda





u  Summary


What is Sybase Unwired Platform (SUP)?

u  Integrated platform solution to get enterprise apps to mobile workers in the field
u  Connects the back-end enterprise systems and data sources to mobile devices

u  Provides a complete end-
to-end solution:
u  Mobile application
development
u  Deployment
u  Security
u  Ongoing device and
application
management
u  Made up of:
u  Sybase Mobile SDK
u  SUP Runtime


What the Sybase Unwired Platform is not?

Ÿ  Mobile application UI and Business logic development tool/platform
–  For native application development, developers still need to use native tools such as
XCode, Visual Studio or other Eclipse plugins.

–  For HTML/JS/CSS, developers may still need to use tools such as Dreamweaver etc.

–  Doesn’t support development of mobile web applications (or portal content)

Ÿ  Data Integration Middleware
–  SUP is not designed to integrate/federate data. This needs to be done outside of SUP

–  SUP needs data from EIS that is pretty close to what the use-cases requires. Not good for
slicing/filtering/subsetting data

Ÿ  Not an identity/security management infrastructure
–  You still need LDAP’s/Active Directories


Sybase Unwired Platform Features

u  Connectivity to multiple client device types and mobile operating systems
u  Support for native client object-based APIs based on the device platform
language
u  Support for mobile Web-based clients within a secure enterprise sandbox
u  Eclipse-based visual development tooling for building mobile data services and
generating device-side data persistence APIs
u  Enterprise mobilization architecture that uses standard and proprietary
interfaces to support a variety of enterprise data resources
u  End-to-end pluggable security that extends from the enterprise to devices
u  Support for mobile users who are either occasionally connected or those that
work entirely online
u  Push notifications that alert clients to refresh their mobile view of data
u  Unified platform administration and monitoring


What can be done with SUP?

Create
Connect Mobile Consume
Eclipse
SDK
Applications

Partner & Custom Applications
Databases
SAP & Sybase Applications

Web
Services Unwired Mobile
Platform Services
Software
Applications

Files

Management Console Afaria

Control

Runtime Landscape

u  Includes multiple components that are part of or interact with Unwired Platform
components to provide the platform mobility solution:

u  Unwired Server — handles enterprise data source and application access,
communication between the EIS data source and the mobile device, security, transaction
processing, and scheduling.

u  Data Tier — comprises multiple databases installed for and used by Unwired Server and
the management console within the runtime landscape.

u  Relay Server — enables secure, load-balanced communication between mobile devices
and Unwired Server. Across-the-firewall deployment occurs without opening any internal
firewall ports for enterprise mobilization and ensures that data is secure while in transit.


Deployment Option 1 – All Components on Single Host

Host 1

Unwired
WorkSpace

Relay
Data Tier Unwired
Server
Server


Deployment Option 2 – Development Tools Only

Host 1

Unwired
WorkSpace


Deployment Option 3 – All Servers on a Single Host

Host 1

*

Relay
Data Tier
Unwired Server
Server


Deployment Option 4 – Data Tier and Unwired Server on
Separate Hosts

Host 1 Host 3

Unwired
Data Tier
Server

Host 2 Host 4
LB

Unwired
Data Tier
Server


Deployment Option 5 – Shared Hosts in Failover Cluster

Data Cluster*
Host 3
Host 1

Unwired
Server
Data Tier

Host 4
Host 2
LB

Unwired
Data Tier Server


Data Orchestration Engine Overview

The DOE is the core of NetWeaver Mobile

ABAP-based mobile middleware

Many concepts similar to SUP, some functional overlap

DOE provides
Data consolidation: load data from backend into staging area. Load rules
separate from distribution rules.
Data Distribution: Large, staged roll-out, complex distribution rules
Pushes data to device


Components: SAP Mobile Gateway

Add-on to DOE

Provides a design-time environment to build applications with re-usability of
data models
− Generates WSDLs per data object with services for CRUD operations.
These can be downloaded as a ESDMA bundle for developing mobile
applications using Web Services

Run-time features include: mobile friendly search, read and write web service-
compliant interfaces and data push web service event interfaces

Not related to NetWeaver Gateway!


Components: Sybase DOE Connector

Provides abstraction and optimization layer between SAP DOE and Sybase
Unwired Server

Provides ESDMA import capabilities to generate necessary inbound and
outbound interfaces

Provides data transformation for DOE interaction


Logical Architecture of DOE Scenario

SAP NetWeaver Sybase Mobile
Backend Mobile w/ Unwired Devices
DOE Platform

NW DOE
Mobile Connecto
AS ABAP Gateway r


Administration and Monitoring


Administration and Monitoring – Sybase Control Center

u  Web-based administration console that allows administrators to centrally manage,
secure, and deploy servers, data applications and devices.
u  Core management activities:
u  Server configuration
u  Cluster management
u  Device registration and security
u  Security configuration, administration and application
u  Monitoring
u  Multitenancy management
u  Log viewing
u  Troubleshooting

u  Application management activities
u  Device application deployment
u  Package management activities
u  Subscription management

Relay Server

u  Enables secure, load-balanced communication between mobile devices and
Unwired Server
u  Ensures that data is secure while in transit
u  Is used in the runtime architecture as a component of the enterprise demilitarized
zone (DMZ)
u  Securely integrates mobile devices into system landscape
u  Provides a single point of contact for devices
u  Is a specialized reverse proxy that avoids opening inbound ports in the firewall to
Unwired Server
u  Accepts and forwards requests from remote clients to Unwired Platform
components
u  Is implemented as a pair of Web extensions that run in a Web server
u  Integrates with existing security for Web and enterprise infrastructure
u  Used to Unwired Platform synchronization (end-to-end encryption)

RSOE – Relay Server Outbound Enabler

u  Runs as an Unwired Server process
u  Manages communication between the Unwired Server and a Relay Server
u  Each RSOE maintains connections to each Relay Server in a Relay Server farm
u  Passes client requests to the Unwired Server on its Replication or Messaging
port
u  Receives response from Unwired Server
u  Forwards it to the Relay Server, to be passed to the client
u  Always starts when Unwired Server starts
u  Monitored by Unwired Server to ensure it is available
u  In case of fail, Unwired Server restarts it automatically


Agenda





u  Summary


What is SAP NetWeaver Gateway?

Open
Any Device, Any Experience, Any
Experiences

Platform

People
Sybase Optimized for user interaction scenarios
Enterprise
Web Unwired Social
Software
Platform
Timeless
Non-disruptive, any SAP Business
Suite version
SAP NetWeaver Gateway

Developers
Simple APIs, no SAP knowledge
required
SAP Business Suite
Standards
Based on REST and OData/ATOM

CRM SRM SCM PLM ERP


What SAP NetWeaver Gateway is and is not!

SAP NetWeaver Gateway is not…
u  The SAP Gateway process in the NetWeaver Application Server ABAP that
enables external communication (E.G. RFC)
u  A mobile infrastructure. (For this we have SUP)
u  A replacement for SAP NetWeaver PI and eSOA Services

SAP NetWeaver Gateway…
u  Is the point of access into SAP Business Suite data and functionality
u  Uses a non-proprietary interface based on the Open Data Protocol (OData)
u  Services can be consumed by any channel that can process XML received
over an HTTP(S) connection


What is the Open Data Protocol (OData)?

OData is a Microsoft developed extension to the Atom
Publishing and Atom Syndication standards, which in
turn, are based on XML and HTTP(S). OData for SAP

It was designed to provide a standardised OData
implementation of a RESTful API. In doing so, it offers
database-like access to server-side resources. Hence, Atom Publishing
OData has been described as:

“ODBC for the Web” Atom Syndication

It can be used freely without the need for a license or
XML
contract.

OData is also extensible. This allows SAP to HTTP(S)
supplement the data types used by OData with extra
information from the ABAP Data Dictionary.


System Landscape Overview
An overview of the server components required

Gateway
Design-time
SAP Backend SAP NetWeaver Plug-in
Gateway

Client
Runtime

SAP NetWeaver 7.02
SP07 or later


SAP NetWeaver Gateway Architecture

IDEs Network
Consumer Consumer Consumer Standards
Plug-ins

Tools Gateway Core OData with SAP Annotations
Technology
Supportability
Metadata
Generators Custom Dev REST Repository Monitoring
SAP NetWeaver

BOR/SCR/ OData
RFC Channel API Service Events /
Adaptation Worflow Security

Data Source Data Conn.
SAP NetWeaver Providers
Gateway BAPI / RFC Dynpro

SAP Business Suite [ERP,CRM,SRM…]


Deployment Option 1
Central Hub

Gateway Server
Consumers
Components deployed on a
central Server

Gateway Backend(s) Gateway Hub

GW Server Add Ons
Components are deployed on
backend systems

Requirement SAP ERP SAP CRM SAP BI
SAP ERP SAP CRM
Backend must be based on Content Content
SAP BI Content

NW 7.00 SP18 Backend
Enablement
Backend
Enablement
Backend
Enablement

ECC Server CRM Server BI Server


Deployment Options 2
Embedded Deployment

Gateway Server
Consumers

Components deployed on
backend systems
SAP ERP SAP CRM SAP BI
Gateway Backend(s)
GW Server GW Server GW Server
Components are deployed on AddOns AddOns AddOns
backend systems SAP ERP SAP CRM
SAP BI Content
Content Content

Requirement Backend Backend Backend
Enablement Enablement Enablement

Backend must be based on ECC Server CRM Server BI Server
NW 7.02 SP7 (e.g. CRM 7 or
ECC 6.05)


Agenda





u  Summary


Summary Landscape

Internet DMZ Intranet Backend
Systems

SUP HA Data Tier HA NW Gateway Hub

ERP

Relay Server Farm
or SUP Server Cluster
Load Balancer Reverse Proxy Device

HA NW Mobile DOE

CRM

SUP & Afaria
Admin Server
Afaria Slaves

Analytics

OTA Deploy Server
Provisioning
& Portal
Afaria DB
Afaria Master Package Server

Legacy


Summary

You should now understand:
Ÿ  SAP’s mobile platform strategy
Ÿ  The architecture and uses of Afaria
Ÿ  The architecture and uses of Sybase Unwired Platform
Ÿ  The architecture and uses of SAP NetWeaver Gateway


© 2011 SAP AG. All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
without the express permission of SAP AG. The information contained herein may be Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
changed without prior notice. mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
Corporation.
All other product and service names mentioned are the trademarks of their respective
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
companies. Data contained in this document serves informational purposes only. National
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/
product specifications may vary.
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, The information in this document is proprietary to SAP. No part of this document may be
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, reproduced, copied, or transmitted in any form or for any purpose without the express prior
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent written permission of SAP AG.
Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of This document is a preliminary version and not subject to your license agreement or any
IBM Corporation. other agreement with SAP. This document contains only intended strategies, developments,
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. and functionalities of the SAP® product and is not intended to be binding upon SAP to any
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered 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.
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
Oracle is a registered trademark of Oracle Corporation.
warrant the accuracy or completeness of the information, text, graphics, links, or other items
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. contained within this material. This document is provided without a warranty of any kind,
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are either express or implied, including but not limited to the implied warranties of
trademarks or registered trademarks of Citrix Systems, Inc. merchantability, fitness for a particular purpose, or non-infringement.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World SAP shall have no liability for damages of any kind including without limitation direct, special,
Wide Web Consortium, Massachusetts Institute of Technology. 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.
Java is a registered trademark of Sun Microsystems, Inc.
The statutory liability for personal injury and defective products is not affected. SAP has no
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for control over the information that you may access through the use of hot links contained in
technology invented and implemented by Netscape. these materials and does not endorse your use of third-party Web pages nor provide any
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, warranty whatsoever relating to third-party Web pages.
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.


SAP Mobile Platform Architecture and Strategy

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to SAP Mobile Platform Architecture and Strategy (20)

More from SAP PartnerEdge program for Application Development (20)

SAP Mobile Platform Architecture and Strategy