Showing posts from October, 2014

Web Dynpro

Web Dynpro is the new User Interface (UI) programming model from SAP. It was launched as a technical component of SAP Netweaver platform and is aimed as a replacement of the popular and generally used classic SAP GUI technology in the long-term.

A Brief History of Web Dynpro: The Driving Forces

(First article of the series: Web Dynpro) I first encountered the term Web Dynpro in the book - ABAP Objects, co-authored by Horst Keller and Sascha Kruger, (I believe it dated back to year 2000) – that SAP is developing the new UI technology called Web Dynpro which sounded far distant. Probably that time around SAP started the project. All development in SAP R/3 embedded business logic within SAP screens, which posed serious limitation to its use by external systems. SAP needed to separate business logic from presentation (UI) logic so as to make the applications independent of any client-software.

Web Dynpro: Reusability

(Fifth article of the series: Web Dynpro) Developing a web-application using HTML and Java script requires the developer to be careful, client-conscious and device-conscious. SAP introduced BSP technology (Business Server Pages) before Web Dynpro and it offered the flexibility to write the html and java script code alongside ABAP code and design the user-interface look and feel the way developer desired. Many developers were happy as they had more control over things and could be more creative.

Web Dynpro: Declarative Programming and Model-Driven Architecture

(Fourth article of the series: Web Dynpro) The Web Dynpro framework helps to create applications using declarative programming techniques based on MVC architecture. MVC Architecture helps in separating the user interface (visual component) from the business logic. Declarative programming techniques simplify the UI development. The developer just needs to specify the GUI elements (input field, drop-boxes, radio-buttons, etc.) on the user screen independent of the client (PC, Laptop, Mobile, etc.) and where those elements send to or get their data from.

Web Dynpro: Abstraction and Rendering

(Third article of the series: Web Dynpro) The web dynpro framework (WDF) allows for building an abstract description of the application. This description is abstract as it is not programming language dependent and just has information about the application – the metadata. The metadata is stored in XML format. This metadata code is generated automatically by the framework once the application is built. Naturally it is recognized by and conforms to standards of WDF.

Web Dynpro: MVC Architecture

(Second article of the series: Web Dynpro) When SAP decided to follow MVC Architecture for , it was a great hit with Java based applications. It became proven path for business applications. There are great advantages offered by the paradigm. MVC or Model-View-Controller architecture helps in organizing complex projects through easy development and maintenance while protecting important data. What is it and how it does that?