SAP Mobile Application Scope Overview

SAP Mobile Application Scope Overview Certification program for packaged Mobile Apps

SAP ICC

August 2012

© 2012 SAP AG. All rights reserved. 2

Agenda

1. SAP Mobile Platform Components for Partner

2. Guidelines for Partner Mobile Apps certification

a) Mobile App Scenario for Sybase Unwired Platform (SUP)

b) Mobile App Scenarios for Gateway

c) Mobile Apps using Afaria

3. Documentation

4. Appendix


SAP Mobile Platform Components for Partner

Components

■ Sybase Unwired Platform (SUP)

– Include Mobile SDK to develop mobile apps.

– SUP 2.1 and 2.0 can be used for certification.

■ SAP NetWeaver Gateway

– Gateway 2.0 SP3 can be used for certification.

■ Afaria

– Mobile Device Management (MDM).

– *Only included in full SAP Mobile Platform bundle.

■ Mobiliser

– Certification planned for Q4/2012.

SAP Mobile Platform

Productivity Business Consumer

Ap

ps

Apps

Ap

ps

SUP

…

Gateway Afaria* Mobiliser


Mobile Apps using SAP Mobile Platform

SAP Back-end e.g. ERP, CRM et al

Third-party backend & services

Mobile Device

OData

Jco/Enterprise

Services/

DOE Connector*

Web service/

JDBC/

REST

MBO

Apps (native, container, Mobile SDK or third party certified

SDKs)

SAP Mobile Platform

Sybase Unwired

Platform

SAP Gateway

Sybase Mobiliser

Afaria (Onboarding,

monitoring

lifecycle, and

administration)

OData


Agenda


2. Guidelines for Partner Mobile Apps certification




3. Documentation

4. Appendix


Guidelines for Partner Mobile Apps certification – 1/2

Requirements To be eligible for this certification, the mobile application must be implemented using

SAP Mobile Platform (SUP, Gateway or both).

Scope of the certification Certification covers end-to-end functionality of mobile solution.

Certification is valid for a single version of mobile apps on multiple mobile device platforms.

Certification is valid for one year.

Packaging Mobile applications developed using Sybase Unwired Platform, plus Gateway if applicable.

o Depending on mobile OS, mobile apps must be packaged natively for native apps.

o SUP server objects or MBOs must be packaged as mobile application package.

o ABAP Add-on delivery package or Gateway content delivery package using Add-on Assembly Kit (AAK), if applicable.

o Packaging of NetWeaver Mobile (aka DOE) objects using AAK, if applicable.

Mobile applications developed using SAP Gateway.

o Depending on mobile OS, mobile apps must be packaged natively for native apps.

o Gateway content delivery package using Add-on Assembly Kit (AAK).


Guidelines for Partner Mobile Apps certification – 2/2

Deploying

Deploying mobile app on mobile device using native tools. Alternatively using Afaria is recommended.

Deploying MBOs using either Sybase Control Center (SCC) on SUP server or command line utilities (or CLU)

shall be used for deploying while using DOE.

Deploying Add-on package or Gateway content package on SAP sandbox.

Deploying DOE objects on NetWeaver Mobile sandbox.

Onboarding of mobile device

Registering mobile device on SUP server.

Functional testing

End to end functionality test of mobile apps.

Out of Scope

Mobile apps developed using third party or non-SAP mobile platforms but using SAP backend.

Using only Afaria for deploying mobile apps.

Please refer to the Appendix for more details on ABAP certification.


Agenda


2. Guidelines for SAP Mobile Apps certification




3. Documentation

4. Appendix


Mobile App Scenario for Sybase Unwired Platform (SUP)

Lightweight Apps Heavyweight Apps

Third-party services

Mobile Device

SDK* on MBO**

OData

Jco/Enterprise Services

/DOE Connector

Web service/

JDBC/

REST

MBO

SDK on OData+

Apps (native, container, Mobile SDK or third party certified

SDKs)

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

Sybase Unwired Platform

OData

SAP Gateway

SAP application


Mobile Apps using Sybase Unwired Platform (SUP) – 1/3

