on 05-21-2008 5:16 AM
Hi All,
I am new to Webdynpro Java and wanted to learn the same.
Appreciate if osmeone can guide me with the below
1) Books/Links for fundamentals and Architecture
2) Books/Links for programming
3) What woukld be the best way to go about learning WD Java
4) Time frame required for the same.
Appreciat your help
Regards
PN
Hi
Look into these Links
[Web Dynpro Java Sample Applications and Tutorials for SAP NetWeaver 2004|https://www.sdn.sap.com/irj/sdn/nw-wdjava?rid=/webcontent/uuid/503f22f6-b978-2a10-bf97-ddc21267e752] [original link is broken];
[Tutorials & Samples for Web Dynpro Java|https://www.sdn.sap.com/irj/sdn/nw-wdjava?rid=/webcontent/uuid/00b64d9f-fea2-2910-c988-ee2544047f8c] [original link is broken];
Best Regards
Chaitanya.A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you have good knowledge in Java,then it will not a tedious job to learn Webdynpro.
WebDynpro for Java:
http://help.sap.com/saphelp_nw2004s/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm
Webdynpro Developer area:
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro
See this documents for more information.
Creating webdynpro component
http://help.sap.com/saphelp_nw04/helpdata/en/20/1d353ed106ec2ce10000000a114084/frameset.htm
This has it all Webdynpro examples
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
? Clear separation of business logic and display logic
? Uniform metamodel for all types of user interfaces
? Execution on a number of client platforms.
? Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
? Data flow between the front end and back end
? Layout of the user interface
? Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
? An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
? An interface for calling Web services
? A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
? The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
? The view is responsible for the representation of the data in the browser.
? The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos
hope that helps
regards
Anil
Edited by: Anil Dichpally on May 21, 2008 10:13 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.