Client Implementation

The figure below provides an overview of the concept of client implementation:

Depending on the rendering device that is selected, the central part of the Web Dynpro runtime works with a certain client implementation. In the case of a browser, this is server-side rendering (SSR). SSR then takes over the task of communicating with the client device.

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

With the Web Dynpro for ABAP, a browser or SAP NetWeaver Business Client 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, most tasks are carried out on the server; the whole layout is arranged on the server, for example. 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 on the client can be expanded or collapsed.

Specific adapter techniques are used to convert data and events, as part of the request response cycle, into the browser's format, HTML and JavaScript or XML, when they are called by the Web Dynpro runtime. Conversely, this data is then converted into ABAP Objects data structures.