Therefore, the implementation only gives the rough processing skeleton: An instance for database operations, as well as an instance for the processing of the REST operation are created, the request handling is delegated to that instance, and there is a catch block for error processing in case that no instance could be determined for processing the request. The implementation of the interface method if_http_extension~handle_request() forms the uppermost level of processing. The class ZCL_JOB_DATA is declared to be responsible for all incoming requests where the request path starts with /job/attributes : Our example service is attached to the path /job/attributes. If this is the case, an instance of the handler class will be created, and the method HANDLE_REQUEST will be called.

The match process is stopped as soon as a node with an attached request handler is found. An incoming HTTP request will be analyzed by the Internet Communication Framework, trying to match the request path against the SICF path. A request handler class can be attached to a path in transaction SICF. Request handlers are classes implementing the interface IF_HTTP_EXTENSION, which consists of one single method HANDLE_REQUEST. You can inspect all the code I am discussing here on the MIGROS BSP website: It’s all in Class ZCL_JOB_DATA. In this blog, I will focus on the server side: How to implement a REST API as ABAP request handler. In two recent blogs, I demonstrated how to write web clients of REST APIs – with XML (demo application here) or JSON (demo application here) as data transfer format.

Sap ariba rest api