web dynpro componentization

1

SAP NetWeaver ’04 – Web Dynpro Componentization

Web Dynpro Componentization

SAP NetWeaver ’04

Bertram Ganz, Christian Georgi, Michael Wenz – SAP AG

SAP TechEd ‘05

© SAP AG 2005, SAP TechEd ’05 / CD355 / 2

Section Overview – Three Building Blocks

ComponentBasics

ComponentUsage Relations Demo

Component-BasedApplicationArchitecture

Hands-On Excercise

ReferencingComponentsNetWeaver

DevelopmentInfrasturcture Component

Interface Definitions

Hands-On Excercise

1

2

3

2



Web Dynpro Component Concept

Web Dynpro Components …

are the fundamental blocks which build Web Dynpro applications

have a specific controller anatomy (whitewhite--boxbox--approachapproach)

have specific interfaces for fulfiling visual, programmaticand context-specific needs (blackblack--boxbox--approachapproach)

are the only unit of reuse in Web Dynpro

1

2

3

4


Visual Facet

Web Dynpro Components – A White-Box Approach

Web Dynpro ComponentView Composition

Window

Custom ControllerCustom

Controller

Window

View LayoutView

LayoutViewViewView

ControllerView

Layout

Window


ControllerInterface View

Controller

Controller FacetComponent Interface ControllerComponent Interface View(s)

Model Interface

Custom Controller

ComponentController

3



Visual Facet



WindowWindow

View LayoutView

LayoutView

Layout

Window

Component Interface View(s)

Visual Facet

The Component UI is modeledinside one or many windows

A windowwindow contains the viewviewcompositioncomposition (views, view setsand the navigationnavigation graphgraphconsisting of linked plugs )

A viewview layoutslayouts contains a treeof Web Dynpro UI-elements

There is a 1:1 1:1 relationrelation between a window and its componentinterface view.


Visual Facet


Web Dynpro Component

View Composition

View LayoutView

LayoutViewViewView

ControllerView

Layout

Controller FacetView Layout and View Controller

Every View-Layout has a corresponding View Controller

The View-Controller is there for …storing and referencing (UI-relevant) context data (data-binding, context mapping)handling user actionstriggering navigation stepsdynamically modifying the view layout

1:1

4





Window


Controller

Window

View LayoutView

LayoutViewViewView

ControllerView

Layout

Window

ComponentController



Controller

Visual Aspect Controller FacetComponent Interface View(s)

1

2

Non-View Controllers

Component Controller (1)

Custom Controllers (0..n)

Provide global services

Store global context data

Eventing

Context-to-model binding

Provide public interfaces to other controllers

Custom Controller

Model Interface




Controller FacetController Interfaces

NonNon--ViewView Controllers canexpose an interface (foraccessing the context, calling methods and subscribing to events) to other controllers

Controllers have to define a controllercontroller usageusage relation in order to access the interfaceof another controller

View controllers do notexpose such an interface to other controllers

ComponentController

View Controller



Controller


ControllerCustom

Controller

5





Window


Controller

Window

View LayoutView

LayoutViewViewView

ControllerView

Layout

Window

ComponentController



Controller


1

2

Interface View Controllers

Implement event handlers which are called when ..

starting (start-up plugs) Web Dypro applications a component is reached via navigation (inbound plugs)

Allow fireing outbound plugs (navigation)

Allow firing exit plug

Have no own context, public methods or events

Custom Controller




Window


Controller

Window

View LayoutView

LayoutViewViewView

ControllerView

Layout

Window

ComponentController



Controller


1

Model Interface

2

Components and theirModel Usages

ProxysProxys connect to the backend system like mySAP or Web Services

ModelModel interfaces provide access to the backend

Data transfer between controller context and model objects is based on a contextcontext--toto--model model bindingbinding relation

Custom Controller

context-to-

modelbinding

6



Visual Facet



Window


Controller

Window

View LayoutView

LayoutViewViewView

ControllerView