Requirements

Mobile application must be implemented using Sybase Unwired Platform (SUP).

SAP Gateway may be used in addition with SUP.

Scope

Two SUP scenarios are possible for developing mobile apps.

a) Heavyweight mobile apps using SUP only.

b) Lightweight mobile apps using SUP and Gateway together.

Out of Scope

Using custom connector.



a) Heavyweight Mobile apps

Using Sybase Unwired Platform only.

For complex mobile apps with

o Offline capabilities – can use them without network connection.

o Focus on data synchronization when mobile apps comes online – storing data locally during network outage or no network connection.

o Heavy in terms of functionality e.g. CRM Sales scenario or Asset Management scenarios etc.

Possible to use SAP and non-SAP backend.

Only standard connectors must be used

o Java Connector (JCo) or Enterprise Service or DOE Connector shall be used for SAP backend.

o Web Service or JDBC or RESTful services shall be used for non-SAP backend.

o Using custom connectors is not allowed and is out of scope for certification.

Developed using Mobile Business Objects (MBOs).

Using SAP backend

o Possible to consume standard BAPIs and release APIs.

o Possible to consume standard SAP delivered Enterprise Services.

o Possible to develop DOE (SAP NetWeaver Mobile) data objects, distribution rules etc., in this case NetWeaver Mobile certification guidelines must be followed as well.

o Possible to develop BAPI wrappers and custom ABAP Add-on, in this case ABAP Add-on certification guidelines must be followed as well.



b) Lightweight Mobile apps

Using Sybase Unwired Platform and Gateway together.

For simple mobile apps with

o Mobile apps have online capabilities only.

o No data synchronization.

o Light and simple functionality e.g. timesheet entry, leave request etc.

OData protocol must be used.

SUP

o No MBO development is required, SUP acts as pass through.

Gateway

o If SAP Delivered Gateway Content is consumed then GW Content Consumption Certification criteria must be followed (refer Mobile Apps using Gateway for details).

o If Custom Gateway Content has been implemented then GW Content Certification criteria must be followed (refer Mobile Apps using Gateway for details).


Agenda


2. Guidelines SAP Mobile Apps certification




3. Documentation

4. Appendix


Mobile App Scenarios for Gateway

Online Apps

Mobile Device

OData

Apps (native, third party certified SDKs or HTML5)

Gateway

OData

SAP application


Mobile Apps using SAP Gateway – 1/2

Requirements

Mobile application must be implemented using SAP Gateway

OData protocol must be used.

Can use certified third party SDKs for developing mobile apps

Scope

Certification covers mobile app and

Gateway scenarios.

Two Gateway scenarios are possible for

developing mobile apps

a) Gateway Consumption scenario.

b) Gateway Content scenario.

Refer to Appendix for using OData

Channel).


Mobile Apps using SAP Gateway – 2/2

a) Gateway Consumption scenario

Verifies the functionality offered in partners’ consumption application.

Installation and configuration the consumption application i.e. mobile apps.

Functionality test of mobile apps

o User experience.

o Security (HTTPS support).

b) Gateway Content scenario

Verifies the correctness of custom Gateway content delivered by Partners.

Using Partner development namespace for content development.

Verify packaging of Gateway content using AAK.

Verify the deployment of custom Gateway content delivery package.

Verify custom Gateway content configuration.

Verify the correctness of custom Gateway content

o Data Model

o Data Source

o Consumption Model

o Workflow process using Business Workflow (optional).

o Notification using Business Event Publisher (optional).


Agenda






3. Documentation

4. Appendix


Mobile Apps using Afaria

SAP will certify Mobile Apps deployed via Afaria based on the following

Guidelines:

Requirements

Mobile solutions must be implemented using

Sybase Unwired Platform.

SAP Gateway.

Can use certified third party SDKs for developing mobile apps.

Out of scope

Mobile solutions developed using third party mobile platforms.

Only using Afaria without SUP or SAP Gateway isn’t valid for the certification.


Agenda






3. Documentation

4. Appendix


Documentation Requirements – 1/2

Questionnaire

Common for SUP and Gateway based mobile solutions.

