Skip to Content
avatar image
Former Member

Why WebDynpro ?

Hi all,

I have in recent times got introduced to PDK. Coding in this case is done using HTML-B , JSPDynpage ,DynPage .....etc., The more i work in this line the more I feel that these alone will serve all the purpose of application development.

What additional advantages does WebDynpro provide apart from supporting different clients.When I am using my computer browser as the only client system.. does it offer any other advantages.....

Though WebDynpro UI development is faster, most of the time due to lack of flexibility in design (lack of flexibility in personalization) i feel its easier to opt for other ways of UI creation using PDK..

I am not sure if I am correct.. but i want to know other people's opinion in this regard.. Hopefully it will give a deeper insight on what webdynpro is really capable of....

Any inputs or comments or suggestions ..welcome..! 😊

Regards

Bharathwaj

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 01, 2005 at 07:20 AM

    How about these:

    1. Web Dynpro comes for free with Web AS 6.40

    2. You don't need to install an Enterprise Portal to run Web Dynpro's.

    3. If you build the UI using Web Dynpro's you have the option to display them in any kind of portal (not just SAP Enterprise Portal) or standalone.

    4. Web Dynpro for ABAP will become available in the future, offering improved SAP backend communication performance.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      To me, the "customers" of Web Dynpro are the developers that create Web Dynpro applications or even other frameworks using Web Dynpro (like the Pattern framework), not the users of the resulting applications.

      Armin

  • avatar image
    Former Member
    Jul 05, 2005 at 07:06 AM

    hi bharath

    i too had the same doubt. coz with pdk you can do all you want, even use the jco client connectivity ( though requires more coding than webdynpro). But as far as i know it loads the entire framework. EP is designed to handle communication between applications ( and others like km) rather than connectivity to the database.

    Mainly the ui elements and connectivity to sap(rfc) in webdynpro score over EP.

    regards

    vln

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 05, 2005 at 07:22 AM

    Hi Karin,

    - Interoperability with other applications based on different Web frameworks (e.g. JSF) since we know that no Web frameworks fits all needs. Communication and openess is also the key.

    I dont have the slightest idea about JSF.Could you suggest me some other framework and some links which will help me to understand this interoperability of WebDynpro with other frameworks.

    Regards

    Bharathwaj

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Bharathwaj,

      Something I would like to add to Karin Schattka's Note.

      Web Dynpro could be viewed from few different perspectives

      Developer Perspective:

      Highly sophisticated web user interface framework for building business applications.

      Provides pre-build infrastructure to connect to R/3 and any industry standard model ( XML, EJB, SQL). If new standard model (web-services would a recent example) comes along and you would like to use, you can plug in and use.

      Let me give you a very simple example: You have web UI built using EJB and for some strategic reason you would like to change this model to web services, you could change it and still use same web UI with ease.

      The point I am trying to make here is “<b>FUTURE PROOFING YOUR APPLICATION</b>”. This is a win big for developers.

      SAP Perspective:

      I am no technology evangelist; I believe Web Dynpro is real strategic Web User Interface tool and best Web User Interface technology I have seen and used.

      SAP developed various Web User Interface technologies with every new technology that has come out.

      I think you might have seen all this

      BSP - HTML + Dynamic rendering (ABAP Based)

      HTMLB - JSP (Java Based)

      PRT API – JSP based Portal API

      Mobile User Interface tools for Mobile infrastructure

      By the end of the day we have all this technology/ programming options, which puts quite a burden on everyone (developer, customer, SAP) to keep up.

      SAP can’t afford to build UI tools for every new technology that’s coming out, so the concept of Model Driven Architecture comes into picture. Web Dynpro is Meta –Data driven programming environment that kind of shields technology (Web-BSP, JSP, and Mobile User Interface) / programming language (JAVA, ABAP) behind the tool.

      At a very high level any UI development would be done at Web Dynpro level (MVC, COMPONENT REUSE) and the rest is left for the tool to generate for the target technology.

      The point I am trying to make here is “<b>SAP IS FUTURE PROOFING IT’S TECHOLOGY OPTIONS AND TOOLS</b>”. This is a big win to SAP and its customers.

      The future releases of Web Dynpro would have UI Patterns, Guided Procedures, which I believe would take user interface development to next level.

      Please let me know if I could be of any help to answer any questions reg. this note.

      Thanks

      Sridhar

      Message was edited by: Phani Edala

      Message was edited by: Phani Edala

  • avatar image
    Former Member
    Jan 06, 2006 at 03:27 PM

    Hi Bharathwaj

    Some advantages of WebDynpro are discussed below:

    1. Different implementation languages are supported.

    2. Strict separation of layout data and business data through use of the Model View Controller concept.

    3. The use of declarative and graphical tools significantly reduces the implementation effort.

    4. Syntax check at design time.

    5. The use of declarative and graphical tools significantly reduces the implementation effort.

    6. Web Dynpro supports a structured design process.

    7. Stateful applications are supported – that is, if the page is changed, the data that are required again remain intact, so you can access the data from a previous page again.

    8. Reuse and better maintainability by using components.

    9. Automatic data transport using data binding.

    10.Web Dynpro for ABAP is also available now offering improved SAP backend communication performance.

    If you want more details i'll provide you.

    thanks & regards

    Madhusudan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Madhusudan's bullets/points are very apt. As usual I started with jspdynpage and then when came across WD it was painful. But once you are aquinted with WD its the easiest/quickest env to develop 3 tier applications. I dont think users of the applications would say the UI is bad. Also SAP customers/partners are benefited as well bcz of the rapid development. Reg the flexibility of UI elements I think it is a development process. The WD(as DCs) in a big team env with NWDI is a big plus.

      Thanks.

      The other advantage is the WD metadata may be used for ABAP WD also(This is completely my guess).