Sap for Mobile, Netweaver Gwy or SUP

[roberto_pezzano2]

Dear SAP friends,

my boss asked to me to study about SAP for Mobile to evaluate what we need to have it in our enterprise.

I'm a bit confused about the differences among:

1) SAP for Mobile

2) SAP Netweaver Gateway

3) Sybase Unwired Platform

4) SAP Mobile Infrstructure

I think I understood that the last one is obsolete and not to be used anymore (am I wrong?)

SUP can be connected via SAP Netweaver Gateway to backend using Odata protocol.

But it can be connected to SAP Backend or other backend using other way of communicating (again am I wrong?)

SAP Netweaver Gateway can communicate to mobile device directly or via Duet Enterprise too.

What is it SAP for Mobile? Just a commercial name to collect all the possible solutions? Or what?

And my final question is (if what written above is correct): how can I choose the best solution?

Thanks for any answer

Roberto

[midhun_vp]

1) SAP for Mobile- It is group in the SCN. it is not a product.

2) SAP Netweaver Gateway- It is a product use that can be used with or without SUP in between SAP and Mobile devices.

3) Sybase Unwired Platform- It is a middle ware (Product) used to connect Mobile devices and SAP server

4) SAP Mobile Infrstructure - As the name says it meant for the infrastructure for SAP Mobility.

Different infrastructures  for Enterprise mobility are. Based on the requirement infrastructure can be selected. The development strategy will be different for each.

• SUP+SAP
• SUP+NW gateway+SAP
• NW gateway +SAP

-Midhun VP

[Former Member]

Hi,

could you please answer the same question for SAP BusinessObjects Mobile?

What are the possibilities to use SAP BO Mobile in a secure way for Enterprise?

I read a lot and found that it can be configured to work through SAP Mobile Platform,

but it is the only and the simplest way?

Of course maximal security is required (https, two way authentication, win ad login, XML gateway,..)

AFAIK with SMP no inbound connection (port opening) is needed. Are there any other possibility?

Thanks

Csaba

[_IvanFemia_]

Hi,

Basically you have 2 approaches: synchronized and not synchronized apps.

• Synchronized mobile app are based on SUP (now SMP - SAP Mobile Platform) MBO
• Not synchronized app are using SUP as a "proxy" for a Gateway OData service.

I suggest to watch my recorded TechEd session

Slides are also available on SlideShare http://www.slideshare.net/ivanfemia/from-abaper-to-mobiler-evolution-of-developer

Best

Ivan

[Former Member]

Hi SAP Users,

I am also Looking for the same information. please provide more information on this.

Thanks

Brijesh

[Dan_vL]

3) Sybase Unwired Platform

The Sybase Unwired Platform enables the creation of either native mobile applications or HTML 5 aka Hybrid Apps that access data exposed via Mobile Business Objects.  Mobile Business Objects are an abstraction layer from back end data sources.  For example an MBO can connect to SAP using JCo,  various databases, or via webserivces/rest services.  The SUP platform can also cache the data (reducing the load on the back end) and provides security.

When accessing the MBO's using a native client, a local copy of the data exposed by the MBO can be stored locally on the device enabling offline usage.

Hybrid Apps are geared more towards online usage (although they do support some offline use cases) and less complicated workflows.  In a matter of minutes a hybrid app can be created and deployed to multiple devices (iOS, Android, BlackBerry 6.x and 7.x) using the Hybrid App designer.  A few other benefits include the ability to call native device functions using the built in PhoneGap libraries (access to device contacts, camera etc from JavaScript), easy deployment and redeployment of apps once the Hybrid Web Container is connected to the SUP server, and app security.

The following is a sample that may be useful if you wish to get started using the Hybrid App Designer and Hybrid Apps.

Expense Tracking Sample https://cw.sdn.sap.com/cw/docs/DOC-148193

I believe the SAP Netweaver Gateway can provide OData access to your SAP system.  It is easy to access the data from within a web page when the data is exposed via OData. 

Here is a really simple example using the open source datajs library.

<html>

<head>

<script src="js/datajs-1.0.3.js"></script>

<script>

function successCallback(data, response) {

    document.writeln("<table><tr><th>Name</th><th>Description</th></tr>");

    for (var i = 0; i < data.results.length; i++) {

        document.writeln("<tr><td>" + data.results[i].Name + "</td><td>" + data.results[i].Description + "</td></tr>");

    }

    document.writeln("</table>");

}

function errorCallback(e) {

    alert("An error occurred");

    alert(e);

}

</script>

</head>

<body>

<script>

    OData.read("http://services.odata.org/OData/OData.svc/Products", successCallback, errorCallback);

</script>

</body>

</html>