Show TOC

Background documentationProcessing HTTP Requests in the ABAP Work Process Locate this document in the navigation structure



The ICM receives the HTTP request, as the URL contains the combination of server name and port to which the ICM responds.

The ICM decides on the basis of the URL whether local handlers need to be called, and if so, which ones.

If the ABAP handler of the ICM receives the request, the HTTP request should be processed by an ABAP program in the work process (for example, by an application created with Web Dynpro ABAP).

Process Flow

The following graphic shows the entire process for this case - from the arrival of an HTTP request from a Web client, to the receipt of the response by the client.

This graphic is explained in the accompanying text.

  • The ICM stores the data it receives in a memory pipe (located in the shared memory) and informs the dispatcher.

  • The dispatcher enters the ICM request in the dispatcher queue, creates a new context (unless the system is in stateful mode and a context already exists), and chooses a work process.

  • This work process (task handler) executes a special ABAP report to run the initialization of the HTTP framework.

    Then it reads the data from the memory pipe, processes the request (via ICF and the HTTP request handler), and writes the response back into the MPI.

    Then, the work process signals to the ICM that it has finished processing the request.

  • The ICM sends the response data back to the client.