Skip to content

Commit f1941a2

Browse files
authored
Create rfc.md
1 parent a20f179 commit f1941a2

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

docs/advanced/rfc.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# RFC Connector
2+
3+
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.
15+
16+
<img width="600" alt="1719296908473" src="https://github.com/user-attachments/assets/6f885f04-2b70-4cb3-83d0-123473b72262" />
17+
18+
19+
#### Installation
20+
21+
_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:
30+
31+
<img width="600" alt="1719296975220" src="https://github.com/user-attachments/assets/8e7dd3dd-abd3-413f-8ec6-8a7a2be7a7ec" />
32+
33+
34+
#### Multi-System Launchpad
35+
You can also use this approach to build a centralized Fiori Launchpad that includes both:
36+
- Apps installed on-stack (on the current system)
37+
- Apps executed remotely via RFC from other systems
38+
39+
<img width="700" alt="1719297067700" src="https://github.com/user-attachments/assets/a010440d-bd82-46f9-b597-c3ad2273dbde" />

0 commit comments

Comments
 (0)