Layout

Window

ComponentController

Custom Controller



Controller

Controller FacetComponent Interface ControllerComponent Interface View(s)

Model Interface


as a

BlackBox


as a

BlackBox


Visual Facet

Web Dynpro ComponentWeb Dynpro Component

Web Dynpro Components – A Black-Box Approach

Controller Facet

Components are theblocks which build Web

Dynpro Applications

1

ComponentInterface View(s)

5

ComponentInterface Controller

2Web Dynpro Application

6

ProgrammaticProgrammaticFacetFacet

MethodsEvents

3

DataData Binding Binding FacetFacet

(External) ContextMapping

4

Visual Visual FacetFacetStartup PlugsInbound PlugsOutbound PlugsExit Plugs

7

7



Component Usage Relations

ChildComponent

ChildComponent

ParentComponent

Component Usage

The parent component must explicitly define a component usage relationcomponent usage relationfor embedding another child component

It acts like a variablevariablereferring to component or component interface definition

At runtime it is associated with a concrete component component instanceinstance

usecomponent



Component Usage

Declared inside a Web Dynpro Component (parent)

Provides two alternative ways of lifecycle lifecycle managementmanagement for the associated component instance

Handle to component factory

Related API: IWDComponentUsageIWDComponentUsage

ChildComponent

ChildComponent

ParentComponent

usecomponent

Parent Component

Controller

Child

Com

ponentU

sage

Child

Com

ponentU

sage

IWDComponentUsageAPI

componentvariable

8




ParentComponent

UI

Com

ponentU

sage

UI

Com

ponentU

sage

ControllerWindow

Child

Com

ponentU

sage

Child

Com

ponentU

sageComponent

Interface View

Component Interface

View

ComponentInterface

Controller

ComponentInterface

Controller

create-Component()

Component Usage

Provides access to instanceinstance of embedded child component

Enables access to the interface controller

Enables embedding the component’s interface view(s)

Optional: e.g. faceless components do not have interface viewsIn the embedding window, interface views behave like “normal” views


Managing Component Lifecycles

Lifecycle Property of a Component Usage

createOnDemandcreateOnDemand: Web Dynpro Runtime automatically creates a component instance on demand (e. g. when thecomponent gets visible on the UI) and destroys it again

manualmanual: component instance lifecycle must be programmaticallymanaged by the the application developer using theIWDComponentUsageIWDComponentUsage-API

9



Web Dynpro Component Diagram

We propose the following diagram type for visualizing Web Dynpro component relations (based on the UML 2.0 )

Ports of a Web Dynpro Component

A Web Dynpro component has special entry points (portsports) between the component’s outer environment an its inner part. A port can be seen as the specification of an interaction pointinteraction point on the hull of a Web Dynpro component.

ChildComponent

ChildComponent

ParentComponent

<< usecomponent >>

Visual PortsVisual Ports: Component Interface Views (0..n)(inbound plugs, outbound plugs, paramters for the inbound plug event handler)

Service PortService Port: Component Interface Controller (1)(context, methods, events)


Web Dynpro Component Diagram

Connectors between Web Dynpro Components

A connector links a Web Dynpro Component with a port of another componentThe connectorconnector visualized by linking a socket symbolsocket symbol with a ball symbolball symbol.The socket symbolsocket symbol starts from the component user The ball symbolball symbol starts from the component interface port of the used component

Note:The graphical representation mustnot explicitly contain the relationdependency (usage relation)

ChildComponent

ChildComponent

ParentComponent

<< usecomponent >>

