HTTP Connector

Remotely Call abap2UI5 Apps via HTTP.

Same approach as the rfc-connector, just with an HTTP connection instead of RFC:

Approach

Browser ── GET/POST ──> Consumer System                    Source System
                        /sap/bc/z2ui5_http                 /sap/bc/z2ui5_http_srv
                        Z2UI5_CL_HTTP_CON_HANDLER          Z2UI5_CL_HTTP_CON_SERVER
                          │                                  │
                          └── HTTP (SM59 destination) ──────>└──> z2ui5_cl_ui5_http_handler

The consumer system receives the browser request, forwards method and body via HTTP to the source system and returns body and HTTP status of the response. All abap2UI5 apps run on the source system.

Installation

Prerequisite: Set up a destination in SM59 (type G or H) on the consumer system pointing to the source system with path prefix /sap/bc/z2ui5_http_srv/ and login data maintained. abap2UI5 1.143.0 or newer needs to be installed in both systems — the connector calls z2ui5_cl_ui5_http_handler, which first shipped with that release.

Steps:

1. Install this repository on both systems.
2. Replace in the HTTP handler Z2UI5_CL_HTTP_CON_HANDLER the destination NONE with your Source System Destination (or maintain the URL constant instead).
3. Activate the ICF nodes /sap/bc/z2ui5_http (consumer system) and /sap/bc/z2ui5_http_srv (source system) in transaction SICF.
4. Call in your browser the endpoint .../sap/bc/z2ui5_http

Limitations

• Stateless apps only. A stateful app (client->set_session_stateful( )) needs the ICF session of the system the app runs on; the consumer opens a new HTTP connection per request and does not forward the sap-contextid header the frontend uses to address that session. Apps keeping their state in the draft table — the abap2UI5 default — work unchanged.
• The consumer forwards method, body and status, not headers. Everything abap2UI5 needs for a roundtrip travels in the body; a request header an app reads through the user exit on the source system does not.

Contribution & Support

Pull requests are welcome! Whether you're fixing bugs, adding new functionality, or improving documentation, your contributions are highly appreciated. If you encounter any issues, feel free to open an issue.