You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
4
+
5
+
#### When to use
6
+
The RFC Connector enables several useful scenarios:
7
+
- Frontend/Backend Split: abap2UI5 apps are implemented in the backend, but users only have access to the frontend server
8
+
- Legacy Systems (e.g. ECC): abap2UI5 can be downported and installed on older systems and then triggered from a newer system via RFC
9
+
- Multi-System Landscapes: abap2UI5 apps distributed across multiple systems can be accessed centrally from a single entry point
10
+
11
+
12
+
#### Architecture
13
+
14
+
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.
_Prerequisite: Set up a destination in SM59 that the source system can be called via RFC. abap2UI5 need to be installed in both systems._
22
+
23
+
Steps:
24
+
1. Install the [abap2UI5 RFC Connector](https://github.com/abap2UI5-addons/rfc-connector) via abapGit on both system
25
+
2. Replace in the HTTP handler the destination `NONE` with your Source System Destination
26
+
3. Call in your browser the endpoint `.../sap/bc/2ui5_rfc`
27
+
28
+
#### UI5 Bootstrapping
29
+
The backend system that holds the abap2UI5 apps does not need to include the UI5 libraries. These are automatically bootstrapped from the calling system:
0 commit comments