Contenu connexe
Similaire à Sybase Unwired Platform- Introduction to Mobility
Similaire à Sybase Unwired Platform- Introduction to Mobility (20)
Plus de SAP PartnerEdge program for Application Development
Plus de SAP PartnerEdge program for Application Development (20)
Sybase Unwired Platform- Introduction to Mobility
- 2. SAP mobile platform
SAP, Partner, and Custom Apps
Native Apps Hybrid HTML5 Apps SMS Apps
Container Apps
SAP App Dev Tools Third Party App Dev Tools
SAP Mobile Platform SAP Afaria
App Catalog
Presentation Frameworks
Application
Application Services Management
Foundation Services Device
Data Sync &
Caching Authentication
App Lifecycle
Managment oData Proxy Notification … Management
SAP NetWeaver
Gateway
SAP Business Suite Sybase 365 Databases Third Party Apps
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
© 2012 SAP AG. All rights reserved. kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement 2
- 3. Agenda
1. Introduction
2. Options for Mobile App Development
3. Development Approaches
4. Client Side Differences / Approaches
5. Deciding Between the Options Available
© 2012 SAP AG. All rights reserved. 3
- 5. Complexity grows fast
Development
tools and TCD Mobile App
Device Lifecycle
and back-
end
Management
diversity Development Device
choice
Databases
Ease of
Software use
Applications
Web Apps and
Services more apps
IT Device
Management
Security TCO and
Configuration
© 2012 SAP AG. All rights reserved. 5
- 6. Enterprise Grade Mobile Platform
Create
Connect Eclipse
Heterogeneous
data sources
Consume
Heterogeneous
mobile devices Android
Databases BlackBerry
Sybase iPhone
Web Unwired iPad
Services Platform Windows
Windows Mobile
Software
Applications
Management Console
Control
Device and server management and security
© 2012 SAP AG. All rights reserved. 6
- 7. Managing andand
Securing
Managing
Securing
The Mobile DeviceLife
Cycle
the
Device
Lifecycle
Process Automation
Asset Tracking
End-to-End
Self Service Security Application
Portal Management
Telecom
Mobile
Expense
Applications
Management
B.Y.O.D.
Governance
iOS 4
iOS 5
Data Loss Prevention Fragmentation
Device Employee IT
© 2012 SAP AG. All rights reserved. 7
- 8. SAP Mobility Platform future direction
Solution today Planned innovation Future direction
Mobility Platform Platform Evolution SAP Mobile Platform
MEAP MCAP
Cloud Cloud deployed
Native SDKs B2E/B2B/B2C mobility platform
Developer Productivity for all apps
Online/Offline on any device
Open Standards
HTML5
Container Closer SAP Integration
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
© 2012 SAP AG. All rights reserved. 8
- 10. Hybrid Web Container-based
Mobile Workflow
Fast and simple application development
Fully generated web application package
Customizable output
Platform independent
Runs in a native application (container) on the device
User initiated or server initiated
Support limited offline capabilities
© 2012 SAP AG. All rights reserved. 10
- 11. Native Application
Synchronization-based applications
Support full offline capabilities
One or more MBO packages assigned
Based on compiled code specific to the target
device OS
Provides the most flexibility in leveraging on
device services
Requires separate application provisioning
© 2012 SAP AG. All rights reserved. 11
- 12. OData SDK Applications
Connect mobile devices more directly to SAP business systems
Data is not persisted, but can be cached
Leverage subscription and push notification features
Implement SAP single sign-on (SSO)
Ensure secure and reliable transport of data
Do not support offline capabilities
© 2012 SAP AG. All rights reserved. 12
- 13. Mobilizing Simple Business Processes - HWC
Enable developers to create mobile workflows without writing any device code.
CONNECT Sybase Unwired
Platform Server
SUP Tooling Mobile Device Application
Deploy Deploy
MBO Lightweight
Application
with Hybrid
Web Container
• Speeds decision-making and responsiveness on alerts, notifications and approvals
• Maximize user and manager productivity
• Improves daily operational activities and accuracy
• Increases ROI on wireless email and SAP Business Suite solutions
© 2012 SAP AG. All rights reserved. 13
- 14. Native Application Development
Object API (MBO)
Data Source Integration Device-Specific Development
CONNECT Sybase Unwired MBO API
Platform Server
SUP Tooling
Generate
Deploy code
MBO
Create
UI
Device GUI SDK
Sybase Unwired Platform enables developers to create mobile applications with device-
specific user experiences using the native device SDK, while leveraging the business logic
already defined.
© 2012 SAP AG. All rights reserved. 14
- 15. Native Application Development
OData SDK (Gateway)
CONNECT
Sybase Unwired
Platform Server
OData SDK Native
Generate
code SDK
OData
Create
Connector
UI
Device GUI
Sybase Unwired Platform enables developers to quickly create online-only mobile
applications connecting to SAP NetWeaver Gateway
© 2012 SAP AG. All rights reserved. 15
- 18. SAP OData Approach
Industry based standards (OData) Tailored for EVERYBODY
Business Suite
Internet style scalability Partners
Customers
ABAP-centric content development
Online / Offline clients Admin/Config Tool Admin/Config Tool
Business Suite Gateway Sybase Unwired Device
Device
(SAP DATA channel) Platform (Lite)
Pull & Push scenarios
Messaging
Connector
Application
SAP Data
SAP Data
SAP Data
RFC OData OData
Library
Proxy
Adaptor
specific
Stub
SDK
(Native)
DevTool (ABAP Code) DevTool Apps
© 2012 SAP AG. All rights reserved. 18
- 19. Runtime Interactions – Request / Response
Native
Device (Native) ResponseCustomer Query
Request Customer Query
Mobile SDKs and libraries per device
Cache
Local Storage
<atom:feed base namespaces>
<atom:id>http://<base_url>/SalesOrderLookUp/
http://<base_url>/SalesOrderLookUp/CustomerCollection?
CustomerCollection</atom:id>
search=Becker
<atom:title>Customers</atom:title>
SAP Data
<atom:updated>2011-02-25T17:55:54Z</atom:updated>
Sybase Unwired Platform <atom:entry>
Cross Firewall and Carrier
…
Device Onboarding
<atom:content type="application/xml">
Application Distribution
<m:properties>
Device Management
<d:value>T-CO05A00</d:value>
<d:customer_id>T-CO05A00</d:customer_id>
SSO, Authentication
<d:customer_name>Becker</d:customer_name>
SAP Data <d:city>Berlin</d:city>
...
</m:properties>
Provisioning of data based on SAP Data as the
Gateway (SAP Data Channel) </atom:content>
common standard
<atom:link href="CustomerCollection(value='T-CO05A00‘)
/SalesorderheaderCollection"
RFC rel="http://schemas.microsoft.com/ado/2007/08/dataservices
Persistence Legend
/related/SalesorderheaderCollection"
type="application/atom+xml;type=feed" title="Recent Sales Real State
Business Suite Orders“ />
</atom:entry> Cache
Business Data
<atom:entry> Consumption Model
…
</atom:entry>
© 2012 SAP AG. All rights reserved. 19
- 20. Runtime Interactions – Subscription / Notifications
Device (Native) PostPusha Notification to a Device
Post notifications to deviceSales Order
a Subscription to a
Vendor specific infrastructure
Cache
Client driven subscriptions to data
<atom:entry base namespaces>
<atom:id/>
<atom:title>Sales Order 4003 has order 4003</atom:title>
<atom:title>Subscription for saleschanged</atom:title>
SAP Data Native Device Push <atom:updated>2011-01-17T11:55:21Z</atom:updated>
<atom:author/>
<atom:updated/>
Map events to device
<atom:link href="SalesorderheaderCollection(value='0000004003’)"
Sybase Unwired Platform Delivery of notifications
rel="via" type="application/atom+xml;type=entry" />
<atom:content type="application/xml">
Enable Pub/Sub
<m:properties>
Notifications <atom:content type="application/xml">
<d:deliveryAddress>
<m:properties>
urn:sap-com:channel:sup:/user(777)/
<d:value>005056B40E791ED088C61515E3FFE043</d:value>
ERP-SEARCH/notifications
<d:collection>SalesorderheaderCollection</d:collection>
</d:deliveryAddress>
SAP Data SAP Data </m:properties>
<d:collection>SalesorderheaderCollection</d:collection>
</atom:content> eq '0000004003‘</d:filter>
<d:filter>value
Gateway (SAP Data Channel) Provisioning of Events based on a common
</m:properties>
</atom:entry> standard
</atom:content>
Subscriptions
</atom:entry>
RFC Business Event
Persistence Legend
Real State
Business Suite
Cache
Business Data
Consumption Model
© 2012 SAP AG. All rights reserved. 20
- 21. Mobile Business Object (MBO) Approach
Optimized Data Messaging Tailored for EXPERTS
Mobile Business Unit
Backend Offloading Custom Development
Selected Partners
Middleware-centric content development
Customers
Full Offline clients
Admin/Config Tool
Synchronization scenarios Business Suite & Sybase Unwired Platform Device
Device
3rd Party Backend
Consolidation
Synchronizat
Distribution
Messaging
Repository
optimized
Rules
MBO
ion &
Data
MBO
(Native & Container/HTML5)
DevTool for Content DevTool Apps
© 2012 SAP AG. All rights reserved. 21
- 22. Mobile Business Objects (MBO)
MBO properties include
Attributes
Data source, type, connection settings
Operations
Bind to existing operations, or Add New
Relationships
Mappings, complex types
Object queries
Query methods generated in object class
Synchronization settings
Rules and partitions
© 2012 SAP AG. All rights reserved. 22
- 23. Runtime Interactions – Synchronization
Local storage optimized for data
Device (Native)
synchronization
Local Storage SDKs for read and write on MBO
Asynchronous notification support
Applications run fully offline
Native Device Push
MBO
MBO
Sybase Unwired Platform
Optimizes synchronization of data
Delta syncs triggered by push notifications
Notification queues for reliable delivery
Notifications Staging and distribution of data per device
Conflict resolution for updates
Data Consolidation Distribution Rules
RFC DCN Persistence Legend
Real State
Business Suite
Cache
Business Data
Consumption Model
© 2012 SAP AG. All rights reserved. 23
- 24. Native Object API MBO
The synchronization architecture is based on a Cache DB that resides on the SUP
Server, and replicates and/or messages updates to the Client DB
Client
SUP DB
Server
Synchronization
Data
Source
Cache
DB Client
DB
Cache Refresh
Client
DB
© 2012 SAP AG. All rights reserved. 24
- 25. Native Object API MBO: Operations
Operations are staged from EIS to Cache, Cache to Client, and vice versa
Enterprise
Operation Replay: operations
Invoke the corresponding executed in Client DB are replayed
System mapped EIS Operations SUP
on Cache DB
Server
Operations Fill Filter Client
DB
Load Operations (with Cache à Device Operations are
Data parameters) to retrieve data filtered by Synchronization
Repository from EIS Cache Parameters
DB
© 2012 SAP AG. All rights reserved. 25
- 26. Example: Synchronization Parameter
Definition: SELECT * FROM Customer
Data Source Type: SampleDB (SQL Anywhere) database
Fill: Data is retrieved by executing the Load Operation (SELECT …)
Customer ID
Name
Address
City
State
1
Intel
1 Intel Drive
Santa Clara
CA
Cache DB
2
Cisco
1 Cisco Way
San Jose
CA
3
Ultra
1 Ultra Lane
Santa Clara
CA
4
AMD
1 AMD Ave
Santa Clara
CA
5
Oracle
1 Oracle Lane
Redwood Shores
CA
6
Qualcomm
1 Qualcomm Way
San Diego
CA
7
JPMorgan 270 Park Ave
New York
NY
Chase
Filter: This MBO has one synchronization parameter [city]
Mobile application sets the synchronization parameter prior to performing synchronization to
‘Santa Clara’
Client DB
Customer ID
Name
Address
City
State
1
Intel
1 Intel Drive
Santa Clara
CA
3 Ultra 1 Ultra Lane Santa Clara CA
4
AMD
1 AMD Ave
Santa Clara
CA
© 2012 SAP AG. All rights reserved. 26
- 27. Load Arguments
Control the amount of data refreshed between the EIS and CDB
Creates its own partition in the CDB based on load argument value (partition key)
Can be paired with synchronization parameters
User will supply values for the argument(s)
© 2012 SAP AG. All rights reserved. 27
- 29. Example: Load and Synchronization Parameters
Definition: SELECT * FROM Customer WHERE State = ?
Data Source Type: SampleDB database
Fill: Data is retrieved by executing the Load Operation with the load parameter set to ‘CA’
Customer ID
Name
Address
City
State
1
Intel
1 Intel Drive
Santa Clara
CA
Cache DB
2
Cisco
1 Cisco Way
San Jose
CA
3
Ultra
1 Ultra Lane
Santa Clara
CA
4
AMD
1 AMD Ave
Santa Clara
CA
5
Oracle
1 Oracle Lane
Redwood Shores
CA
6
Qualcomm
1 Qualcomm Way
San Diego
CA
Filter: This MBO has one synchronization parameter [city]
Mobile application sets the synchronization parameter prior to performing synchronization to
‘Santa Clara’
Client DB
Customer ID
Name
Address
City
State
1
Intel
1 Intel Drive
Santa Clara
CA
3 Ultra 1 Ultra Lane Santa Clara CA
4
AMD
1 AMD Ave
Santa Clara
CA
© 2012 SAP AG. All rights reserved. 29
- 30. Development Approaches by Examples
SAP OData Mobile Business Objects
Expense Capture Mobile Sales for CRM
Employee Lookup Mobile Service for CRM
Ramp Reservation System (Yard Management) Asset Management
Loyalty Management (CRM) Direct Store Delivery
Dialog Reception (Vehicle Dealer Business Meter Reading
Management)
© 2012 SAP AG. All rights reserved. 30
- 32. Choice in Mobile Application Development
Ÿ Leverage web development resources
Ÿ Leverage industry standard development tools & tool-chains
HTML5
Ÿ Easily build, support, and deploy cross platform
Ÿ Great for rapid development of simple apps accessing web services
Ÿ Access to native device capabilities
Hybrid Ÿ Encrypted/secure data store
with SAP Ÿ Robust data messaging layer w/guaranteed push notification
Mobile Ÿ Application Lifecycle Management
Ÿ Data Integration with complex SAP & non-SAP data sources
Ÿ Reuse investments/assets from HTML5/Hybrid development
Ÿ Access to robust device and middleware services such as database/data object store
Native & replication services
Ÿ App lifecycle, deployment, and management provided by Afaria
Ÿ Great for apps requiring robust graphics, complex offline transactions
© 2012 SAP AG. All rights reserved. 32
- 33. Choice in Mobile Application Development
How does SUP support these approaches?
Native
Ÿ SDKs
Ÿ Code generation
HWC
Ÿ IDE for UI
Ÿ How-to Guide for alternative 3rd Party approach
© 2012 SAP AG. All rights reserved. 33
- 35. Questions frequently asked by customers/partners
What mobile
application architecture
should I choose?
© 2012 SAP AG. All rights reserved. 35
- 36. Evaluate the Use Case
“Which Sybase Unwired Platform SDK should I use?”
SDK Application Type Use Case
Native Native Offline applications
Object API • iOS • Typically mission-critical and more complex.
• BlackBerry • Users can work on data while fully-offline
• Windows/WM • Server and client updates are synchronized
• Android • Very good for large data volumes and disconnected environments
OData SDK Native Online applications
• iOS • Applications targeting SAP Netweaver Gateway
• BlackBerry • Very good for ‘lightweight’ services-based development scenarios in native apps.
• Android • No synchronization or MBOs
• Request-Response type of protocol
Hybrid Apps Web Online+, with Push
• HTML5/JS/CSS • Very good for lightweight HTML cross-platform development scenarios with access to
Native Container native.
• iOS • Contains features that allow server-driven push notifications.
• Android • Allows users to act on approvals while offline, and push those updates to the server when
• BlackBerry the device regains connectivity.
• Windows Mobile
© 2012 SAP AG. All rights reserved. 36
- 37. SAP Mobility and various application models
Applications Data Light Moderate Heavy
models
Use Case Consumer B2C Productivity B2E, B2B Process B2E
Important Application • Multi-platform device Support • Multi-platform device support • Large data volume
characteristics • Very high scalability • Large scalability • Synch/Offline data
• Online/ Minimal local storage • Online/Offline persistency
• Application on-boarding • Enterprise Security integration • Backend Data caching
• Backend Application • Transactional integrity
Integration
Important Architecture • Web/HWC/Native • HWC/Native • Native
Elements • Direct backend access-ODP • ODATA/MBO • MBO/ESDMA
• Online/Message-based • Messaging/Sync • Messaging/Sync
• Auto provisioning • Self-registration • Device Data security
© 2012 SAP AG. All rights reserved. 37
- 38. Mobility Decision Matrix (Customer Specific)
Capability Needed Native Hybrid Web Web Content
Use Cases Most Robust Apps – DSD, EAM Medium / Lightweight - Lightweight / Content-based or
Employee Productivity, etc. Server-centric Uses – Portal, etc.
Development Effort More Complexity Light to Moderate Complexity Basic Content
Development Framework Native Tools and SDK for UI SUP Forms Designer + Web 2.0 SDK Web Technologies
Cost of Development Higher due to resources and Much less due to web development Varies depending on how much
complexity resources and UI Generation mobile-optimization is required
Cross Platform Support None – device and OS Specific Yes – based on the supported Yes – assuming correct browser
containers versions
Robust Offline Yes – full capabilities to store data in Moderate- there are practical Very limited – need to code with
Capabilities customized way limitations to discuss HTML5 APIs for offline support
Robust Device Capabilities Yes – full capabilities of the device Some – dependent on the container Minimal – some techniques to control
and OS and the limitation of HTML5 device
Usability / User Experience Optimal – can take advantage of full Significant – leverages web Variable – dependent on connection,
capabilities of OS technologies for look and feel network speed, web optimization
© 2012 SAP AG. All rights reserved. 38
- 39. Web apps versus hybrid web container apps
Web
Applica5on
Hybrid
Web
Container
Usability
Always Available
• Push Enabled
• Native Services
• Ease provisioning
Performance
Security
© 2012 SAP AG. All rights reserved. 39
- 40. Web apps versus hybrid web container apps
Web
Applica5on
Hybrid
Web
Container
Usability
Performance
Reliable Communication
• Guaranteed Delivery
• Data stored natively
• Transactional integrity
Security
© 2012 SAP AG. All rights reserved. 40
- 41. Web apps versus hybrid web container apps
Web
Applica5on
Hybrid
Web
Container
Usability
Performance
Security
Secure Sandbox
• Personal & Company use device
• Authentication
• Application password
© 2012 SAP AG. All rights reserved. 41
- 42. How to choose the application model?
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
No Yes
Yes
No
No
Yes Yes
No
No
Yes
Yes
No
Yes
No
No Yes
Yes
No
Yes
No
No
Yes
No
© 2012 SAP AG. All rights reserved. 42
- 43. SUP Client stack comparison
Features Native Hybrid Web Container 2.1.3
Communication
Guaranteed delivery ✔ ✔
Messaging paradigm ✔ ✔
Synchronization paradigm ✔ ✖ (Roadmap)
Push ✔ ✔
Data Persistency
Data Storage ✔ ✔
MBO Object Generation ✔ ✔
MBO Object Query ✔ ✔
MBO Object API ✔ ✖ (Roadmap)
Security
On-Device encryption ✔ ✔
Authentication ✔ ✔
Application Password ✖ ✔
User interface
Generate UI ✖ ✔
Common Business Logic ✖ ✔
Customization ✔ ✔
© 2012 SAP AG. All rights reserved. 43
- 44. Mobile SDK
Accelerate development of mobile apps.
Device integration
Reusable UI Components
GPS, address book, email, tasks, phone
UI controls, widgets, forms, and views
Calendar, camera, barcode scanner, printer, RFID
Cache management
Runtime data management, Persistence Data parser
synchronization, metadata, Metadata, app data, and encryption Data protocol parsers
and app data
Connectivity Configuration and
Security
Authentication (basic and Supportability
SSO), asynch and
On-boarding support, RSA
Error-handling, logging,
packaging
key generation, and Preferences, defaults, and
synchronous requests, tracing, versioning
certificate-handling app constants
notifications, push
© 2012 SAP AG. All rights reserved. 44
- 45. Mobile requirements and application patterns
UI Native HTML5/JS Container Native
Ÿ Native coded apps Ÿ Rapid development on Ÿ Native coded apps
Ÿ Phone, PIM integration multiple device types Ÿ User can access and modify all the critical information even when disconnected
without client coding
Ÿ Example — Employee Ÿ User gets relevant business data calculated and pushed to the device directly
productivity apps, etc Ÿ Example — Leave
approvals, etc.
Communication
Pattern Request-response & Notifications Synchronization & Seamless offline - online
Ÿ SAP OData extensions for Ÿ Connectivity to any backend Ÿ Backend application logic calculates Ÿ Rules based data distribution —
people centric exposure system through various data set that goes to the device outside the context of the
models. protocols Ÿ Optimized for scenarios with daily application; offloading of distribution
device data refreshes calculations to mobile middleware
Ÿ SAP Backend publishes
service descriptions which Ÿ Example: Direct Store Delivery Ÿ High flexibility reg. change of data
can be subscribed by users. distribution rules; Example: Mobile
Data and changes are Sales & Service
delivered via Gateway and
Solution proxied by SUP
Components
SUP
Gateway / SUP Consolidation /
Mobi Extension Backend Distribution Extension (DOE)
Backend Backend
Afaria (Mobile Device Management)
© 2012 SAP AG. All rights reserved. 45
- 46. SUP 2.1.3
Back End Model/Conn Mobile Middleware Device
iOS
Gateway OData BB
SAP (Native SDK) Android
Business
Suite
RFC/BAPI
Proxy MBO
(Hybrid Web iOS
Container) BB
Android
3rd Party
WS WM
Non SAP
System REST MBO
iOS
JDBC BB
MBO Android
(Native SDK + WM
Gen Code)
SUP Server Win32
© 2012 SAP AG. All rights reserved. 46
- 48. © 2012 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,
permission of SAP AG. The information contained herein may be changed without prior notice. Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,
Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.
Some software products marketed by SAP AG and its distributors contain proprietary software components of
other software vendors. INTERMEC is a registered trademark of Intermec Technologies Corporation.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Wi-Fi is a registered trademark of Wi-Fi Alliance.
Microsoft Corporation.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,
POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are
Linux is the registered trademark of Linus Torvalds in the United States and other countries. trademarks or registered trademarks of SAP AG in Germany and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Systems Incorporated in the United States and other countries. 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
Oracle and Java are registered trademarks of Oracle and its affiliates.
is an SAP company.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.
registered trademarks of Citrix Systems Inc. Sybase is an SAP company.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG
Consortium, Massachusetts Institute of Technology. in Germany and other countries. Crossgate is an SAP company.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, All other product and service names mentioned are the trademarks of their respective companies. Data
and Xcode are trademarks or registered trademarks of Apple Inc. contained in this document serves informational purposes only. National product specifications may vary.
IOS is a registered trademark of Cisco Systems Inc. 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.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry
Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered
trademarks of Research in Motion Limited.
© 2012 SAP AG. All rights reserved. 48
- 49. © 2012 SAP AG. Alle Rechte vorbehalten.
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,
welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,
In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Google Mail, Gmail, YouTube, Dalvik und Android sind Marken oder eingetragene Marken von Google Inc.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten INTERMEC ist eine eingetragene Marke der Intermec Technologies Corporation.
auch anderer Softwarehersteller enthalten.
Wi-Fi ist eine eingetragene Marke der Wi-Fi Alliance.
Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation.
Bluetooth ist eine eingetragene Marke von Bluetooth SIG Inc.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System
Motorola ist eine eingetragene Marke von Motorola Trademark Holdings, LLC.
z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,
POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, Computop ist eine eingetragene Marke der Computop Wirtschaftsinformatik GmbH.
XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix und Smarter Planet sind Marken oder eingetragene Marken der IBM Corporation. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden
Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Ländern. Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern.
Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Adobe Systems Incorporated in den USA und/oder anderen Ländern. Web Intelligence, Xcelsius und andere im Text erwähnte Business-Objects-Produkte und -Dienstleistungen
sowie die entsprechenden Logos sind Marken oder eingetragene Marken der Business Objects Software Ltd.
Oracle und Java sind eingetragene Marken von Oracle und/oder ihrer Tochtergesellschaften.
Business Objects ist ein Unternehmen der SAP AG.
UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.
Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und weitere im Text erwähnte Sybase-
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin sind Marken oder Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der
eingetragene Marken von Citrix Systems, Inc. Sybase Inc. Sybase ist ein Unternehmen der SAP AG.
HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Crossgate, m@gic EDDY, B2B 360°, B2B 360° Services sind eingetragene Marken der Crossgate AG in
Consortium, Massachusetts Institute of Technology. Deutschland und anderen Ländern. Crossgate ist ein Unternehmen der SAP AG.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im
und Xcode sind Marken oder eingetragene Marken der Apple Inc. Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische
Unterschiede aufweisen.
IOS ist eine eingetragene Marke von Cisco Systems Inc.
Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry
Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit
Storm, BlackBerry Storm2, BlackBerry PlayBook und BlackBerry App World sind Marken oder eingetragene ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet.
Marken von Research in Motion Limited.
© 2012 SAP AG. All rights reserved. 49
- 50. The Grid Headline area
White space
Drawing area
© 2012 SAP AG. All rights reserved. 50