RFC Connector

What it does

rfc-connector puts a thin ICF handler on a consumer system that the browser talks to; the handler forwards method, body, path and query string of each roundtrip through an SM59 RFC destination to the source system where the abap2UI5 apps run, and returns body and HTTP status. The apps stay where they are and run unchanged. Use it in landscapes where users should reach the apps of another system through one entry point. It is the same approach as the http-connector, with an RFC connection instead of HTTP.

• ICF node /sap/bc/z2ui5_rfc and handler Z2UI5_CL_RFC_CONNECTOR_HANDLER on the consumer
• RFC-enabled function module Z2UI5_FM_RFC_CONECTOR on the source system
• Forwards method, body, path, query string and HTTP status over RFC
• Apps run unchanged on the source system; stateless (draft table) apps supported
• No ICF node needed on the source system

Requirements

• Standard ABAP 7.50 or higher on both systems
• abap2UI5 1.143.0 or newer on both systems
• abap2UI5 newer than 1.146.0 on the consumer to forward URL parameters
• An SM59 destination (type 3) on the consumer system pointing to the source system with login data
• Stateless apps only; request headers are not forwarded

Installation

Pull the repository with abapGit into a package of your own. abap2UI5 itself has to be installed first.

https://github.com/abap2UI5-addons/rfc-connector

1. Install abap2UI5 and this repository (branch main) on both the consumer and the source system, the same version on each
2. On the consumer system replace the destination NONE in Z2UI5_CL_RFC_CONNECTOR_HANDLER with your source system destination
3. On the consumer system activate the ICF node /sap/bc/z2ui5_rfc in SICF
4. Call .../sap/bc/z2ui5_rfc of the consumer system in the browser

Usage

The addon is used through its own apps and needs no code of yours; the README shows how to start them.

Links

• Repository, README and issues
• http-connector
• abap2UI5
• abap2UI5 documentation