Professional Documents
Culture Documents
Web Dynpro For ABAP: IBM Global Business Services
Web Dynpro For ABAP: IBM Global Business Services
Session Overview
Web Dynpro is a programming model provided by SAP. Web Dynpro is
implemented in Java and ABAP. It is suited to generate standardized user
interfaces (UIs) using a declarative approach, resulting in a minimum time effort
to realize Web applications.
The advantages of using the Web Dynpro programming model (compared to
other established Web programming models) will be explained in this unit. In
this context, the basic architecture and functionality of Web Dynpro will be
summarized.
Learning Objectives
After completing this unit, you will be able to:
Describe the declarative programming approach used to create Web
Dynpro applications.
Explain the benefits resulting from this metadata approach.
List the most important elements that are part of a Web Dynpro application
and that can be defined declaratively
Achieve Independence
run on multiple platforms - Browser, Smart
Client, Mobile Device,
Development Benefits
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.
10
11
Meta-model Declarations
Custom Coding
Guarantees universality
Data Flow
Componentization ...
12
Controller
Event handling
Application data update
Control flow definition
Model
Application data definition
Connection to business
functionality
13
14
Controllers
Context Data
Eventing
Methods
Attributes
Component Interface
Interface Controller
Interface View
15
16
17
View
Is embedded into window
Defines the visible layout via
predefined UI elements
Dont contain any HTML or scripting
UI elements
Are the smallest UI building blocks
(button, input field,)
Available as provided UI element
libraries
Have properties which steer their
behavior
Can be nested with Container UI
elements
Are positioned in hierarchical structure
18
19
UI Element Categories
Various categories of UI element are supported
View Controller
Stores Data in Context
Methods access context data and
Model layer
Supply functions fill context nodes
Actions for event handling
21
22
View Assembly
The Subset of views visible at any point of time is known as a View Assembly.
Navigation causes either specific views within a view area to be replaced, or it can
cause entire view combination within the window to be replaced
View Assembly 1
23
View Assembly 2
View Assembly 3
Context Mapping
Component Controller
Controller which is the backbone of the Web
Dynpro component
Has its own Context
Contains the logic for interaction with the
model (ABAP class, function modules,
BAPIs, Web Services)
Context Mapping
Nodes of Component Controller context can
be mapped to nodes of other contexts
Framework cares about data transport
(references)
24
Context Mapping
25
Data Binding
Context
Mapping
26
Which inbound plug will act as the entry point for the
nominated interface view (this inbound plug must be
of type Startup)
27
Session Summary
You should now be able to:
Describe the declarative programming approach used to create Web Dynpro
applications.
Explain the benefits resulting from this metadata approach.
List the most important elements that are part of a Web Dynpro application
and that can be defined declaratively
28