Beruflich Dokumente
Kultur Dokumente
SAP AG 2001
WebDynpro Overview
WebDynpro Goals
SAP AG 2001
Utilize state-of-the-art, standards-based Web development technology Guide application development in creating consistent and user-friendly applications
Extend existing Web infrastructures with tools that allow to easily design, develop, deploy, maintain and customize 80% of business (Web) applications with 20% of the usual effort and cost! Make sure that Web Dynpro applications can run in the SAP Portal
WebDynpro
SAP AG 2001
What is WebDynpro?
A set of design- and deployment-time tools for
(dialog) process modeling view editing pattern-based view assembly business data types definition data-binding and input validation rendering error handling dialog flow customization personalization tracing and profiling batch input and automatic testing
WebDynpro Applications
SAP AG 2001
persisting
View
visualization
Controller
Controller Controller
Controller
selecting
processing
Data separation
State is kept in contexts Contexts are used for data transport between views, controllers and model
Model Model WebDynpro Application
WebDynpro Features
SAP AG 2001
UI Elements
Additional elements compared to Dynpro Possibility to construct composite UI elements from elementary ones
Dynamics
The UI (framework) allows for dynamically constructing a user interface at runtime (e.g. for reporting purposes) However, the recommended way is to define screens statically with welldefined exceptions (e.g. place-holder UI element serving as starting point for dynamically constructed sub-view)
Input Validation
Syntactic validation can be done automatically (meta data information) To avoid redundancy (checks must be made on server too), the checks are derived from a single point of definition (e.g. data type repository)
Eventing
UI elements raise events as a result of user interaction Processing of events can take place on the server and on the client Both client and server logic operates on context only
Caching
Caching of layout and content are independent To allow client-side caching a location-independent data container derived from the context definition is used
Usability
Three reuse pattern levels
composition component
patterns
UI
element patterns
support the selection and usage of such patterns
Navigation
Declaration of the dialog flow/page sequence/view composition
allows eases
Data binding
UI elements are bound to application data via context At runtime, data container is used for data transport Data container is derived from current set of contexts
always
side
flicker-free
Simple Client
ID
Server
Product Ov erv iew
De s c ri p ti o n av ailable
Data Merging
Viewed Page
10 11 12 ABC 40 yes yes yes ABCPro ABC50+ Chose a product from list to view the details.
< Product ID= "11" Available= "yes"> < Description> ABC Pro < /Description> < /Product> < Product ID= "12" Available= "yes"> < Description> ABC 50+ < /Description> < /Product>
Application
Data Merging
Static Layout
ID De s c ri p ti o n av ailable
Viewed Page
10 11 12 ABC 40 yes yes yes ABCPro ABC50+ Chose a product from list to view the details.
Dynamic Data
< Product ID= "12" Available= "yes"> < Description> ABC 50+ < /Description> < /Product>
< Product ID= "11" Available= "yes"> < Description> ABC Pro < /Description> < /Product>
10
Big Picture
SAP AG 2001
11
Dynpro Converter
Dynpros
ABAP Generator ABAP / BSP BSP Runtime Web Dynpro Common Native (Remote) WebAS Runtime Services Services
Current Picture
SAP AG 2001
12
DATA
Later