RFC Connector

The abap2UI5 RFC Connector calls abap2UI5 apps remotely over RFC between two ABAP systems. This is handy in distributed system landscapes or with legacy systems that can't directly host UI5 frontend logic.

When to use

The RFC Connector enables several useful cases:

• Frontend/Backend Split: abap2UI5 apps live in the backend, but users can only access the frontend server
• Legacy Systems (e.g., ECC): downport abap2UI5 to older systems and call it from a newer system over RFC
• Multi-System Landscapes: one entry point reaches abap2UI5 apps spread across multiple systems

Architecture

The system that calls the app (the frontend system) ships with the UI5 library and bootstraps the UI. The system that runs the app (the backend system) doesn't need to host the UI5 runtime.

Installation

Prerequisite: Set up an SM59 destination to call the source system over RFC. Install abap2UI5 on both systems.

Steps:

1. Install the abap2UI5 RFC Connector via abapGit on both systems
2. In the HTTP handler, replace the destination NONE with your Source System Destination
3. In your browser, call the endpoint .../sap/bc/2ui5_rfc

UI5 Bootstrapping

The backend system that holds the abap2UI5 apps needs no UI5 libraries. The calling system bootstraps them automatically:

Multi-System Launchpad

You can also use this approach to build a unified Fiori Launchpad that combines:

• Apps installed on-stack (on the current system)
• Apps called remotely over RFC from other systems