SAP RFC via OData protocol using HANA Cloud Platform / HANA Cloud Integration

[former_member182650]

Hi folks,

I am trying to find some information in order to know if it is possible this escenario:

1. Custom taylor-made UI5 app developed on SAP WEB IDE

2. Reuse existing RFCs functions from SAP customer on-premise systems.

I would to know if it is possible to expose RFC via OData protocol without Gateway (and without custom development like ). Is it possible through HANA Cloud Integration (eg. OData Provisioning) or our customer will require a SAP Gateway on-premise?

Thanks in advance

Kind regards

[nageshcaparthy · Accepted solution]

Hi Angel,

Best option would be to have GW and since there are Cloud services now, you have few options:

1. Have your Exisiting RFC to export SOA Services (WSDL) files and integrate using HCI Services and convert to oData.

Reference Link:

Note: This is still in beta stage and not ready for production.

2. Use HCP oData Provisioning which is renamed from HCI oData Provisioning

Note: This is also not GA and not available for production with full GW developments

3. Have GW on Premise Hub Model and expose them via cloud connector.

Option 3 would be best and all customer use this approach for developments.

Hope this helps.

Question: Custom taylor-made UI5 app developed on SAP WEB IDE

What do you mean by "Custom taylor-made" how are the odata services used here?

Regards,

Nagesh

[former_member182650]

Finally we will use GW on Premise Hub Model and expose them via cloud connector as the best suitable option. Thanks!

[Ulrich_Schmidt]

Hi Angel,

in addition to what Nagesh already said, I would like to point out one more possibility, which may be possible in your scenario and which requires only one additional component to be installed (the SAP Cloud Connector):

1. UI5 app calls a custom servlet on your HCP app

2. The servlet makes use of the built-in JCo in HCP

3. JCo calls backend RFC module via Cloud Connector

You don't get the data in OData format, but this does not need to be a disadvantage. The advantage is that no extra conversion step (NW Gateway or HCI) is required, so the performance is probably as good as it can get. The data is transferred from backend to JCo directly in binary RFC format, and the servlet may then adjust it a bit for the UI, if necessary.

An entry point to get started with this is:

Invoking ABAP Function Modules via RFC Protocol

Regards, Ulrich