SUP/SMP REST API application connection benefits

[Former Member]

We have created couple of REST API applications to run through SUP 2.2 and netweaver gateway.

At first we just used SUP proxy directly without using connection creation. Later on we added also application connection.

We are still wondering what are the actual benefits for using application connection creation? Is it only that you can get push notifications and see some client related logs, browse user lists in SUP SCC? After creating a connection, you still need to pass username/password in headers in order to get data from the backend (netweaver) so there seems to be no real benefits in client development perspective.

Is there something what we are missing here?

[midhun_vp]

In short the REST APIs allows you to develop apps for any platform and provides security, push notifications, management and monitoring of apps. You are free to choose third party developer tools for development (javascript libraries, Cordova, sencha, Appcelerator etc).

Midhun VP

[Former Member]

Hi Midhum VP,

It seems that we have not missed anything then. Most of the benefits seems to be in SCC admin side. Unlike the MBO client development, after creating connection, it is still needed to pass the username and password (header field) in order to get the data from the backend.

[midhun_vp]

The benefit of REST API is the support to different mobile OS. Ex. Windows 8 and BB are supported by SMP through REST API approach. The Odata SDK supports only Android and Ios for now, that can give many enterprise level features to the app out of the box (ex. offline, encryption) those are not available with REST API approach.

Midhun VP

[Former Member]

My original question was about creating a application connection with REST API approach and examining its actual benefits.
We can still get the data from backend without creating the connection if SUP is configured correctly.

[midhun_vp]

We can still get the data from backend without creating the connection if SUP is configured correctly.

I don't understand this point.

Midhun VP

[Former Member]

Well the original question was that is there specific benefits for client side developing if application connection is created before using the HTTP GET requests?

We know that the APPCID is the thing which we can play with, but we can also get it generated without creating the app connection.

[Virinchy]

We can still get the data from backend without creating the connection if SUP is configured correctly.

Are you referring to consume the data from SAP via BAPI and develop MBO's from it ?

also are you trying to compare the importance of using Odata in application development ?

[Former Member]

I thought you needed an application connection in order to retrieve an endpoint? Sounds like you folks did it, or maybe published the endpoint all the way out to the SUP proxy?

Regardless, I think the value of app connection is simply management.debugging. Like you said, you can get client logs. I believe there's an additional layer of encryption at network layer as well.

[midhun_vp]

As I mentioned earlier the app connection is needed for features like security, push notifications, management and monitoring of app.

I am assuming that you are developing the app without registering the user by directly using the whitelisted URL. That is not recommended and there is no advantage of doing that. The licensing is based on the number of users registered.The app should register with the server to get the advantage of the product.

Midhun VP

[Former Member]

Hello Virinchy p,

No, in this case we are not creating or using MBOs. I just brought it up in comparison that after creating app connection in MBO dev model, developer did not need worry about passing user credidentials anywhere. Creating a application connection In REST API do not seem to offer the same kind of possibilities in client side.

[Former Member]

Hi Daniel-Jay,

No, clearly the app connection is not needed for retreaving the endpoint. This is the case at least with SUP 2.2. We have configured the the proxy into domain x and it's possible to interract with the backend without creating the app connection.

[midhun_vp]

The approach mentioned is not recommended. There is no advantage of using this approach where you whitelist an end point URL and using the URL directly in app. It is equal to directly using the end point in the app without whitelisting it. You will get advantage of the product only when you register the app with the server.

Midhun VP