Web Dynpro ABAP Client Implementation

The graphic below gives an outline of the concept of the client implementation:

Depending on the rendering device selected, the central part of Web Dynpro runtime works together with a specific client implementation. If a browser is selected, the client implementation is server-side rendering (SSR). SSR then takes on the task of communicating with the client device.

View elements are kept in user interface element libraries, see also Web User Interfaces.

With Web Dynpro for ABAP, a browser is always used as the rendering device. Data, events, and layout information are converted on the server into HTML and JavaScript and transferred together. In the case of the browser, this is done mostly on the server; for instance, the whole layout is placed on the server. The browser itself does not take on many tasks. For example, it is responsible for ensuring that a tray or the nodes of a tree can be expanded and collapsed on the client.

When data and events are called by Web Dynpro runtime, specific adapter techniques are used in the request/response cycle to convert them into the browser’s format, HTML, JavaScript, or XML. Conversely, this data is converted into data structures for ABAP objects.