Which One Is Better, Web Dynpro Java (WDJ) Or Web Dynpro ABAP (WDA) And Why?

This is probably one of the most asked questions in SAP technical world. This article will provide answers to all those who want to learn Web Dynpro, but are wondering which technology they should learn? It will also clear the doubts of all those who are planning to develop new Web Dynpro applications for their business scenarios, but they are not able to decide which technology they should go for?

We will compare both the technologies on various parameters and then based on the results, we will declare the winner.

The parameters on which we are going to compare these two are:

1. Availability
2. Skills Requirement
3. System Landscape, Version Control and Transport Management
4. Designtime Environment
5. Database Access
6. UI Elements and User Experience
7. Additional Functionalities
8. Performance
9. Customization
10. Transport System

1. Availability: Web Dynpro ABAP is available from Oct-2005 with Net Weaver 7.0 and Web Application Server (WAS) 7.0, from the day of its availability it is widely used and preferred UI Technology.

Web Dynpro JAVA is available from the year 2004 with Net Weaver 2004 and Web Application Server (WAS) 6.40, and is used to create applications such as the Employee Self Service (ESS) and Manager Self Service (MSS).

SAP has reduced the promotion of Web Dynpro Java; however, they are going to support it till 2018. This makes it clear that Web Dynpro ABAP will be the preferred UI Technology.

2. Skills Requirement: To develop a complete Web Dynpro ABAP application from scratch, a developer should have skill set in ABAP programming, ABAP Objects, Database concepts and Development tools.

To develop a complete Web Dynpro JAVA application from scratch, a developer should have the knowledge of JAVA development tools and object-oriented concept. Additionally, ABAP skills are required for the development of Function Modules and BAPI’s.

3. System Landscape, Version Control and Transport Management: Standard ABAP life-cycle concepts of version control and transport management applies to all Web Dynpro based applications. Web Dynpro ABAP components, Applications and other objects can be developed in one system and can be transported to the destination server by using the standard correction and transport system (CTS), just like other ABAP objects like programs or classes.

The Lifecycle of Web Dynpro JAVA application is managed through SAP Net Weaver Development Infrastructure (NWDI).

NWDI has the following three parts:

1. Design time repository (DTR);
2. Component based Build (CBS)
3. Change Management (CMS) systems.

If you want to use Web Dynpro JAVA and to manage its life cycle i.e. of version control and transport management then you will have to additionally install NWDI.

4. Design-time and Runtime Environment: Web Dynpro ABAP is integrated to ABAP Workbench (SE80) so no additional installations are required.

Installation for SAP Net Weaver Developer Studio (NWDS) is required for designing Web Dynpro JAVA applications. And J2EE Engine is required to configure the runtime environment.

5. Database Access: As Web Dynpro ABAP is integrated to the ABAP stack, database access is simple, just like in report programs and function module. You can access the database directly using the select statement.

While in Web Dynpro JAVA, Business Application Programming Interfaces (BAPI’s) are required in order to consume the same business logic.
Adaptive RFC layer is used to communicate between R3 and the J2EE Engine.

6. UI Elements and User Experience: Almost all the UI elements in Web Dynpro ABAP and Web Dynpro JAVA are same but still there are some UI elements which are not available on both the technologies.

The UI elements which are only available with Web Dynpro ABAP are Search help, Select-Options, ACFExecute, ACFUpDownload.
The ABAP Data dictionary and Mime objects are also available.
The UI elements which are only available with Web Dynpro Java are Analytics Chart UI & Column Layout.

Data modeller, Component modeller and View Designer are also available with Web Dynpro JAVA.

7. Additional Functionalities: Web Dynpro ABAP includes Floor Plan Manager, POWL and much more additional functionalities which are not there in Web Dynpro JAVA.

8. Performance: As Web Dynpro JAVA runs on J2EE web application server provided by SUN Microsystems, it has been assumed that Web Dynpro JAVA applications are much robust and scalable compared to Web Dynpro ABAP which runs on ABAP web application server. But, this is not true because Web Dynpro ABAP applications are also as scalable and robust as Web Dynpro JAVA with its multiple application server and dialog work process model.

9. Customization: Web Dynpro ABAP applications can be customized on both application level and component level. This configuration is done at design time which offers much flexibility and the developers can change the look and feel of the UI to meet with customer’s needs.

To customize Web Dynpro JAVA applications custom development component (DC) are created in Net Weaver developer studio.

10. Total Cost of Ownership: With the option of portal agnostic deployment and harmonized user interface technology, which does not necessarily requires a separate JAVA stack for Employee Self Service without the total cost of ownership of Web Dynpro Applications is much lesser than Web Dynpro Java.

Summary:

With no doubts we can say that Web Dynpro ABAP is the better choice. All applications in Employee Self Service which were on Web Dynpro JAVA are now offered by SAP in Web Dynpro ABAP with much more customizations options and superior UI elements.