abap2UI5

Appearance

RFC Connector ​

The abap2UI5 RFC Connector allows you to trigger abap2UI5 apps remotely via RFC between two ABAP systems. This is particularly useful in distributed system landscapes or when working with legacy systems that cannot directly host UI5 frontend logic.

When to use ​

The RFC Connector enables several useful scenarios:

  • Frontend/Backend Split: abap2UI5 apps are implemented in the backend, but users only have access to the frontend server
  • Legacy Systems (e.g. ECC): abap2UI5 can be downported and installed on older systems and then triggered from a newer system via RFC
  • Multi-System Landscapes: abap2UI5 apps distributed across multiple systems can be accessed centrally from a single entry point

Architecture ​

The system that calls the app (the frontend system) includes the UI5 library and bootstraps the UI. The system where the app is implemented (the backend system) does not need to host the UI5 runtime.

1719296908473

Installation ​

Prerequisite: Set up a destination in SM59 that the source system can be called via RFC. abap2UI5 need to be installed in both systems.

Steps:

  1. Install the abap2UI5 RFC Connector via abapGit on both system
  2. Replace in the HTTP handler the destination NONE with your Source System Destination
  3. Call in your browser the endpoint .../sap/bc/2ui5_rfc

UI5 Bootstrapping ​

The backend system that holds the abap2UI5 apps does not need to include the UI5 libraries. These are automatically bootstrapped from the calling system:

1719296975220

Multi-System Launchpad ​

You can also use this approach to build a centralized Fiori Launchpad that includes both:

  • Apps installed on-stack (on the current system)
  • Apps executed remotely via RFC from other systems
1719297067700