Available on the Partner Center portal.

Partners will have to provide details like:

a) Mobile devices supported.

b) SAP Mobile Platform used.

c) Functional details of the mobile solution.

Technical Product Profile (TPP) document

Relevant for both SUP and Gateway.

Technical details of the mobile app, MBOs and backend system.

a) Details of APIs called, custom ABAP Add-on etc.

b) List test cases that will be performed during certification test

c) Additional details.

Solution Manager and PPMS Data Collection

SLD registration is required for non-SAP backend integration.

PPMS stands for Product and Production Management System.

a) (Core-)PPMS: Central knowledge repository for (technical) information on SAP products and software components.

b) Central knowledge repository is extended for (technical) information on Third Party Vendor products and software

components too.

c) PPMS Data collection is required for all mobile applications.


Documentation Requirements – 2/2

Installation and configuration documents

No specific template provided, Partners are free to choose their own format.

Required for

a) Mobile apps.

b) SUP mobile application package, if applicable.

c) ABAP Add-on package, if applicable.

d) Gateway content package, if application.

Documentation language

The Templates for the Questionnaire, TPP and PPMS Data collection will be provided by ICC.

Irrespective of the mobile app language, the templates mentioned above as well as the test case description must be documented in English.

If the mobile App will be sold outside the local market, the App UI as well as the complete documentation has to be provided in English language.

If the mobile App will be sold for the local market:

a) It is not required to translate the mobile app screens to English

b) It is not required to translate the installation and configuration documents to English.

c) Several European language versions as well as some double-bite languages could be certified. For further information please get in touch with your Partner Manager.


Agenda






3. Documentation

4. Appendix

APPENDIX


ABAP Add-on development guidelines

Registration of development namespace.

Develop ABAP objects (e.g. transactions, function modules, classes etc.) using development

namespace.

Delivery objects in customer namespace (i.e. starting with X, Y or Z) is not allowed.

Add-on Assembly Kit (AAK)

AAK will be delivered by SAP ICC after signing up for the program.

AAK must be installed on delivery system using transaction SAINT.

Custom Add-on must be delivered as Add-on delivery package using AAK.

o Delivering transport request is not permitted.

Even Gateway Content must be packaged using AAK.


Gateway – OData Channel and Content Generator

Generic Channel

As of SAP NetWeaver Gateway 2.0 SP3, provisioning OData services via the Generic Channel has been

deprecated. Similarly partner solutions built by leveraging the Generic Channel cannot be certified by SAP.

SAP recommends the use of OData Channel for creating new OData services.

OData Channel

The OData Channel (ODC) for SAP NetWeaver Gateway allows you to develop content by defining object

models and registering a corresponding runtime data provider class.

This is an optimized channel for OData that supports the OData protocol with minimal development and

runtime overhead.

Content Generator

Content generators refer to the SAP NetWeaver Gateway design-time tools that enable you to create

content (i.e. expose OData Services) quickly without having to write source code. At runtime, such

generated content executes original program (BAPI, RFC, Screen, etc.).

Generated services are an ideal approach for small and medium volume use cases and for prototyping.

Furthermore, in a certified Partner solution, updating SAP data is only allowed through released SAP APIs

(i.e. BAPIs, RFCs, etc.). Hence, Partners who need to update SAP data might also need to use the

generators to provision OData services based on such released RFCs or BAPIs.


Information

SAP Integration and Certification Center

http://www.sdn.sap.com/irj/sdn/icc

SAP Mobile Application Certification website

http://scn.sap.com/docs/DOC-25303

SAP Gateway Certification website


SAP ABAP Add-on Certification website


SAP Mobile Apps Partner Center

http://www.sapmobileappspartnercenter.com













http://www.sapmobileappspartnercenter.com/

http://www.sapmobileappspartnercenter.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 and Java are registered trademarks of Oracle.

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.

© 2012 SAP AG. All rights reserved.

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 trademarks or registered

trademarks of SAP AG in Germany and other countries.

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.

SAP Mobile Application Scope Overview

Technology

Transcript of SAP Mobile Application Scope Overview