IExternalIExternal Interface (Comp. Interface (Comp. InterfInterf. C:. C:Ball notation for an exposedexposedinterface

can be omitted

Socket notation for a requiredrequiredinterface

10



Section 2 – Component Based Application Architecture

ComponentBasics



Hands-On Excercise

ReferencingComponentsNetWeaver

DevelopmentInfrasturcture Component


Hands-On Excercise

1

2

3


Breaking Applications into Parts: Components

Scenario 2UI Component

MasterComponent

Scenario 1 UI Component

ModelComponent

Model Interface

Components are the blocks

which build Web Dynpro Applications.

11




Components hide implementation behind an

interface (black box approach)

BenefitsBreak down applications into manageable parts

Distribute work between developersStay independent of implementation details (black box approach)

Construct reusable entitiesA component can be used in several other components

Order ManagementComponent

Order DetailComponent

AddressComponent

Customer DetailComponent

Employee Component

AccountComponent

AddressComponent



Components concentrate reuse in one element

(components, not views …)Clearing

Component

AddressComponent

AddressComponent

BenefitsMulti-instance capability

A component can embed another one more than once

Relieve developer from instance managementNo multi-instance capability for parts of a component (views, controllers)Create (non-view) controllers on demandGet access to controller by specifying its type name

12



Web Dynpro Component Types

UI Components Faceless Components

ModelComponent

ConfigurationComponent

Visual Components

Address EntryComponent

MasterComponent

Layout Components

ServiceComponent

Component types are only an application design concept


Web Dynpro Component Types – UI-Components

UI Components

Visual Components

Address EntryComponent

MasterComponent

Layout Components

ServiceComp.

User Interface Components

Visual Components:Visual Components:

Provide user interactionExample: address entry form

Layout Components:Layout Components:

Arrange the visual components into screensOnly needed for providing uniformly structured screens in large applications

Service Components (with UI):Service Components (with UI):

Provide reusable UI service


13



Web Dynpro Component Types

Faceless Components

ModelComponent

ConfigurationComponent

Service Comp.

Faceless Component

Model Components:Model Components:

Embed models and expose them in their component interface context

Configuration Components:Configuration Components:

Special type of model component for storing and retrieving configuration data



Components: Component Types

Use specialized Web Dynpro ComponentTypes

User Interface ComponentsVisual componentsLayout components

Faceless / Model ComponentsService Components

Component types are only an application designconcept

Keep UI components and faceless componentsindependent of each other to be able to exchange the other part if this is necessary

AddressModel

Employee Component

Address Model Component

ClearingApplication


14



Allowing Reuse and Extensibility: Granularity

Finding the right component granularity

the application might notbe performant

resulting „sea“ of components might reduce

maintainability

Model Access Layer

UI Layer

Too many smallcomponents

1

best reusability, extensi-bility and maintainability

allows distributing workbetween several

developers

Right componentgranularity

Model Access Layer

UI Layer

Model Interface

2

Model Access Layer

UI Layer

Model Interface

reusability is reduced

distributing work betweenseveral developers is

harder

Too large components

3


Model Access Layer

UI Layer

Example: A Simple Web Dynpro Component Architecture


MasterComponent


ModelComponent

manage lifecycle

Web Dynpro Client

Visual Components

Layout Component

map contextmap context

Model Interface

15



Model Access Layer

UI Layer

1 DC

Example: A Simple Web Dynpro Component Architecture


MasterComponent


ModelComponent

manage lifecycle

Model Interface

Web Dynpro Client

Visual Components

Layout Component




ComponentBasics



Hands-On Excercise

ReferencingComponents

NetWeaver DevelopmentInfrasturcture Component


Hands-On Excercise

1

2

3

16



Development with or w/o NWDI

Errors due to missingautomatism

Errors caused by lack of checks during check-in of foreign components

Errors caused by differences between local and central environment

Errors caused by differences between local and central environment

Few test problems due to consistent development environment and CBS

activation concept. Defined release process for completed objects. Central test and release objects

Access to correct archives because of central archive management in the CBS.

Very few build problems due to centrally stored archives and

additional check of used objects during CBS activation.

Find correct sources

Copy & checkout source files

Find correct foreign libraries

Change development objects

Local build, local test

Check-in changed files

Central build

Build results can be tested in thelocal development environment. Onlydefined components can be used

Errors due to missingautomatismAccess to correct sources because of central source management in

the DTR and defined dev. environment in development configurations.


Local Installation (Developer‘s PC) Central Infrastructure (SAP NetWeaver)

Overview: Java Development Infrastructure

SAP NW Developer Studio

RunTimeJ2EE

Systems(RTS)

RunTimeJ2EE

Systems(RTS)

Deploy

Local File System

ComponentModel

Local J2EE

Engine

ComponentBuild Service

(CBS)

Name Service

System Landscape Directory (SLD)

Design Time Repository

(DTR)

Cha

nge

Man

agem

ent S

ervi

ce(C

MS)

17



DTR – Basics

Distributed, concurrent development

Distributed versioning that spans repositories

Conflict detection and resolution

Files and Folders

DTR knows only files and folders

No knowledge about objects of programming model (classes, tables, screens etc)

Check in/check out model

Files are checked out from DTR and modified “offline”

Files are checked in again when change is complete


CBS – Features

Storage of all archives of a software component

Immediate build of changes on request by developers

Automatic rebuild of dependent DCs

Provides access to latest build results for developers

Web UI (administration)

Parallel execution of build requests

18



CBS – Activation Concept

Inactive Workspace

Changes are done only here

Active Workspace

Has only successfully built sources

Always in sync with archives available from CBS

Activating Changes

Additional step after check in

Each code line (DEV, CONS) represented by two DTR workspaces


NWDI Based Development: Process

Local DC BuildLocal J2EETest System

Local File System

CBSDTR Server

Software Logistics(CMS, TCS)

Central J2EETest System

inact

act

2

4

3

5

Build

8

9 11b

11a

7

Build10

Test succeeds

Test succeeds

Loca

l Dev

. Env

ironm

ent

Cen

tral

Dev

. Env

ironm

ent

6

12 Release

SAP NetWeaverDeveloper Studio UISLD Dev.

Conf.

1

ActivateCheck in

Name Server

4b

19



SC B(imported, read only)

SC A(imported,read only)

SC X(changeable)

Structuring Applications Using the Component Model

1. Define a product

2. Define used SCs (in the development configuration)

3. Define new SCs

4. Define top-level DCs

5. Create DCs (default use dependencies to DCs of used SCs are set automatically)

6. Create development objects

7. Create public parts of DCs

8. Set use dependencies

Product X

DC

DC

DC

DC

DC

DC

DC

DC

consists of

uses

uses

DC

SAPNWDev.

Studio

CMS

SLD


DC 1 DC 3

DC 2

Allowing Reuse and Extensibility: Delivery

Package Web Dynpro Components into Development ComponentsA development component is

unit for packaging, building and transportation in SAP's infrastructure (NWDI)mapped to a project in the NetWeaver Developer Studio

Distribute objects over development components (reuse, size)component interface definitions and their implementationsmodels

Generally keep development components smallimproved build and deploy performancewatch out for increased overhead for maintaining references between them

<< Component >>Employee Self

Service„Personal Data“

<< Component >>AddressDisplay

<< Component >>Bank Account

Display

<< ComponentInterfaceDefinition >>Detail

Display

20



A Simple Web Dynpro Component Architecture

Model Access Layer

UI Layer


MasterComponent


ModelComponent

manage lifecycle

Model Interface

Web Dynpro Client

Visual Components

Layout Component


2

UI DC 1

Master DC




MasterComponent


ModelComponent

Public Part

Used DC Relation

use UI DC

Master DC

Model DC UI DC


Public Part

21



SLD Location

The URL for the system landscape directory has to be entered in the IDE preferencesEnable IDE to access defined configurations stored within the SLD


Logon to Development Infrastucture

Logon needed to work with Java development infrastructure

After every start of the IDEPreference setting to enable auto logon after IDE start

22



Import configuration

Start wizard from context menu or toolbarImport either

Locally stored configuration fileConfiguration from SLD (remote)


Browsing and Syncing Development Components

Use the development configurations perspectiveGlobal and local views

Inactive DCs view: global state of inactive DTR workspaceActive DCs view: global state of active DTR workspaceLocal DCs view: Local view on available DCs

Use context menu in the tree toSync DCsUnsync DCsCreate projects for existing DCs to import them into the IDE→ Do NOT use Eclipse project import for DCs !

23



Create a new DC

Create a new DC together with an Eclipse project with the help of the

Eclipse new object wizardContext menu in the inactive DCs view

First step: Assign new DC to an existing SC within an imported configurationSecond step: Name the DC


Check-out

Check-out can be explicitly triggered by chosing Edit from the DTR submenu of the context menu of the desired objectCheck-out for Web Dynpro objects will also be implicitly triggered by trying to modify an object

E.g. creating a view within a read-only component will first check-out the component

24



Performing DC Build

Start DC build from the context menu of one or more DC projects

Considers the correct build order when called for more than one DC

PerformsFull build of the DC Creates a deployable archiveCreates public parts defined by the DC

Build results are displayed the general user output view

Status message in viewDouble click on message to get detailsNo Eclipse task entries written!

DC build is necessaryWhen an object beloging to a public part has been changedPrior to checking in to assure correctness


Check-in and Activating

Check-in your changes to DTR by using the context menu entry in the open activities view in the development configuration perspectiveStatus and progress messages will appear in general user output view

After check-in an activation request can be triggeredSources and created archives will be moved from inactive to active workspace

25



Remove DC

Remove DC by simply deleting the DC project including its files

Use delete in context menu of Web Dynpro explorerUse remove from client in local or global DCs view

Remove DC by simply deleting the DC project including its filesUse delete in context menu of Web Dynpro explorerUse remove from client in local or global DCs view

Local DCs can be deleted completelyDCs stored in DTR can only be removed from the IDE



ComponentBasics



Hands-On Excercise

ReferencingComponents

NetWeaver DevelopmentInfrasturcture Component


Hands-On Excercise

1

2

3

26



Sharing Component Instance between Component Usages

A componentcomponent usageusage can be seen as a variable for a Web Dynpro componentcomponentinstanceinstance.

When using another Web Dynpro component a correspondingcomponentcomponent usageusage relationrelation must bedeclared.

Referencing Mode component usages can reference thesame component instanceinstance life cycle cannot becontrolled in referencing modelook on API IWDComponentUsageIWDComponentUsage

Master Component

Employee Component

ModelComponent

ModelComponent

Master Component

Employee Component

ModelComponent 1 Component

Instance

2 ComponentUsages

Design Time

Runtime


Model Access Layer

UI Layer


How can both UI componentsuse thethe samesame model componentinstance?

But both have their own, independantindependant component usages.

Solution

The lifecycle of the modelcomponent is managed by themaster component

The model component usages in both UI components must defineLifecycleLifecycle = = manualmanual..

The reference to the modelcomponent instance is injectedby the master component bycalling a component interfacemethod of the UI components.

The UI components can thenenter the model component in referencingreferencing modemode.


MasterComponent


ModelComponent

Model Interface

27



Model Access

Layer

UI Layer

Using a Component Instance in Referencing Mode

Entering a Referencing Mode 1. The master component creates an

instance of the model component.2. The UI component has defined a

component usage relation to themodel component. It does notmanage the lifecycle (= = manualmanual) of the used model component itself!

3. The master component passes a reference of the model componentusage to the UI component (via a public component interface method).

4. The UI component uses thisreference for entering the modelcomponent in referencing mode(IWDComponentUsageIWDComponentUsage-API).

5. The model component usage is nowrelated to the concrete runtimeinstance of the model component.

UI Component

MasterComponent

ModelComponent

1 ModelCompUsage

ModelCompUsage

4

reference5

2

Model Interface

3

setModel-CompInst()


setModelComponentInstance(IWDComponentUsage modelCompUsgmodelCompUsg)

{wdThis.wdGet<ModelCompUsageName>

.enterReferencingModeenterReferencingMode(modelCompUsgmodelCompUsg) }

Entering another Component in Referencing Mode

UI Component Interface Controller must expose method

UI Layer

UI Component

MasterComponent

ModelCompUsage

ModelCompUsage

setModelCompInstsetModelCompInst()()

28



Java Interfaces and the Strategy Design Pattern

Java Interfaces

In Java an interface is a type, just as a class is a type.

Like a class an interface defines methods but never implements them.

An interface is an abstraction of a class independent from its implementation.

<<interface>>IPayment

<<class>>Sale

CreditCardPayment

Cash Payment

<<class>>Sale

<<class>>CreditCard

Payment

<<class>>Sale

<<class>>Cash

Payment

Runtime

1

2

Design Time


Java Interfaces and the Strategy Design Pattern

The Strategy Design Pattern in Java

DefineDefine a a familyfamily of of algorithmsalgorithms, , encapsulateencapsulate eacheach oneone, and , and makemake themthem interchangeableinterchangeable. . StrategyStrategy letslets thethe algorithmalgorithm varyvaryindependentlyindependently fromfrom clientsclients thatthat useuse it.* it.*

It embodies two main OO design principles:encapsulate the concept that variesprogram to an interface, not an implementation.

GoodGood softwaresoftware = = looselyloosely coupledcoupled collectioncollection of of interchangeableinterchangeable partsparts

BadBad softwaresoftware = = monolithicmonolithic, , tightlytightly coupledcoupled systemsystem

Loose coupling makes your software much more extensible, maintainable, and reusable.

* Chapter 1 of the Gang of Four‘s (GOF) Design Patterns

29



Stratey Pattern and Component Interface Definitions

Component Interface Definitions

Allow decoupling Web Dynpro Components

Define a component interface without an implementationInterface can be implemented by one or more components

Benefits DecouplingComponent user can program against separately defined component interface (implementation is hidden)Component implementation can be provided (or selected) later on (plugin concept)

<< WD CompI >>DetailDisplay

MasterComponent

manage lifecycle

Bank AccountDisplay

Bank AccountDisplay

implement

AddressDisplay

AddressDisplay

ComponentComponentInterface DefinitionInterface Definition

(Suffix (Suffix CompICompI))


UI Layer

2

UI DC

1UI DC

Model Access Layer

Example: Adding a Component Interface Definition

MasterComponent

ModelComponent

Model Interface

Web Dynpro Client



<< WD CompI >>UICompI

setModelCompInst()

implementsimplements

3Model DC

30



Summary

Web Dynpro componentsWeb Dynpro components are the key to extensible, reusable and managable Web Dynpro software

A state-of-the-art Web Dynpro application architecture can be achieved by using specialized component typesspecialized component types

The NetWeaver Development NetWeaver Development InfrastuctureInfrastucture provides functions for developing professional, component-based Web Dynpro applications


Further Information

Public Web:www.sap.comSAP Developer Network: www.sdn.sap.com Web Application Server Web Dynpro ( Code Samples Sample Applications and Tutorials)SAP Customer Services Network: www.sap.com/services/

Related Workshops/Lectures at SAP TechEd 2005CD210, Transaction Handling in Web Dynpro, 1-Hour LectureCD213, Web Dynpro Meets JSF – A New Level of Interoperability , 1-H L.CD258 Putting It All Together –

Application Development in SAP NetWeaver, 4-H Workshop CD255 Component-Based Java Development with SAP NetWeaver, 4-H W.CD207 SAP NetWeaver Development Infrastructure – An Overview, 1-H L.

Related SAP Education Training Opportunitieshttp://www.sap.com/education/

31



No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Copyright 2005 SAP AG. All Rights Reserved

web dynpro componentization

Documents

party web pages

web dynpro explorer

based application architecture

bank account display

netweaver development infrasturcture

application design concept

web dynpro components

web dynpro component