Technology options for building apps with the SAP Mobile - Tyconz [PDF]

Elisa Nieto | Download | HTML Embed

Oct 3, 2013
Views: 19
Page(s): 79
Size: 1.68 MB
Report

Transcript

1 Technology options for building apps with the SAP Mobile Platform RIG - Paul Todd V1.3 October 2013

3 Technology options for building applications with the SAP Mobile Platform Styles of Mobile Development that are Relevant Today

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

5 Mobile Enablement Functions Understanding the total picture Represents 20% of the total cost of deploying a mobile strategy Can be accelerated with partners and off-the- shelf applications Represents 80% of the total cost of implementing your own infrastructure Costly and time consuming Requires skill sets which are not core to Mobile Enablement business Functions 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 2011 SAP AG. All rights reserved. 5

6 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 Challenges and requirements Qualities and features Skill-set diversity Enable world-class tools Services Application diversity platform Reusable platform services for mobile B2E Rapid evolution Device/platform agnostic B2B B2C Heterogeneous landscape Embrace open standards 2011 SAP AG. All rights reserved. 6

7 The platform value proposition Developer Admin User Open platform Open platform Platform approach millions of developers easily extensible consistent app experience Flexible framework Seamless integration and Self service portal native, HTML, or business centralized management user empowerment analysts optimized TCO BYOD enabled SDK and tools Industry standard security user choice fast and productive assurance and control Enterprise app store Reusable services and App platform + app mgmt discover new apps and frameworks end-to-end mobile lifecycle capabilities consistent and extensible management 2011 SAP AG. All rights reserved. 7

8 SAPs end-to-end solution strategy A comprehensive enterprise mobile portfolio Banking Retail Telco B2E apps B2C apps Industry LoB Analytic Custom Partner Partner s Travel & Media & hospitality entertainment Automotive Mobile application platform Mobile with Development Platform developmentTools tools/SDK / SDK and framework Sencha SAP Mobile Platform Appcelerator PhoneGap Mobile Enterprise Mobile Consumer Application Platform (MEAP) Application Platform (MCAP) On-premise SAP HANA Cloud SAP/Sybase build Ecosystem 2011 SAP AG. All rights reserved. 8

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

10 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 Native, Hybrid, Meta-Data Driven, SMS Apps Connect to any SAP or non-SAP data source and application iOS Android BlackBerry Windows 8 Create amazing mobile applications using native and third-party IDEs and SAP SDKs and libraries: authentication, data integration, synchronization, SAP Mobile Platform 3D visualization, and reusable components Deploy native, hybrid and metadata driven mobile applications from the device of their choice: iOS / Android / BlackBerry / Windows 8 / SAP Windows Phone 8 / Windows Mobile SAP Systems HANA 3rd Party 2011 SAP AG. All rights reserved. 10

12 Client Paradigms Why we support them all? SMP 2.3 SMP 3.0 RTC Q3 2013 Q4 2013 Player Agentry 6.x Agentry Agentry Native SMP 2.2 SUP SUP HWC SMS Mobiliser 5.x Mobiliser 5.x Mobiliser 2011 SAP AG. All rights reserved. 12

13 Architectural Break-down of a Mobile Solution Web-services Synchronization SMS W3C SOAP OData JSON Mobilink Protocol Angel Protocol SAP JCO JDBC Mobile Consumption Application Model UI Mobile Implementation Enablement Development Tools Model Functions User Onboarding Authentication & Authorization Player Hybrid Web Container Connection Management. Native Application Settings SMS Resource Bundles Encryption Services Central Monitoring, Logging, Tracing 2011 SAP AG. All rights reserved. 13

14 Player Type Applications Pros: Cons: Design Once Deploy Many On Device Complex Calculations Auto App Updates tedious Codeless UI Control Set Limited Offline Capable Device support limited Player Good Use Cases: Bad Use Cases: Field Force Automation Novel UI Requirements Sale Force Automations Consumer Oriented 2011 SAP AG. All rights reserved. 14

15 Hybrid Web Container Applications Pros: Cons: Design Once Deploy Many No implicit Sync Model for Offline Massive Development Community Apple Rules Large Device Support Resource Intensive - > User XP Hybrid Web Container Good Use Cases: Bad Use Cases: Lightweight workflow apps Heavy process driven apps with Online lookup apps offline requirements Consumer Oriented 2011 SAP AG. All rights reserved. 15

16 Native Applications Cons: Pros: Expensive Maximise Performance Specialized Skills Maximise User XP Rewrite for each Device Type Direct Access to Peripherals Updates require redeploy Native Good Use Cases: Specialized Interfaces (3D) Bad Use Cases: Process Intensive Apps Consumer oriented (cost) UX important 2011 SAP AG. All rights reserved. 16

17 SMS Applications Pros: Cons: Large Device Support User XP Limited No App Deployment Spam Simple and Intuitive Cost to user SMS Good Use Cases: mCommerce Apps Bad Use Cases: Loyalty Apps Complex process driven Utility Apps 2011 SAP AG. All rights reserved. 17

