I have two questions regarding building Web Dynpro applications in SAP Portal 6.0:
1. what is the difference (functional and architectural) between:
a) creating iViews using SAP Portal's Web Dynpro Template and
b) deploying the Web Dynpro application as a par file inside SAP Portal;
2. we are planning to develop java iViews for SAP portal 6.0 SP14. Should we use NWDS or Eclipse with PDK 6.0? what is it that NWDS offer that Eclipse w/ PDK does not?
I will try to answer my own question. feel free to add or correct if necessary.
Web Dynpro execute outside of portal environment so typically they are slower than Dynpages. On the other hand, this is a bonus, since Web Dynpro do not need a PRT to run, they can run on a J2EE server (only SAP's for now!).
Web Dynpro are easier to develop because of the tools offered by SAP ( context mapping etc).
both Web Dynpro and Dyn Pages can access Portal services such as UME, can inherit Portal themes. So from a functionality offered to the end user they are the same.
Both use a MVC design paradigm.
Did I miss anything?
To answer your first question,
Case a: creating iViews using SAP Portal's Web Dynpro Template .
Here you are making use of the standard WebDynpro iView template provided by SAP for creating WebDynpro iViews.
Case b: deploying the Web Dynpro application as a par file inside SAP Portal
Here once you deploy the WebDynpro application as a PAR file, you can make a custom iView template out of this PAR file and create iViews based on this template.
Please refer to this thread for details.
As for your second question, it is better to develop your application in NWDS. This is because NWDS comes with all the pluggins required to develop your Portal or WebDynpro applications whereas you have to download these pluggins and extract them into Eclipse for developing your applications.
Make sure that the versions of both EP and NWDS is the same.
Hope that helped.
P.S: Rewarding points for helpful answers is SDN's way of saying "Thank You!"