Android/SCP application through RFC with ABAP backend

[emanuele_matino]

Hi expert (midhun.vp),

I need to configure the following scenario:

I have an Android application that call SCP services. SCP services need to communicate with ABAP backend through RFC protocol via SAP Cloud Connector.

How can I do?

I already set the following configuration:

• We are using SCP Identity Managment for authentication
• Set the SCC as following:

• Set the SCP as following:

About the RFC Type, when I check the connection I had the following message:

• Mobile configuration in Identity Management

Please can you check the previusly images and tell me what is missing in the configurations?

I also need the other missing steps to have an RFC connection to the backend and also the steps needed to call the SCP services with Android.

Thanks in advance for the help.

Regards.

[gregorw]

I've just tried to get a successful connection test with this configuration:

I would suggest you sick with the system number you use in the backend also for the Virtual Host.

Also do you already have the Java middleware that will translate the HTTPS calls of your Android App to the RFC? Might it be the easier option to implement an OData Service in the backend?

[Ivan-Mirisola · Accepted solution]

Hi Emanuele,

I see that you have installed your Cloud Connector using a Location ID. This setting is only used when multiple Cloud Connectors are connecting to the same Cloud Account. If this is not the case, I suggest removing the value from that field. If indeed you need this setting, then you are missing a parameter to set the location id to be used by your RFC destination.

jco.client.cloud_connector_location_id 

As a rule of thumb, keep things simple for testing purposes. Implement one feature at a time. I would do this configuration in small steps like this:

1) Configure an RFC destination without load balance and with a fixed user id and password. Then test it against the FM: RFC_SYSTEM_INFO or STFC_CONNECTION. Don't add restrictions to your backend just yet. Leave it "open" to call any RFC for now. This will give you plenty to figure out several connectivity aspects. There is a good and simple how-to document on the help that can guide you on this direction.

2) Once you have passed step 1, make your code more complex by consuming an actual RFC. Make sure you are adding simple input parameters, tables or structures to make it work

3) After you have your RFC working, it is time to make the scenario more complex, by changing it to perform load balance and tweak it a bit regarding pooling, etc.

4) Now it is time to change the authentication from fixed user to Principal Propagation - that is, if you want to pass/map users from your IdP into your ABAP system. Try using this blog as reference. It deals with the HTTP protocol, but you will first have to enable SNC on your backend in order to work.

As you can see there's still a road ahead to success, but if you trail bit by bit I am confident you will get to the finish line.

Regards,
Ivan