Skip to Content

Executing RFCs in an ABAP backend system from a NetWeaver Cloud Application


I wrote a little tutorial explaining how to execute remote-enabled function modules (RFMs) from within a Java application running on the NetWeaver Cloud:

Executing RFC Calls from a NetWeaver Cloud Application

Currently the SAP Cloud Connector does not yet support the RFC protocol, but with the workaround described in the above document, it should be possible to call any ABAP function module in an on-premise R/3 system in a secure and effortless way. The workaround leverages an internally installed SAP Business Connector, which can be set up in half an hour, if not yet installed.

The above mechanism is not limited to calling RFMs: the Business Connector provides much more functionality, and the referenced jar file allows executing any SAP BC Service very easily, so you could for example access an on-premise database using the Business Connector's WmDB package, put/get files onto/from an internal FTP server, etc.

In this thread please report your experiences with the above procedure or any problems you encounter.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on May 22, 2012 at 07:34 AM

    Hi Ulrich,

    the link you posted refers to an image. You may want to double-check...

    BTW, there's already a document describing how-to execute RFCs here: Executing RFC Calls from a NetWeaver Cloud Application

    BR, Matthias

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Matthias,

      I know...

      When I tried uploading my document, for some strange reason the system accepted only extensions like .jpg, .gif, .png etc. It rejected my .pdf document! So I uploaded some picture I happened to have at hand as a "placeholder" and asked an administrator to replace it with the real pdf document. Unfortunately there seem to be technical problems getting the real pdf document in place...

      The link you mention above is a copy of the first version of my document from an SAP-internal discussion forum, which Steven Thorne for some reason duplicated here on SCN. I will have to ask him to delete it, as it is a bit out-dated by now.

      Best Regards, Ulrich

  • Posted on May 24, 2012 at 12:46 PM

    Ok, everybody: the real document is now uploaded! Thanks to Matthias for updating the link in the first post; I tried and failed bitterly...

    Let the fun begin...

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 29, 2012 at 10:28 AM

    Document updated to reflect the changes in the HTTP Destination API. (Moved from deprecated API to JNDI based API.)

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Szymon,

      according to that message, the internal host you try to access is in principle known, but does not respond on that port. The physical port for sapgw00 can be seen in /etc/services (on Windows <WINDOWS>\system32\drivers\etc\services). Typically, it's port 3300 for this logical port. Try accessing the location with niping from your SAP HANA Cloud connector machine.

      Best regards,


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.