hi Ramu,
welcome to WebDynpro for ABAP .
prequisites .
It was bundelled with Net weaver2004's .If you have mySAP businesss suit it will be with it . You need ECC6.0 and WAS 7.0 .so I doubt will it be avilable with 4.7 .
Other than that
For Web Dynpro ABAP there are configuration settings for the areas ICM and ICF, as well as for the View Designer.
· HTTP/HTTPS must be set in the ICM (see also Displaying and Changing Services).
· The following configuration prerequisites must be fulfilled:
¡ ICF services must be activated.
If a service is not activated by default, you can activate it from the SAP Implementation Guide (IMG). In transaction SPRO choose Display SAP Reference IMG. The path in the Implementation Guide for SAP NetWeaver is: Application Server ® Internet Communication Framework ® Activate HTTP Services or Activate Services in Installation.
For more information see SAP note 517484.
¡ Administration of (ICF) server functions (authorization assignment): Administration of Server Functions
¡ Administration of (ICF) client functions (creation of RFC destinations, and so on): Administration of Client Functions
· For the layout editor in the View Designer, in addition to the services for Web Dynpro ABAP listed in note 517484, the following services must be activated:
¡ /sap/bc/webdynpro/sap/public/bc/viewdesigner/
¡ /sap/bc/wdvd/
SSO must be set up on the respective application server (see also the security section in the table).
1) Web Dynpro ABAP
As the name suggests Web Dynpro for ABAP uses exactly the same meta model as its cousin Web Dynpro for Java. A Web Dynpro component, a Web Dynpro view, a Web Dynpro model, a Web Dynpro controller have the same semantics both for ABAP and Java. The main difference is the designtime environment, the development infrastructure and the runtime environment.
The designtime environment is properly embedded in the ABAP Workbench where Web Dynpro artifacts are simply a new category like BSP applications or classical dynpro based applications before. Also no surprises regarding the development infrastructure. The correction and transport system keeps track on all changes that are done, versions them and helps to propagate the Web Dynpro application from development to production like you would do with ordinary BSP or dynpro-based applications.
Last not least the execution platform is the ABAP server that produces application content ready to be integrated in the NetWeaver Portal seamlessly. Features like portal eventing can be used between applications written in ABAP or applications developed with Java.
2 ) I can give you links that can help you a lot.
First of all start doing SAP SDN tutorials .
Create some compenents with BAPI , Component usage and ALV .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02e1fa45-0801-0010-10a0-f1c...
/people/marilyn.pratt/blog/2005/12/20/web-dynpro-for-abap
Try to Download demo tutorials from SDN library & Try to search WebDynpro ABAP WebLogs .
Wait not just that SAP has provided you with ample demo example of WD ABAP already bundled with SAP . Just Try out Components starting with WDR . I can tell you few like WDR_TEST_EVENTS ( It shows how every UI elments to use )
See packages like SWDP_DEMO , SALV_WD_DEMO
there are many more .
/people/marilyn.pratt/blog/2005/12/20/web-dynpro-for-abap
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a282c952-0801-0010-1eb5-87953e03...
Cheers
Parry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.