‎2007 May 30 4:04 PM
Hello Experts,
Can any one gimme some good idea about web dynpro... I am planning to learn that, I do have lot of links to go through but not the basic stuff
so before I start reading those can anyone give me some overview of web dynpro what it is for and what are the basic requirements to learn that and what actually this contains...
I really appreciate your valuable time..
SIRI
‎2007 May 30 4:07 PM
‎2007 May 30 4:06 PM
hi Siri,
I have a very good document on that . Give me your mail ID.
Regards,
Santosh
‎2007 May 30 4:24 PM
hi Santhosh,
My id is sriy2303@yahoo.co.in can you send the document across this id plz...
‎2007 May 30 4:43 PM
hi,
I Have sent it on to your mailid. Please look for the same.
Regards,
Santosh
‎2007 May 30 4:48 PM
Ya do have all these links with me
I need the basic info what is it for ....... and where exactly v will make use of this webdynpro
can some one gimme some idea plz
SIRI
‎2007 May 30 6:49 PM
‎2016 Jan 22 9:16 AM
‎2016 Jan 22 12:38 PM
‎2007 May 30 4:07 PM
‎2007 May 30 4:14 PM
Hi Sri,
<b>WEBDYNPRO :</b>
A Programming Model for User Interfaces
Defines a standard structure for user interface applications
Derived from the MVC (model-view-controller) design pattern
A Set of Tools for User Interface Design
Focus on graphical modelling
Code is generated from meta-model declarations
Integrated in SAP NetWeaver Developer Studio and the ABAP
Workbench
A Runtime Environment for Applications
Framework running on SAP Web AS server offers common services
A Technology for Software Modularization
Components help structure applications and support pattern-based
UIs
Benefits
Deliver an Enterprise Quality
Web Development Environment
minimize coding, maximize design
separate layout and logic
support arbitrary backend systems
support reuse of components
configuration of UI patterns
support Web services and data-binding
Achieve Independence
run on multiple platforms
Improve User Experience through a
"High Fidelity Web UI"
browser based, zero footprint
screen updates w/o page reloads
client-side dynamics
performance through caching
and now about WD ABAP
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.
Refer these links :
http://help.sap.com/saphelp_nw2004s/helpdata/en/20/1d353ed106ec2ce10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/fed073e5-0901-0010-4eb... [original link is broken]
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/content.htm
http://www.sap-press.de/download/dateien/1079/sappress_web_dynpro_for_abap.pdf
Reward if useful.
Thanks
Aneesh.
‎2007 May 30 4:56 PM
Hi,
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
● The use of declarative and graphical tools significantly reduces the implementation
effort
● Web Dynpro supports a structured design process
● Strict separation between layout and business data
● Reuse and better maintainability by using components
● The layout and navigation is easily changed using the Web Dynpro tools
● Stateful applications are supported that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
● Automatic data transport using data binding
● Automatic input check
● Automatic operation of the Web Dynpro application using the keyboard
● User interface accessibility is supported
● Full integration in the reliable ABAP development environment
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
Regards,
Ferry Lianto
‎2007 May 30 5:39 PM
Ok Aneesh and Ferry thanks a ton for the info you provided to me
Thanks a lot for your valuable time
SRI
‎2007 May 30 5:44 PM
You may notice that a lot of the information can be found in the online help.
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Regards,
Rich Heilman