sap integration and certification center (sap i

8/13/2019 SAP Integration and Certification Center (SAP I..

1/10

2/18/13 SAP Integration and Certification Center (SAP I... | SCN

scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20 1

Getting Started Newsletters Store

Solutions Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Login RegisterWelcome, Guest Search the Community

Activity Communications Actions

Brow se

SAP Integration and Certification Center (SAP ICC)

4 TweetTweet 4

Disclaimer: Views expressed here are strictly personal and present only one approach for mobile app

development using Sybase Unwired Platform (SUP) and SAP NetWeaver Gateway (GW). Please consult

with the SAP Integration and Certification Center ( ICC) tolearn more about other available

integration scenarios.

This blog describes the integration scenario when developing mobile apps using GW 2.0 and SUP 2.1.

Sybase Unwired Platform is at the heart of SAPs mobile strategy. It has seen tremendous growth and just recently,

the company announced an impres sive milestone as it hit the 500M mark in mobile pipeline with more than 350

new customers and 17.5 million total seats in 2011.

With the recent release of SUP 2.1, SAP and Sybase are promoting seam less integration and closer alignment of

their technology stacks with the introduction of SAP NetWeaver Gateway integration. This new arch itecture of

combining SUP and GW promises not only to ease but accelerate the development cycle of mobile apps and facilitate

integration to the SAP back-end by exposing processes as easily consumable OData services. For mobile app

developers who have experienced first-hand the challenges of interfacing with SAP back-end processes , this comes

as a welcomed addition to an already impress ive platform.

With such promises and encouraging claims, many are eager to jump onboard and be part of the burgeoning

ecosystem which by SAPs es timate, should contribute upwards of 80% to future SAP-related mobile app

development. As often the case with anything new, theres some confusion on this new approach and many are

wondering how it works and more precisely what this architecture translates to in terms of development effort when

compared to the current main approach for integrating backend SAP processes with Mobile Busines s Objects

(MBOs). Certainly, theres a lot of information on the respective websites o f SUP and Gateway yet there is little

information generally available on the integration of these two components (at the time of writing in January 2012).

This s tate of affairs combined with the launch of the Mobile App Certificationfor partners and ISVs by ICC has

compelled me to shed som e light on this new approach and share my experience.

In this blog, I will introduce mobile app development using SUP 2.1 and Gateway 2.0* by providing an overview of this

architecture and m ore importantly, how to enable the integration between these two components.

*restricted to onl ine nati ve apps only, hybrid a pps wil l not be discussed here.

THE BASICS

First, lets s tart with the basics . Prior knowledge of mobile app development using SUP is clearly indispensable in

understanding the topics dis cussed here and how this new approach differs from current standards. Before I

proceed, I invite you to review some basic concepts of mobile app development with SUP (including MBO) and SAP

NetWeaver Gateway (including OData) if you are not familiar with them. Here are a few links to help you get started on

the right track.

If youre new to developing on SUP altogether, there is a nice starter page on SDN compiled by Stan Stadelman,

Product Manager for SUP:

Developing Mobile Apps with Sybase UnwiredPlatform 2.1 and SAP NetWeaver Gateway 2.0

Posted by David Thirakulin SAP Integration and Certification Center (SAP ICC)on Jan 16, 2012 3:08:20 PM

ShareShare 12 Like 5
http://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/people/eric.lai/blog/2011/12/13/sap-we-have-175-million-mobile-users-influencer-summit-recap-slideshttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/bloghttp://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20http://scn.sap.com/community/icchttp://scn.sap.com/docs/DOC-25303http://www.sap.com/corporate-en/press.epx?PressID=17731http://blogs.sybase.com/mobiledevelopment/?p=636http://blogs.sybase.com/mobiledevelopment/?p=629http://scn.sap.com/people/eric.lai/blog/2011/12/13/sap-we-have-175-million-mobile-users-influencer-summit-recap-slideshttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-83317/Picture1.pnghttp://scn.sap.com/community/icchttp://twitter.com/search?q=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20https://twitter.com/intent/tweet?hashtags=SCN&original_referer=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20&text=Developing%20Mobile%20Apps%20with%20Sybase%20Unwired%20Platform%202.1%20and%20SAP%20Net...&tw_p=tweetbutton&url=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20&via=SAPCommNethttp://scn.sap.com/community/icc/blog/2012/02/16/certification-webinars-sybase-unwired-platform-and-sap-netweaver-gatewayhttp://scn.sap.com/community/icc/bloghttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/contenthttp://scn.sap.com/actionshttp://scn.sap.com/communicationshttp://scn.sap.com/activityhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/login.jspahttp://scn.sap.com/community/icc/blog/2012/01/16/login.jspahttp://scn.sap.com/community/developer-centerhttp://scn.sap.com/welcomehttp://www.sapstore.com/http://scn.sap.com/community/newslettershttp://scn.sap.com/community/getting-started


2/10



New SUP Developer Resources

To that, I would add the following compilation of resources:

Sybase Unwi red Platform - An Introduction (Part 1)on SDN

SUP Product page on Sybase

SUP Installation

SUP Online Documentation on Sybase

Developing Mobile Applications with Sybase Unwired Platform MBO

MBO Best Practices

Which Mobile Architecture Should I Use?

SUP Apps on Code Exchange

Getting started with SAP NetWeaver GatewayOData.org

Introducing OData

OData SDK Developer Guide

Gateway Installation

SAP NetWeaver Gateway Architecture

Gateway How-to guides

Gateway Online Demo System

In a nutshell, SUP is an integrated platform that enables mobile devices to access back-end enterprise data. Prior to

version 2.1 of SUP, the primary development approach for creating native mobile apps with SUP to connect to SAP

systems was through MBOs. MBOs encapsulate back-end business logic which is m ade accessible on mobile

devices. When integra ting to an SAP back-end, MBOs are us ually derived from a BAPI (via WS or JCO). Consequently,

the integration scenario that I present here will be compared to what I refer to as the MBO approach since its the

mos t common one and it provides a good point of reference. As for SAP NetWeaver Gateway, it is ess entially a

component that exposes SAP Business Suite processes as OData services (OData & Generic channelswill not be

discuss ed here). This is perhaps an oversimplified summ ary so please take a look at the resources mentioned

above for more information.

UNDERSTANDING THE NEW ARCHITECTURE

Lets now discus s this new architecture in comparison to the previous model of MBOs and highlight some key

differences. First off, when developing a mobile app using SUP you have the choice to adopt (or not) SAP NetWeaver

Gateway, in case this was not clear. MBOs have always been at the core of SUP and they still have their merits. They

remain an interesting option, even a better choice for some s cenarios. With SUP 2.1, SAP is propos ing a

complementary approach to ease the development effort but furthermore, SUP and GW tackles the challenges posed

by a specific class of application defined as online apps (as opposed to offline apps). This approach is specific to

this class of application (in this release anyhow).

Online apps are defined as lightweight apps with rather simple bus iness use cases or processes that are almost

always connected and store little or no data on the device. Technically speaking, this category of applications usually

relies on synchronous messaging based on the request-response pattern. If your application fits this model than the

general consensus is to use SUP in conjunction with SAP NetWeaver Gateway as a scalable and viable mobile

strategy. If you want to know more about which mobile architecture to use, take a look at this blog from Sybase.

The SUP and Gatew ay integration is enabled by the Online Data Proxy. The prim ary focus of this blog is highlighted

in blue.

BENEFITS

Surprising claimsaside, the integration of SAP NetWeaver Gateway does provide some very interesting benefits. First

of all, it should be stated that the vast majority of mobile development projects at SAP rest on Gateway. The slew of

SAP-delivered mobile apps out there (or upcoming) is bas ed on this architecture so there is most certainly merits to

this manner. Simply, I would say that the best reason for adopting this approach is OData and how it can easily allow

information from SAP systems to be easily consumed on a variety of devices. This protocol is extremely appealing as

it is based on open standards, its eas y to consume and sim ple to use (think in terms of http). Since OData is meant

for all types of clients (not specifically mobile apps ), nothing prevents your gateway services to be reused and

consumed by a variety of other devices or applications if engineered properly.

Another good reason to favor this approach is the fact that all the data modeling is encapsu lated at one level, the

backend (contrary to the MBO approach where busines s logic also res ides on the middleware). Needless to say, if

your company is already a SAP Services Partner then you are better off investing in the in-house ABAP skill s and
http://en.sap.info/gateway-apps-mobile-rest-duet-enterprise/43463http://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76094/diag1B.jpghttp://blogs.sybase.com/enterprisemobility/2011/10/which-mobile-architecture-should-i-use-part-1/http://help.sap.com/saphelp_gateway20/helpdata/en/47/25dd9e63c54f268ec132195773326c/content.htmhttp://www.sdn.sap.com/irj/sdn/gateway?rid=/webcontent/uuid/1051f6d9-e87a-2e10-d188-e2786c7878b1http://www.sdn.sap.com/irj/sdn/gateway?rid=/webcontent/uuid/c0a638d0-8478-2e10-8eb4-f157b64fb221http://scn.sap.com/docs/DOC-8180http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b054074c-d6cf-2e10-8e96-f818697921fehttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01708.0210/doc/html/title.htmlhttp://msdn.microsoft.com/en-us/data/hh237663http://www.odata.org/http://scn.sap.com/docs/DOC-24763https://cw.sdn.sap.com/cw/groups/sup-appshttp://blogs.sybase.com/enterprisemobility/2011/10/which-mobile-architecture-should-i-use-part-1/http://blogs.sybase.com/mobiledevelopment/?p=632http://www.sdn.sap.com/irj/scn/advancedsearch?query=developing+mobile+applications+with+sybase+unwired+platform+http://infocenter.sybase.com/help/topic/com.sybase.infocenter.pubs.docset-SUP-2.1.0/doc/html/title.htmlhttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.pubs.docset-SUP-2.1.0/doc/html/PLUGINS_ROOT/com.sybase.infocenter.dc01698.0210/doc/html/title.htmlhttp://www.sybase.com/products/mobileenterprise/sybaseunwiredplatformhttp://scn.sap.com/people/alexander.ilg/blog/2010/05/23/sybase-unwired-platform--an-introduction-part-1http://scn.sap.com/people/stan.stadelman/blog/2011/06/25/new-sup-developer-resources


3/10



perform all the programming in the back-end vs. having to program custom Java code (such is the case with SUPs

result set filters).

Finally, one common issue that developers encounter most when modeling MBOs to interface with the SAP back-end

is that MBOs are generated based on existing BAPIs and this can pose quite a challenge. The inherent problem with

this method is that existing BAPIs are not necessarily best suited for the purpose at hand as they have been designed

for desktop-grade applications with different requirements in mind (think heavy and complex processes). This makes

the modeling task far more com plex than the trivial exercise it is s upposed to be. Indeed, in this particular case the

modeling task is neither straightforward nor confined to using the MBO generation tool. Linking MBOs and m apping

attributes is now a tricky exercise. And so more often than not, developers decide to implement custom ABAP code to

meet the specific needs of their mobile application. I think this is one of the most compelling reas ons for adopting

GW. If there is a clear requirement to develop your own BAPI then its easy to see why it makes a lot of sense to

implement them in the back-end within the context of Gateway services and benefit from reusability, extensibility and

scalability.Now that you understand the benefits of using SUP and GW, lets take a look at how to enable the integration between

both.

HOW TO GET SAP NETWEAVER GATEWAY

A complete pre-packaged SAP NetWeaver Gateway Trial versionis available in the Downloads section of SDN (note

that Linux or Windows Server 2008 is required). Or, you can proceed with the easy route and opt for the SAP

NetWeaver Gateway Demo system. This is more than enough if your goal is to understand the basics.

HOW TO GET SYBASE UNWIRED PLATFORM 2.1

At the time of writing, a trial version of SUP 2.1 is only offered to Sybase partners or customers. SAP partners should

consult the SAP Service Marketplaceor their partner manager.

The first thing you will notice if you are familiar with SUP 2.0 is that the software installation package for SUP 2.1 has

been split into two 2 dis tinct components: SUP Platform Runtime and Mobile SDK. This is a good thing s ince it is

purposely addressing the needs of deployment vs. development. You will need to ins tall both packages.

INSTALLING THE SOFTWARE

The focus of this blog is really about the technical aspects of the integration scenario. Personally, I did not encounterany major issues by following the installation guides and so I will not cover the installation process. Theres already

some good sources of information on this topic, check them out:

- SAP Developer Network: Installing Gateway

- Sybase Online Documentation: Installing SUP 2.1

DEVELOPMENT FLOW

A typical developm ent flow can be initiated using a top-down or bottom-up approach (in the same way as MBO

design). This is still true when developing online apps using GW and SUP. Actually, the development flow does not

differ much from the standard way but you have to keep in mind that all the modeling and adaptation tasks that were

required for SUP have now been m oved to GW. Essentially, you will develop your client code, expose Gateway

services and configure your SUP server to allow your device to consume OData services. Since, we do not have any

MBOs with this approach, theres no modeling, mapping of attributes or generation of device-specific client code to

interface with the MBOs.

EXPOSING ODATA SERVICES

SAP NetWeaver Gateway is an OData provider meaning it exposes existing SAP Business Suite processes as OData

services . Simply put, it takes RFC data from SAP back-end and adapts it into OData. For developers familiar with

MBOs, this im plies that your business logic will reside solely on the back-end and not on the SUP server. For the

purpose of this blog and to showcase an end-to-end scenario, I invite you to use the SAP NetWeaver Gateway demo

system. Most developm ent projects will probably require creating your own Gateway services and in this case, the

how-to guides on SDNcover a wide range of poss ibilities on how this can be achieved.

DEVELOPING THE CLIENT APPLICATION

On the client side, you must develop your client code using the OData SDK in order to enable your mobile device to
http://www.sdn.sap.com/irj/sdn/gateway?rid=/webcontent/uuid/c0a638d0-8478-2e10-8eb4-f157b64fb221http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/1051f6d9-e87a-2e10-d188-e2786c7878b1http://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76095/diag2B.jpghttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.pubs.docset-SUP-2.1.0/doc/html/PLUGINS_ROOT/com.sybase.infocenter.dc01698.0210/doc/html/title.htmlhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b054074c-d6cf-2e10-8e96-f818697921fehttp://service.sap.com/http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/1051f6d9-e87a-2e10-d188-e2786c7878b1http://www.sdn.sap.com/irj/scn/downloads?rid=/webcontent/uuid/90b292cc-a2d7-2e10-709d-9fba966a6937


4/10



consume OData services (OData SDK is shipped with SUP 2.1). The OData SDK currently supports iOS, Android and

Blackberry platforms. The ins tallation steps are described on the Sybase documentation

websitehttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01708.0210/doc/html/title.html (see the

OData SDK Developer Guide).

It is also worth noting that as of SUP 2.1, the OData SDK only supports native mobile application development. This is

certainly a deal breaker if you are building apps using the m obile workflow package (hybrid apps running on the

hybrid web container).

CONFIGURING SUP

Once OData services are exposed and provide access to back-end SAP processes , the remaining step is to enable

the client application to access them by configuring SUP via the Sybase Control Center (SCC). When used in

conjunction with Gateway, the SUP server is no longer a container for business logic but acts as a dispatcher of

requests from mobile devices located outside the corporate firewall to Gateway and provides more infrastructure-

centric functionalities, such as user handling, security and so forth. To give you a clear idea of how this is done, here

is a step-by-step guide:

Open SCC (https://localhost:8283/scc/)

Sybase Control Center Welcome Page:

Select Applications Select Application Connections tab Press button Register

Applications Connections:

Fill in information specific to your app to register a new application connection (*pre-requisite: your application has

already been created/defined in the Applications tab of SCC)

New Application Connection Registration:
http://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76097/sc2.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76096/sc1.pnghttps://localhost:8283/scc/http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01708.0210/doc/html/title.htmlhttp://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01708.0210/doc/html/title.html


5/10



Topics:Mobile

Select the newly created item and press button Properties Select Proxy Enter value for field Application endpoint

to direct to your OData service (for GW demo system, simply fill in the URL of the sample consumption model here).

Application Connection Properties:

Click OK and we are done configuring the connection to the Gateway OData provider in SCC.

As you can see, once the client code has been im plemented using the OData SDK and the OData service has been

made availab le from Gateway, integrating GW and SUP is simply configuration work. This is quite different from the

MBO approach as theres little development effort required on SUP. With this approach, theres ess entially no more

business logic residing on this com ponent (tasks s uch as managing devices/users and security remain).

CONCLUSION

With the release of SUP 2.1, SAP is offering a compelling integration scenario to easily access complex SAP

processes and help mobilize the workforce. Developing mobile solutions us ing SAP NetWeaver Gateway and SUP

offers many benefits such as the ability to leverage existing ABAP skills and confine the complexity of business logic

in the back-end layer. More importantly, the main advantage of this approach and key differentiator is the ability to

expose information using the OData protocol.

A few years ago, SAP establis hed a bold s trategic goal of reaching a billion people by 2015 and this release is a step

in that direction. It provides scalability in distributing critical bus iness information stored in SAP systems across

multiple devices and platforms. Furthermore, the recent launch of the SAP Store for Mobile Appsillustrates the

ambitions of the company in promoting a rich and vibrant ecosystem for enterprise m obile apps. And ICC is certainly

aligned with this effort as it rolls out the Mobile App certification for partners and ISVs.

The New Year is off to a great start and should be a thrilling one for mobile app developers as news of new developerresources have already been announced. Decidedly, its a great time to build enterprise mobile apps. Get started

now by getting in touch with ICC and learn how simple it is to get your mobile app certified and on the SAP Store!

NEXT STEPS

Allow me to reiterate that the approach discuss ed here is on ly one of many integration scenarios available to partners

and ISVs. If you are interested in learning more about the Mobile App certification, please contact SAP ICC at

[email protected] to discuss your interest more in-depth.

14674 View s Tags: mobile, sybase, sup, gatew ay, iphone, certification, unwired, platform, odata, app
mailto:[email protected]?subject=RE:%20SUP+GW%20SDN%20BLOGhttp://scn.sap.com/community/icchttp://scn.sap.com/docs/DOC-25303http://www.forbes.com/sites/sap/2011/12/19/sap-taking-action-to-ensure-no-mobile-developer-left-behind/http://scn.sap.com/docs/DOC-25303http://ecohub.sap.com/store/mobility/http://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76099/sc4.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-61253-76098/sc3.pnghttp://scn.sap.com/community/icc/blog/tags#/?tags=apphttp://scn.sap.com/community/icc/blog/tags#/?tags=odatahttp://scn.sap.com/community/icc/blog/tags#/?tags=platformhttp://scn.sap.com/community/icc/blog/tags#/?tags=unwiredhttp://scn.sap.com/community/icc/blog/tags#/?tags=certificationhttp://scn.sap.com/community/icc/blog/tags#/?tags=iphonehttp://scn.sap.com/community/icc/blog/tags#/?tags=gatewayhttp://scn.sap.com/community/icc/blog/tags#/?tags=suphttp://scn.sap.com/community/icc/blog/tags#/?tags=sybasehttp://scn.sap.com/community/icc/blog/tags#/?tags=mobile


6/10



Average User Rating

(3 ratings)

4 TweetTweet 4ShareShare 12 Like 5

27Comments

Like (1)

John MoyJan 16, 2012 4:37 PM

Thanks for a good, detailed pos t. I have a SUP 2.0 installa tion, but have yet to get my hands on a

SUP 2.1. This post will certainly be useful, especially the links.

Rgds

John

Like (0)

Community UserJan 16, 2012 11:22 PM (in response to John Moy)

What a lovely blog.Nobody has covered on an end to end scenario which you have done is

very good.Looking out for few more of the blogs or articles or whichever you want to share

knowledge.

Like (0)

David ThirakulJan 17, 2012 7:41 AM (in response to John Moy)

Thanks John! I appreciate the positive comment since it's my 1st pos t on SDN.Cheers,

David

Like (0)

John MoyJan 18, 2012 2:07 AM (in response to David Thirakul)

Hi David,

Trust me, the 1st post is the hardest one by far. Hope to see much m ore from you

in future ;-)

Rgds

John

Like (0)

Frank StdleJan 16, 2012 11:41 PM

Thanks for an honest and useful discus sion on SUP and Gateway. If I have to choose between

developing applications based on MBOs and Gateway, Gateway is now to obvious choice.

However, I wonder if there might be a third, viable option - to build a custom RESTful service using

the SAP ICF framework, bypassing MBOs and Gateway all together (some excellent blogs have

previously discuss ed how to do this http://goo.gl/9j9om). If the number of applications in the

enterprise is small and requirements are relative s traightforward, this seems and attractive option.

OData is a sophisticated protocol, but it requires s ome effort to build an OData service, and perhaps

a full fledged OData/Gateway service is overkill for a few, simple applications. What I don't know is if

SUP would be able to communicate with such a RESTful service?

Like (0)

David ThirakulJan 17, 2012 8:03 AM (in response to Frank Stdle)

Hi Frank,

Thanks for the feedback! I would also keep in mind what kind of apps I want to build when

considering m y options. Right now, SUP+GW is best s uited for online apps. As for your

third option, it's certainly interesting(thx for the link). Technically, SUP supports the creation

of a connection profile from a REST WS so it might work (using MBOs). However, I shouldpoint out that it's not supported as an integration scenario from ICC if that's a concern.

Cheers!

David

Like (0)

John MoyJan 18, 2012 2:06 AM (in response to David Thirakul)

Hi David,

Just seeking clarification here. By saying ' it's not supported as an integration

scenario' does that mean that if partners code apps with custom REST APIs from

ICF rather than using GW, they won't be certified?

Rgds

John
http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285001http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285002http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285000http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285001http://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://goo.gl/9j9omhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285000http://scn.sap.com/people/frank.stdlehttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284998http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284999http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284996http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284998http://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284996http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284997http://scn.sap.com/people/community.userhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-284996http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://twitter.com/search?q=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20https://twitter.com/intent/tweet?hashtags=SCN&original_referer=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20&text=Developing%20Mobile%20Apps%20with%20Sybase%20Unwired%20Platform%202.1%20and%20SAP%20Net...&tw_p=tweetbutton&url=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Ficc%2Fblog%2F2012%2F01%2F16%2Fdeveloping-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20&via=SAPCommNet


7/10



Like (0)

Wim SnoepJan 18, 2012 2:19 AM (in response to John Moy)

Hi John/David,

@David; Great work in this blog.

True;

Apps with a custom REST solution won 't be certified. It is however

poss ible to use custom REST as a datasource in SUP.

Certification: http://www.sdn.sap.com/irj/scn/index?

rid=/library/uuid/900a5cb7-5a09-2f10-e5bb-dd756c54fbfd

Certification is a prerequisite for adding your app to the SAP appstore.

Rgds,

Wim

Like (0)

Wim SnoepJan 18, 2012 2:22 AM (in response to John Moy)

Hi John/David,

@David; Great work in this blog.

True;

Apps with a custom REST solution won 't be certified. It is however

poss ible to use custom REST as a datasource in SUP.

Certification: http://www.sdn.sap.com/irj/scn/index?

rid=/library/uuid/900a5cb7-5a09-2f10-e5bb-dd756c54fbfd

Certification is a prerequisite for adding your app to the SAP appstore.

Rgds,

Wim

Like (0)

Ethan Jew ettJan 18, 2012 2:50 AM (in response to Wim Snoep)

Interesting. This presentation indicates that REST interfaces to

third party systems are supported. Maybe app developers will

jus t "forget" to mention to the ICC that the third-party system the

connect to is an SAP system :-) I doubt it, but amusing

nonetheless.

Cheers,

Ethan

Like (0)

Frank StdleJan 18, 2012 3:17 AM (in response to Ethan

Jewett)

Looking at the certification process in the link above, it

doesn't look like you will get so easily away with that :)

Like (0)

David ThirakulJan 18, 2012 10:51 AM (in response to Wim Snoep)

Hi everyone,

Thank you for the positive comments!

Well, regarding my "not supported" comment, I saw this com ing

and I actually wanted to edit it the moment it was added (I

should have said "might not" be s upported). In any case, I

apologize for the misunderstanding. Allow me to rectify: as a

general rule for the mobile app certification, if what you are

developing is supported by SUP (i.e. REST web services) then itshould be fine for the certification. But because every mobile

app is different, I invite you to get in touch with us so we can

discuss your needs in detail ( [email protected] ). It is never too

early to involve us if you wish to get your app certified and have it

on the SAP Store.

@Wim: thank you for pointing that out!

Cheers !

David

DJ AdamsJan 18, 2012 2:31 AM (in response to David Thirakul)

Hi David

Great first blog post.
http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285001http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285008http://scn.sap.com/people/dj.adamsmailto:[email protected]://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285004http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285007http://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285005http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285006http://scn.sap.com/people/frank.stdlehttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285004http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285005http://scn.sap.com/people/esjewetthttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/900a5cb7-5a09-2f10-e5bb-dd756c54fbfdhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285002http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285004http://scn.sap.com/people/wim.snoep2http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/900a5cb7-5a09-2f10-e5bb-dd756c54fbfdhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285002http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285003http://scn.sap.com/people/wim.snoep2http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#


8/10



Like (0)

Can you please give us the reasons why such a mechanism would not be

supported? That would help this discuss ion for sure.

Many thanks

dj

Like (0)

Frank StdleJan 18, 2012 3:01 AM (in response to David Thirakul)

David, thanks for taking the time to elaborate! You say REST WS requires using

MBOs -- what would the role of the MBO be in this scenario? I got the impression

from your blog that MBOs were best avoided for "online" apps. I have in mind a

setup where SUP only takes care of security, authorization etc, and simply

dispatches reques t from the client to an ICF node which takes care of all the

busines s logic and data handling.

Like (0)


Hi Frank,

the role of an MBO will remain one of a DTO (data transfer obj) between

frontend and backend. I associated REST WS with MBOs because your

MBO can be created/binded us ing the MBO generation tool with this type

of data source... In any case, it's an interesting setup!

Like (1)


BTW, I should a lso point out that I never stated "MBOs are best avoided

for "online" apps". SUP2.1 and GW 2.0 is best suited for online apps .

Just want to be clear:)

Like (0)

Steve CherestalJun 13, 2012 12:29 AM

Great post Dave, I was looking for some info on SUP and GW and how they work together... this gave

me a pretty good idea. I'll come see you if I have more questions!

Like (0)

Clemens Suter-CrazzolaraJun 25, 2012 1:46 PM

Two additional resources:

The Sybase Unwired Platform developer center in the SAP Developer Center

For partners, SAP has created a great external site with a lot of addition content

http://www.sapmobileappspartnercenter.com/get-started

Like (0)

Mark GearhartAug 1, 2012 2:07 PM

Holy cow David, that is one great article. I can visualize a big decision matrix in my brain. Online-only

versus Offline-enabled, MBO versus Gateway, native versus HWC.

Like (0)

Malik NaeemDec 29, 2012 8:40 AM

Thanks a lot David. It's very helpfull info for me as a bignner.

and its help me alot to understand path of mobile Development using SUP and SAP gateway.

Like (1)

Rammutla Ishmael NdlovuJan 7, 2013 12:08 PM

Thanks a lot for a great article David. Dear colleauges , kindly clarify the need for Sybase Unwired

Platform. If we have selected a non-SAP Mobile product as our Enterprise Mobility Managem ent

suite (for example, Zenprise), why would we need Sybase Unwired Platform to access our SAP

Business Suite? Thank you all in advance.

John MoyJan 7, 2013 12:27 PM (in response to Rammutla Ishmael Ndlovu)

Hi Rammutla,

That is entirely your choice. However, from my experience the m ajority of 3rd party platforms

will serve you only as mobile development platforms. That means, you are developing your

apps from scratch, with som e ass istance (code generation or other) from the particular

platform you choose. Only the SAP Mobile Platform additional ly provides you with a suite of

apps that you can purchase from SAP to run with end-to-end integration working out of the

box with SAP Business Suite. So when comparing SUP with other platforms, this is one

factor to take into consideration ... http://store.sap.com/mobile
http://store.sap.com/mobilehttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335713http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335714http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335713http://scn.sap.com/people/rammutlandlovuhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-334736http://scn.sap.com/people/malik.naeemhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-314771http://scn.sap.com/people/mark.gearharthttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://www.sapmobileappspartnercenter.com/get-startedhttp://scn.sap.com/community/developer-center/mobility-platformhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-309874http://scn.sap.com/people/clemens.suter-crazzolarahttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-309176http://scn.sap.com/people/steve.cherestalhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285009http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285011http://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285009http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285010http://scn.sap.com/people/david.thirakulhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285001http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-285009http://scn.sap.com/people/frank.stdlehttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#


9/10



Like (0)

You might be able to custom code a couple of apps using your 3rd party platform, but can

you code the 100+ apps provided by SAP and supported ongoing by SAP? Don't

underestimate the cost to support your own custom apps. With every new mobile operating

system release (eg. iOS6.1) you might need to revisit your apps - and at the moment the

these are being released at a rapid pace.

I'm not saying you shouldn't use another platform, just go in with eyes wide open about

what that might mean from a pros and cons perspective.

Regards

John

Like (1)

John MoyJan 7, 2013 12:32 PM (in response to John Moy)

Hi Rammutla,

I just looked up Zenprise and that appears to be a mobile device management

solution.

That is very different to a mobile application development platform like SUP. I'm

afraid you're comparing apples and oranges.

Regards

John

Like (0)

Rammutla Ishmael NdlovuJan 7, 2013 12:34 PM (in response to John Moy)

Good day John, Thanks for the feedback. I do unders tand. However, most of the

articles seem to indicate that there should be SUP between the mobile devices

and the NetWeaver Gateway. A decis ion on the Enterprise Mobility Management

su ite. It might end up being SAP Afaria or other competing products . However,

our architecture has to indicate what is necessary and what is optional. Do you

imply that for us to use the apps available on http://store.sap.com/mobile we must

definitely use Sybase Unwired Platfrom 2.x? Kind regards, Ramm utla

Like (1)

John MoyJan 7, 2013 1:20 PM (in response to Rammutla Ishmael Ndlovu)

Hi Rammutla,

As at today, yes the majority of those apps requi re SUP in order to be

supported by SAP. You will need to look at the pre-requisites for each

app. For most of the productivity on-line apps, SUP acts moreso as a

secure authentication provider and as a reverse proxy, whereby the

OData communications is from NW Gateway to the app, via SUP.

I have recently noticed a few apps that can be supported for use directly

with NW Gateway within the intranet. Look at the ins tallation guides for

apps like SAP Performance Monitor, or SAP End User Experience

Monitoring. Although these particular apps s eem to be ones which

connect with NW Gateway in Solution Manager, so they are only useful for

your technical support people, not your real end us ers.

The other consideration you might need to be aware of is the newAgentry platform (from Syclo) which SAP acquired las t year. This is

planned to be merged with SUP. I have heard through the grapevine

(and confirmed with an SAP contact) that SAP have moved the CRM

Sales app to Agentry. This is an app that has offline syc capabil ity. You

should be aware of this because that means also that not all apps are

on SUP. Also with the acquis ition Syclo had pre-existing apps that

integrated with SAP running on Agentry. This included some apps for

field services and works m anagement, among others.

Regards

John

Like (0)

Rammutla Ishmael NdlovuJan 7, 2013 1:35 PM (in response to John

Moy)

Thanks a lot John. Much appreaciated.

Kind regards,Rammutla

Like (1)

Clemens Suter-CrazzolaraJan 7, 2013 1:42 PM (in response to John

Moy)

For SAP partners, the guidelines outlined in the SAP MobileApps Partner Programhttps://www.sapmobileappspartnercenter.com/ may be useful:

"The SAP mob ile platform to build m obile apps consists of: (1)

Sybase Unwired Platform, (2) SAP Afaria, and (3) SAP

NetWeaver Gateway."

As a result we have partner apps live on the SAP Storethat use

Sybase Unwired Platform or SAP NetWeaver Gateway.
https://store.sap.com/sap/cp/ui/resources/store/html/Solutions.html?pcntry=DE&sap-language=EN&catID=MOB&_cp_id=id-1357562192827-0#Allhttps://www.sapmobileappspartnercenter.com/http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335718http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335583http://scn.sap.com/people/clemens.suter-crazzolarahttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335718http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335720http://scn.sap.com/people/rammutlandlovuhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335716http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335718http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://store.sap.com/mobilehttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335714http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335716http://scn.sap.com/people/rammutlandlovuhttp://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335714http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#comment-335715http://scn.sap.com/people/john.moy3http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#http://scn.sap.com/community/icc/blog/2012/01/16/developing-mobile-apps-with-sybase-unwired-platform-21-and-sap-netweaver-gateway-20#


10/10


/ it /i /bl /2012/01/16/d l i bil ith b i d l tf 21 d t t 20 10

Follow SCNSite Index Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright
http://www.sap.com/corporate-en/our-company/legal/copyright/index.epxhttp://www.sap.com/corporate-en/our-company/legal/impressum.epxhttp://www.sdn.sap.com/irj/scn/policyhttp://www.sdn.sap.com/irj/scn/policy?view=PPhttp://help.sap.com/http://scn.sap.com/docs/DOC-18476http://scn.sap.com/docs/DOC-19361http://bit.ly/SCNLnIhttp://bit.ly/SCNyouThttp://bit.ly/SCNFBhttp://bit.ly/SCNTwR

sap integration and certification center (sap i

Documents