18 SMP 2.3 Architecture

21 Technology Options

23 SMP Native MBO Application Software Architecture ERP RFC SCC SOAP Player WS RESTful Hybrid Web WS MBO Container Operations Queries OData Load WS Native Sync Object API Cache DB DB SAP Mobile SDK + Native Framework 2011 SAP AG. All rights reserved. 23

24 SMP HWC MBO Application Software Architecture ERP RFC SCC SOAP Player WS RESTful Hybrid Web WS MBO Container Operations Queries JS API OData Load WS Native Cache SAP Mobile SDK + DB DB Any UI Framework 2011 SAP AG. All rights reserved. 24

27 SMP Native ODP Application Software Architecture ERP RFC SCC SOAP Player WS RESTful Hybrid Web WS Container OData Proxy OData WS ODP API Native NWGW SAP Mobile SDK + DB Native 2011 SAP AG. All rights reserved. 27

30 SMP Player Application Software Architecture Agentry Addon ERP RFC SCC SOAP Player WS JCO RESTful Agentry Hybrid Web WS Java Runtime Container Integration Code OData WS Native Meta Data JDBC Repository DB Agentry Editor Triggers, Stored Proc 2011 SAP AG. All rights reserved. 30

31 MBO Technology

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

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

34 Mobile Business Objects - MBO Architecture Admin/Config Tool Business Suite & 3rd Party SMP Device Backend Device Synchronization & Messaging optimized Distribution Rules Data Consolidation MBO Repository MBO (Native & Container/HTML5) DevTool for Content DevTool Apps 2011 SAP AG. All rights reserved. 34

35 SMP MBO-based App Development Native Object API: MBO configures server for synchronization, client DB & objects, and generates query methods in Native Object API SMP Development Task Flow 1 2 3 4 Develop 5 6 Develop Deploy Mobile Install native Install native Generate MBO Native Mobile Business application application API from MBO Application Business Objects to and test in and test on Diagram using MBO Objects Unwired Server Simulator Device Native SDK 2011 SAP AG. All rights reserved. 35

36 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 EISs 2011 SAP AG. All rights reserved. 36

38 HWC Technology

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

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

42 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 SMP Development Task Flow 1 2 3 4 5 6 Develop Deploy Mobile Generate Develop Hybrid Deploy to Deploy to Mobile Business JavaScript API Application in SCC and test SCC and Business Objects to from MBO UI5, JQM or in HWC in test in HWC Objects Unwired Server Diagram Sencha Touch Simulator on Device 2011 SAP AG. All rights reserved. 42

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

44 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 APIs such as NFC 2011 SAP AG. All rights reserved. 44

45 OData Proxy SDK

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

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

48 OData Proxy - ODP Architecture Client Specialized Native Applications OData SDK (Persistence, Caching, ODATA parsing) SMP Glue (Authentication, On-Boarding, Connectivity) Messaging (Secure Connectivity, Reliable Messaging) SMP Server Messaging (Authentication, Mobile Data Delivery(IMO), Push, Message Handlers) Push Notifications Http(s) Proxy Connector Registry (Tunneling & URL Re-write, Subscriptions) Requests & Response (App, User, Subscription, Configuration) SAP Gateway 2011 SAP AG. All rights reserved. 48

49 ODP-based Apps Development Native API: ODP API provides support operations and management functionality to ease development SMP Development Task Flow 1 2 3 4 5 Develop Create Develop Test Deploy onto backend registration in application application device OData SMP 2011 SAP AG. All rights reserved. 49

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

51 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 2011 SAP AG. All rights reserved. 51

52 REST SDK Technology

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

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

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

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

57 SMP REST-based Apps Development Ensure programming API has access to HTTP headers and cookies SMP Development Task Flow 1 2 3 4 Test SMP Register Deploy Access in Integrate into application in application to REST testing application SMP app stores tool 2011 SAP AG. All rights reserved. 57

58 Metadata Technology

59 Agentry Architecture Fundamentals Agentry Server Administration Client Agentry Agentry Server Development Server Agentry Client installed on the mobile device Connection/Steps can be: Application Java VM Definitions Server ANGEL HTTP XML Port S SQL Database T Java Logic E File System P S Publish application into the Agentry Server Eclipse ATE - Agentry Test Agentry Editor Environment 2011 SAP AG. All rights reserved. 59

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

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

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

63 Solution Architecture SAP Enterprise Meta-Data Driven Technology Eclipse Agentry Editor SAP ERP SAP CRM Bluetooth (PAN) Network (LAN) WAN Agentry Development Wireless LAN FIREWALL Server Wireless WAN Namespace Satellite Dial-Up METADATA Docking Cradle SAP Add-On (Application Definition) FIREW Standard ALL IRDA Enhanced BAPIs TCP/IP Configuration exchange Module data System Connection Agentry Client Administration Application Logic Communication Module UI Application Flow Configuration Peripheral Integration Communication Storage 2011 SAP AG. All rights reserved. 63

