Management
When used correctly, Web Dynpro is an efficient and powerful tool for building robust and reliable business applications. Web Dynpro is unlike other Web development toolsets, however, and if developers use it incorrectly, they will create poor-quality applications that are difficult and costly to maintain. This article describes the most common mistakes made in Web Dynpro Java implementations, why they occur, and how to avoid them. It then explains the key design principles that will enable you to write high-quality, low-TCO business applications and start reaping the real rewards of Web Dynpro.
Chris Whealy
Chris Whealy started working with SAP software in 1993 making assembler modifications to the RF and RV modules of R/2. He then went on to work as a Basis consultant installing and upgrading R/3 systems, starting with R/3 version 2.0B. In May 1995, he joined SAP (UK) as a Basis Consultant and ABAP programmer; however, when the first Internet boom started in 1996, he turned his attention to Web-based interfaces into SAP. This led to him working with the earliest versions of the Internet Transaction Server (ITS), and consequently, he taught the first course on this subject in January 1997. Since then, Web- based front ends for SAP functionality have been the main focus of Chris’ attention. In January 2003, he started working with Web Dynpro and has worked closely with the development team in Walldorf, both learning the product and writing proof-of-concept applications. The knowledge gained while working with the developers became the foundation for the book “Inside Web Dynpro for Java” published by SAP PRESS in November 2004. This book is now in its second edition (September 2007). Chris lives in the UK and works as the Web Dynpro Java expert for the SAP NetWeaver Regional Implementation Group (RIG) EMEA in Walldorf, Germany.
You may contact the author at chris.whealy@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
