github.com/abap2UI5-addons/http-connector

HTTP Connector

Call abap2UI5 apps on another system via HTTP.

ActiveMIT license

Repository on GitHubInstall with abapGit

What it does

The browser talks to a consumer system, which forwards each abap2UI5 roundtrip through an SM59 destination to the source system where the abap2UI5 apps run. The apps stay where they are and run unchanged. It is for landscapes where users should reach the apps of another system through one entry point, and follows the same approach as the rfc-connector with an HTTP connection instead of RFC.

  • Thin ICF handler Z2UI5_CL_HTTP_CON_HANDLER on the consumer system
  • Server endpoint Z2UI5_CL_HTTP_CON_SERVER on the source system
  • Forwards method, body, query string and HTTP status via SM59 destination
  • Apps run unchanged on the source system
  • Stateless apps only; headers and the consumer path are not forwarded

Requirements

  • Standard ABAP 7.50 or higher on both systems
  • abap2UI5 on both systems: consumer newer than 1.146.0, source 1.143.0 or newer
  • ABAP Cloud: only an unmaintained prototype branch cloud (consumer side, no CI)
  • SM59 destination (type G or H) on the consumer system with path prefix /sap/bc/z2ui5_http_srv/ and login data

Installation

Pull the repository with abapGit into a package of your own. abap2UI5 itself has to be installed first.

https://github.com/abap2UI5-addons/http-connector

  1. Install abap2UI5 on both systems, then this repository (branch standard) on both the consumer and the source system
  2. On the consumer system replace the destination NONE in Z2UI5_CL_HTTP_CON_HANDLER with your source system destination or maintain the URL constant
  3. Activate the ICF nodes in SICF: /sap/bc/z2ui5_http on the consumer system and /sap/bc/z2ui5_http_srv on the source system
  4. Open .../sap/bc/z2ui5_http of the consumer system in the browser

Usage

The addon is used through its own apps and needs no code of yours; the README shows how to start them.