64 SMP Player-based Apps Development Player application Metadata driven solution means faster deployment and testing. SMP Development Task Flow 1 2 3 4 5 6 Test in dev Move Do backend Build workflow Deploy to dev environment application Roll out to customizations And screens environment with ATE and from dev to all users Devices production 2011 SAP AG. All rights reserved. 64

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

66 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 APIs outside the documented player APIs is required. Client OS is not supported by player yet. 2011 SAP AG. All rights reserved. 66

67 Review

68 Review: Evaluate the Use Case Which SMP Technology should I use? SDK Application Use Case Type Native Native Offline applications Object iOS Typically mission-critical and more complex. API 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 Native Online applications SDK iOS Applications targeting SAP Netweaver Gateway BlackBerry Very good for lightweight services-based development scenarios in Android native apps. No synchronization or MBOs Hybrid Web Online+, with Push Apps HTML5/JS/CSS Very good for lightweight HTML cross-platform development Native Container scenarios with access to native. iOS Contains features that allow server-driven push notifications. Android Allows users to act on approvals while offline, and push those BlackBerry updates to the server when the device regains connectivity. Windows Mobile In 2.1, can support Camera; in 2.1.1 can support other device APIs. 2011 SAP AG. All rights reserved. 68

69 Review: Evaluate the Use Case Which SMP Technology should I use? (Part 2) SDK Application Use Case Type REST Any Online applications API Applications targeting SAP Netweaver Gateway No synchronization or MBOs Focus on Application Management Player Native Online applications iOS Applications based ERP & CRM BlackBerry Very good for metadata driven/code less solutions Android Optimized workflow for various device profiles. Windows Mobile 2011 SAP AG. All rights reserved. 69

70 A Mobile Architecture Decision Tree playing to the strengths of each architecture type Start Pre-built SAP Disconnected Acceptable to Have available web No No No No Supporting multiple No industry app match operation / sync package as a web design / programming device platforms? your needs? required? site? talent? Yes Yes Yes Yes Yes Yes Supporting multiple Mobile Need strict Yes Native MDD Apps device platforms? vendor UI/UX Web Site conformance? great st art er Nat ive IDE + apps + o ine via Mobiliser Nat ive Object support or SAP UI5 No or ODat a No SDKs Hybrid Nat ive t ooling, wit h eit her Nat ive Object or ODat a SDK, depending on Container complexit y of o ine requirement s Kapsel - Writ e once approach 2011 SAP AG. All rights reserved. 70

71 SMP 2.3 Deployment Options

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

74 Deployment of a Single Node Development Server Development Server Server Spec: Mid to High End Recommended: Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 40Gb Free 2011 SAP AG. All rights reserved. 74

75 Deployment of a Multi Node QA Environment Reverse Proxy Quad Core (64 bit) 8GB Ram Cluster Node 1 Cluster Node 1 Windows 2008 R2 64bit 40Gb Free Quad Core (64 bit) 8GB Ram Data Tier Windows 2008 R2 64bit 100 Gb Free 2011 SAP AG. All rights reserved. 75

76 Deployment of a Multi Tier Production Environment Load Balancer Quad Core (64 bit) 8GB Ram RP1 RP2 Windows 2008 R2 64bit Cluster Cluster Cluster 40Gb Free Node 1 Node 2 Node 3 NON VM MS MS Cluster in Active Active CLUSTER AA Quad Core (64 bit) 8GB Ram Windows 2008 R2 64bit 2011 SAP AG. All rights reserved. 76

78 Thank You! Any questions drop me an email [email protected]

79 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 products and services mentioned herein as well as their respective logos are trademarks or Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft registered trademarks of Sybase, Inc. Sybase is an SAP company. Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, All other product and service names mentioned are the trademarks of their respective System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, companies. Data contained in this document serves informational purposes only. National z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, product specifications may vary. 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, written permission of SAP AG. Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered This document is a preliminary version and not subject to your license agreement or any trademarks of 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 particular course of business, product strategy, and/or development. Please note that this Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or document is subject to change and may be changed by SAP at any time without notice. registered 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 contained within this material. This document is provided without a warranty of any kind, UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. either express or implied, including but not limited to the implied warranties of Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are merchantability, fitness for a particular purpose, or non-infringement. trademarks or registered trademarks of Citrix Systems, Inc. SAP shall have no liability for damages of any kind including without limitation direct, HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World special, indirect, or consequential damages that may result from the use of these materials. Wide Web Consortium, Massachusetts Institute of Technology. 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 control over the information that you may access through the use of hot links contained in JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for these materials and does not endorse your use of third-party Web pages nor provide any technology invented and implemented by Netscape. warranty whatsoever relating to third-party Web pages. 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. 79

Share

Transcript