Hi Sandeep,
i am giving the full details about webdynpro.pls have a look on it
and reward me points......if u think it is usefull to you
The main purpose is......
Purpose:
Web Dynpro for ABAP or 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
● User interface accessibility is supported
● Full integration in the reliable ABAP development environment
The concept of Web Dynpro ABAP is identical with Web Dynpro Java and offers more or less the same functions
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
Web Dynpro is available both in the Java and the ABAP development environment. Platform-specific information is available under
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 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.
·
Web Dynpro ABAP: Development in Detail
This manual is an introduction to programming user interfaces for business applications using the UI technology Web Dynpro for ABAP. Consecutive sections explain the most important basics and concepts with several illustrating examples.
The programming manual is subdivided into the following sections:
● Basics
This section contains the information on how to build a simple Web Dynpro application.
● Cross-Component Programming
In this section, the previous topics are extended to allow communication across multiple components.
● Dynamic Programming
This section contains information about the dynamic manipulation of the context or layout, for example. Dynamic programming requires good knowledge of ABAP objects.
● Integration
Information about integrating different applications
● Advanced Concepts
This section covers different topics relevant to advanced projects with Web Dynpro for ABAP. These topics are self-contained and do not build on one another.
● Example Applications
In this section you can find a few short descriptions of applications that are stored in package SWDP_DEMO in your system.
● Programming Notes
Compilation of main notes about programming with Web Dynpro ABAP.
These notes are intended to help make decisions about structural issues in large-scale projects. Since, however each programming project has its own specific requirements, it is not possible to provide standard solution proposals.
In addition to this programming manual for Web Dynpro for ABAP, the following documents are available in the SAP NetWeaver documentation:
Architecture Manual for Web Dynpro
This manual describes the Web Dynpro concept, irrespective of the selected programming language (ABAP or Java).
Tools Manual for Web Dynpro for ABAP
Reference Manual for Web Dynpro for ABAP
Here, you will find all information on UI elements, classes, and interfaces relevant for development.
Future:
This is oine of the hottest technology .In future also it is having lot of ravishing oppurtunities.defenetly u have a huge career growth in that. no doubt grab the knowledge in it. be expertise. in it first,..........its a good move to you in webdynpro if time permits learn webdynpro-java also.......
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.