Architecture of web dynpro

hi everyone
can any one breif me about the architecture of Dynpro
thanks and regards
sandeep

Hi Sandeep Pendyala ,
The following r excellent websites on architecture of Dynpro which contain PDF & PPT documents :
Web Dynpro Architecture
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1a1e3e7181b60ae10000000a114084/content.htm
Web Dynpro User Interface Design
https://www.sdn.sap.com/irj/sdn/webdynpro?rid=/webcontent/uuid/ce44a14c-0a01-0010-af89-d7dbd944f176 [original link is broken]
The Structural Concepts of Web Dynpro Components
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a048387a-0901-0010-13ac-87f9eb649381
Web Dynpro Java Foundation What's new in SAP NetWeaver 2004S
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c29a4d25-0c01-0010-50ae-e69d0e1c61f3
SAP Web Dynpro Overview
http://wendtstud1.hpi.uni-potsdam.de/sysmod-seminar/SS2005/presentations/12-WebDynpro-Overview.ppt
Web Dynpro General Concepts
https://admin.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/30ea953b-8e57-2910-4e85-f7be60b00407 [original link is broken]
cheers!
gyanaraj
xxxxxxx (please read forum rules)
Edited by: Armin Reichert on Jan 17, 2008 10:13 AM

Similar Messages

In web dynpro i want explanation/definition for the following things

Hi dudes,
I want explanation *** definition for the following
(1) web dynpro
(2) Cardinality
(3) methods
(4) Nodes
(5) Attributes
(6) Interface
(7) Views
(8) Windows
(9) Mapping
(10)Binding
(11)Model
(12)Controller

Hi,
Here are the defintions for the terms you hav requested-
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
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.
A Web Dynpro component is a reusable entity. It summarizes all components that are
required as part of this programming unit for an executable Web Dynpro application.
The Web Dynpro component concept offers a number of advantages:
Structuring of the programming
Creation of easily manageable application blocks
Reusability of whole components
Decoupling of software projects in both time and space
The Web Dynpro component contains any number of windows and views and their
corresponding controllers. Additional Web Dynpro components can also be referenced.
View
A view describes the layout and behavior of a rectangular area of a user interface.
Every Web Dynpro application has at least one view. The layout of a view is made up of
different user interface elements, which can be nested in each other. The positioning of
interface elements in one view is supported by the supplied layout variants.
In addition to the visible part, the layout, a view also contains a controller and a context. The
data to which the elements of the view can be bound are stored and managed in the view
context, enabling them to be represented or used on the screen. The view controller can
contain methods for data retrieval or for processing user input.
Window
A window is used to combine several Views and View Sets (the concept of view sets is only
offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
embedded in a window. A window always contains one or more views, which are connected
by navigation links. One of these views, or a view set, is specified as the start view and is
displayed the first time the window is called.
Windows have inbound and outbound plugs.
Inbound Plugs and Outbound Plugs
A window has one or several inbound or outbound plugs. Using these plugs, a window can be
included into a navigation chain. The concept of these plugs corresponds to the concept of
the plug for a view. Each plug of a window is visible within the entire window and can be used
for navigating within this window. In addition, one or several plugs can be made accessible to
the component interface so that they are visible even beyond the limits of the component in
question. They thus belong to the interface view of the relevant window.
They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
Controller
Controllers are the active parts of a Web Dynpro application. They define how the user can
interact with the Web Dynpro application. The data that a controller can access is defined in
the corresponding context. Different instances of controllers and contexts exist within a Web
Dynpro application.
View Controller
Each view has exactly one view controller, which processes the actions performed by the user in the view.
A view also has exactly one view context, which contains the data required for the view.
Interface Controller
Each Web Dynpro component contains exactly one component controller. This controller is a
global controller that is visible also outside the component. It is thus part of the interface of a
Web Dynpro component.
Context
Definition
The data used in the component or in the view are stored in the context. Read-write access to
this data is available using the controllers as a starting point.
Structure
The data from the contexts is managed in a hierarchical structure. Each context has a root
node, underneath which the individual data fields (attributes) are stored in a tree structure.
You create this tree structure according to the structure of your application.
CONTEXT is generally called as a ROOT Node.
Each context has nodes and attributes also.
Cardinatlity
Each node contains data fields that represent one of the following:
u2022
An individual instance of an object type
u2022
A table of instances.
This property of a node is known as its cardinality. The following table summarizes the
possible cardinalities for a node:
Cardinality Description
1:1 The node contains only one element instance, which is instantiated automatically.
0:1 The node contains only one element instance, which must not be instantiated.
1:n The node can contain multiple element instances, of which at least one must always be
instantiated (and is instantiated automatically).
0:n The node can contain multiple element instances, of which none have to be instantiated.
Further information about this and other properties of context nodes is available in the section
Context-Nodes: Properties.
Recursion Nodes
Dynamic node nesting is possible within a context, creating what is called a recursion node.
The node that is used for recursion is always a predecessor of the new node. The newly
created recursion node is a reference to a predecessor node and therefore cannot be
processed separately. Instead it takes on the structure of the node to be repeated.
Data Binding and Mapping
Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
different ways:
u2022
A UI element of the user interface of the view can be linked with an element of the view
context.
u2022
A mapping can be defined between two global controller contexts, or from a view
context to a global controller context.
The context of a global controller can be linked to a Web Dynpro Model.
Defining Mapping Between Two Contexts
The elements of a view context can be locally defined. In this case (represented in the graphic
below as a "Local Node"), all the contained attributes are only visible within the relevant view.
When the view disappears, the attribute values are deleted.
Event
The component controller allows you to create events.
Events are used to communicate between controllers and enable one controller to trigger
event handlers in a different controller.
Cross-component communication can be implemented using the interface controlleru2019s events.
Events that were created in the component controller are visible within the component only.
Inbound Plugs
Inbound plugs in a view also react like an event. Therefore, when a view is called using an
inbound plug, the event handler that is optionally available for the inbound plug is always
called first. In this case event handling takes place within the current view controller.
UI Element Events
Some UI elements, such as the Button element have special events that are linked with user
actions. These events are predefined and have to be linked with an action at design time.
Actions for UI Element Events
Some UI elements such as the button element can react to a useru2019s interaction: clicking on
the corresponding pushbutton can trigger a handling method to be called within the view
controller. Such UI elements are equipped with one or several general events, which can be
linked with a specific action at design time (switching to a subsequent view, for example). If
such an action is created, an event handler method for this action is created automatically. In
this way, you can equip a UI element event (which has been inserted several times into a
view) with different actions as necessary. The event is then processed by the corresponding
event handler depending on the action that is linked.
Interfaces of Web Dynpro Components
Each component has an interface in order to enable communication between Web Dynpro
components and to enable a component to be called up by a user. This interface consists of
two parts:
Interface View of a Window Contained in a Component
The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
application that can be called by the user.
Reward if helpful.
Best Wishes,
Chandralekha

Webinar: Introduction to Web Dynpro Business Graphics

SAP NetWeaver Know-How Network Webinar:
Introduction to Web Dynpro Business Graphics
Wednesday 15 September 2004
11 a.m. EDT
On Wednesday 15 September, Jeff Gebo hosts the webinar titled Introduction to Web Dynpro Business Graphics as part of the ongoing SAP NetWeaver Know-How Network Webinar Series.
Heres how Jeff describes his webinar presentation:
Learn how to bring your Web Dynpro Applications to life with business graphics. Business graphics can be generated by Internet Graphics Services (IGS) which is included in the 6.40 SAP Web AS. Get an overview of the IGS architecture, the Web Dynpro Business Graphics API, and the features of the IGS. Join this webinar and then go and impress your boss with the incredible business graphics that you will be able to create!"
SDN invites you to post your questions to the presenter prior to the webinar and continue the online discussion afterward.
How to Participate
(Please go to the SDN Events page to see the article and download the PDF presentation)
Dial-in Information:
Date: Wednesday 15 September 2004
Time: 11 a.m. EDT
Within the U.S., call: +1.888.428.4473
Outside the U.S., call: +1.651.291.0618
Password: NetWeaver04
WebEx Information:
Topic: SAP NetWeaver Know-How Network
Date: Wednesday 15 September 2004
Time: 11 a.m. EDT
Meeting Number: 742391500
Meeting Password: netweaver04 (lowercase)
WebEx Link: sap.webex.com
Replay Information:
A recorded replay of this call will be available for approximately three months after the webinar. Access this recording by dialing the appropriate number and using the replay access code 720158.
Toll-free: +1.800.475.6701
International: +1.320.365.3844
About the SAP NetWeaver Know-How Webinar Series
The SAP NetWeaver Know-How Webinar Series is driven by the SAP NetWeaver Regional Implementation Group (RIG), part of the SAP Development organization. The mission of the SAP NetWeaver RIG is to enable customers, employees, and partners to successfully implement the SAP NetWeaver solution. This SAP RIG has expertise in BI, EP, XI, and WebAS. They contribute their implementation expertise to the SDN implementation forums as well as to the SAP NetWeaver Know-How Webinar Series.
Disclaimer
SDN is not responsible for any changes to the webinar schedule. The webinar schedule may be changed or cancelled without prior notice.

Hi,
Go thru..
What is Webdynpro?
What is Web Dynpro?
Webdynpro Sample Applications and Tutorials
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d
SAP WebAs Samples And tutorials
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/7d646a6c-0501-0010-b480-bf47b8673143 [original link is broken]
Basis Webdynpro tutorials....
http://help.sap.com/saphelp_erp2005/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e9/1fc0bdb1cdd34f9a11d5321eba5ebc/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/d08342a7d30d53e10000000a155106/frameset.htm
Web Dynpro Sample Applications and Tutorials:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d [original link is broken]
http://searchsap.techtarget.com/searchSAP/downloads/SAPPRESS.pdf
Check the following thread u can get lot of materials,
WeB Dynpro Documents
Refer these linkshttps://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/web%20dynpro%20tutorial%20and%20sample%20applications.faq
Why WebDynpro ?
Why WebDynpro ?
Why webdynpro and not BSP or JSP?
Why webdynpro and not BSP or JSP?BSP to WEB Dynpro
BSP to WEB Dynpro
Benifits of using Webdynpro Benifits of using
Webdynpro
Java vs. ABAP WEbDynpro Java vs.
WebDynpro ABAP
regarding Java related webdynpro
Regarding Java related Web Dynpro vs. Struts - a few questions
Web Dynpro vs. Struts - a few What kind of applications are being developed with Web Dynpro?
What kind of applications are being developed with Web Dynpro?
http://www.sappro.com/downloads/OptionComparison.pdf
Hop this will helpful for u..
Urs GS

Want docs for Web Dynpro ABAP

Hi All ,
Can anyone please send me the Docs or link for Web Dynpro ABAP .
Thanks in advance
Rahul

Hi,
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Also, I have the official Web Dynpro for ABAP documentation. Please let me know if I should send it to you.
Hope that the following also helps you.
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
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Reward points if useful
Regards
Anji

Web Dynpro concept

Hi all,
What is web dynpro concept in ABAP. What are the future scope for the same.
Regards,
John

Hi,
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Hope that the following also helps you.
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 u2013 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.
Web Dynpro ABAP Demonstration Videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Cheers,
vasavi.v

Error in opening sap web dynpro iview

hi all,
i am trying to open sap webdynpro iview in portal but getting the following error...
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
 java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs Found in negative cache -
Loader Info -
ClassLoader name: [local/SLAReporting_KM] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/com.sap.km.application sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:tccolapi library:com.sap.aii.util.misc library:tccmi library:tccol~runtime Resources: D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
 ... 49 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0007.20060509173555.0000 (release=NW04S_07_REL, buildtime=2006-05-09:16:21:23[UTC], changelist=13857, host=pwdfm114), build date: Thu May 18 17:33:32 GMT+05:30 2006
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Wed Jul 12 09:17:18 GMT+05:30 2006 (Java Time: 1152676038656)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.lti.CSLs. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:300)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:359)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1278)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
 at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:300)
 at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
 at sun.reflect.GeneratedMethodAccessor3364.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:659)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:532)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs
Found in negative cache
Loader Info -
ClassLoader name: [local/SLAReporting_KM]
Parent loader name: [Frame ClassLoader]
References:
 common:service:http;service:servlet_jsp
 service:ejb
 common:service:iiop;service:naming;service:p4;service:ts
 service:jmsconnector
 library:jsse
 library:servlet
 common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
 library:ejb20
 library:j2eeca
 library:jms
 library:opensql
 common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
 interface:resourcecontext_api
 interface:webservices
 interface:cross
 interface:ejbserialization
 sap.com/com.sap.km.application
 sap.com/tcwddispwda
 sap.com/tcwdcorecomp
 service:webdynpro
 service:sld
 library:tcddicddicservices
 library:com.sap.aii.proxy.framework
 library:tcgraphicsigs
 library:com.sap.mw.jco
 library:com.sap.lcr.api.cimclient
 library:sapxmltoolkit
 library:com.sap.aii.util.rb
 library:com.sap.util.monitor.jarm
 library:tcddicddicruntime
 library:com.sap.aii.util.xml
 library:tccolapi
 library:com.sap.aii.util.misc
 library:tc~cmi
 library:tccolruntime
Resources:
 D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar
Loading model: {parent,references,local}
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
 ... 52 more

Hi there,
Try re-deploy the application and restart the server. It will fix this problemn.
Regards,
Luciano

Moving Local Web Dynpro project from Dev to Prod

Hi,
i have a scenario where there is a small application to be developed. And m the only developer to work on it.
I need to a create local web dynpro project for the same and deploy it to the deveopment server. and test it here. However, the client for whom i am developing this service, is based somewhere else. How do i deploy this local application on his production server?
I dont have JDI architecture here. Can i achieve this without JDI? and How? Which is more feasible - using JDI or not in my case ?
Regards,
Apeksha

Hi,
Genrally, it is recommended to work with JDI. But, as you said you have only project that needs to be deployed then you can change the server settings in your NWDS and make it point to the production server.
Windows>Preferences>SAP J2EE Engine--> <details of your remote production server>
NOTE: You should have sdm password to deploy this applicaiton.
Regards,
Murtuza

After applying SP21 the web dynpro is not working (WDTypeNotFoundException)

Hi
We have recently applied SP21 to our NW04 system.
The patch was successfully applied. But while accessing the Web Dynpro, we are getting WDTypeNotFoundException exception.
The Error Message is as follows :
+500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Hide
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Hide
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type jp.co.companyname.projectname.pp.fnp09.datapreparemodel.types.Ru_cnfind not found
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:224)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:517)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:530)
at jp.co.companyname.projectname.pp.fnp09.main.RawMaterialView.wdDoModifyView(RawMaterialView.java:191)
... 28 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4021.00.0000.20070905102710.0000 (release=630_VAL_REL, buildtime=2007-09-19:20:40:15UTC, changelist=460812, host=PWDFM026)
J2EE Engine 6.40 patchlevel 109749.313
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Other
Session Locale ja
Time of Failure Mon May 17 18:35:52 JST 2007 (Java Time: 1197884152810)
Web Dynpro Code Generation Infos
companyname.co.jp/pp~fnp09
SapDictionaryGenerationCore 6.4010.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-12-09:22:23:41UTC, changelist=280522, host=PWDFM026.wdf.sap.corp) +
If you have any ideas please let me know.
thanks and Regards
Raghunahth L

Hi raghu,
You can go to Visual administrator (/usr/sap/<SID>/JCxx/j2ee/admin--go.bat)
Give administrator credentials..
Cluster-Server-Services-webdynpro Runtime.
See if it is stopped.You can see red croos,if it is stopped.If it is,
Right click on Webdynpro Runtine and start.
One more option,you can give a try is start all teh srvices manually through
telnet
This can be done with "run' command on you system
telnet <IP adress> telnet port
telnet port will be http port ending with 8.
then give administrtaor credentials.
then go with these commands,
jump 0
add deploy
list_app
start_app-all
Try looki in for detailed error messages in default trace and application logs.
Loc : /usr/sap/<SID>/JCxx/j2ee/cluster/server0/log
Regards
Usha

Error message when I run the Web Dynpro Project

Dear friend,
I had deploy & run project, but it's got the error message under the line:
I had install NWDS V. 2.0.11 on my PC, but the project which I deployed was the version that I created by NWDS V. 2.0.9, and I had install new OS as XP Home instead the old one (Windows2000), are these the cause of problem?
Please advise how can I do.
Best regards,
SeMs
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Media Center PC 3.0; .NET CLR 1.0.3705), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC local/ZWelCome:
SapDictionaryGenerationCore: 6.4011.00.0000.20050127161623.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:34:47[UTC], changelist=324383, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4011.00.0000.20050121170001.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:38:14[UTC], changelist=322883, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4011.00.0000.20050121165648.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:28:49[UTC], changelist=322878, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:53:22[UTC], changelist=329752, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:53:22[UTC], changelist=329752, host=PWDFM026)
SapGenerationFrameworkCore: 6.4011.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:28:00[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4011.00.0000.20050215134310.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:42:02[UTC], changelist=329103, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4011.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:32:12[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4011.00.0000.20050121165648.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:28:59[UTC], changelist=322878, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4011.00.0000.20050215134310.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:42:32[UTC], changelist=329103, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_08-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Message was edited by: Sukasem S.wattanakoon
Message was edited by: Sukasem S.wattanakoon

Probably the usual problem of deploying an application built with a newer NWDS (SP11) on an older server (SP9).
But without the stacktrace this is only a guess.
Armin

Trying to run a Web Dynpro Simple Sample with no luck??

Hi I have downloaded a Web Dynpro and BPM simple sample application from this location: The problem is after configuring the CE instance and setting everything up, when i Deploy and Run this app i get the following error displayed can some one please help?? 500 Internal Server Error SAP NetWeaver Application Server/Java AS The initial exception that caused the request to fail, was: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) ... 115 more See full exception chain for details. Failed to process request. Please contact your system administrator. While processing the current request, an exception occured which could not be handled by the application or the framework. If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file). For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811. Correction Hints Exception could be caused by the development component: tcwdwebdynpro Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases. System Environment Client Web Dynpro Client Type AJAX Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; LLY-EMA-EN; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; LLY-EMA-EN; LLY-EMA-EN) Client Type msie7 Client Type Profile ie6 ActiveX enabled Java Applets enabled Accessibility mode disabled Inline CSS false Validate by rendering true Server Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.2001.20091210105536.0000', change number: '79724', codeline: NW720_01_REL J2EE Engine 7.20.3710.69682.20090922144234 System ID (SID) CE1 Server Node ID |3191650|31916|Server 00 00_31916|YHP30964.ema.lilly.com/40.205.138.181|SERVER|RUNNING Java VM SAP Java Server VM, version:6.1.007, vendor: SAP AG Operating system Windows XP, version: 5.1, architecture: x86 Application Java EE Application (deployable object) ides.com/soacmpssc~salsord Web Dynpro Application CreateSalesOrderApp Request URI /webdynpro/resources/ides.com/soacmpssc~salsord/CreateSalesOrderApp Version vendor: 'ides.com', name: 'soa/cmp/ssc/salsord', location: 'localDevelopment', counter: '20100329143545', change number: 'null' Session & Other Session Locale en_GB Session Timezone Greenwich Mean Time Time of Failure Mon Mar 29 15:38:53 BST 2010 (Java Time: 1269873533200) Session User ClientUser(id=USER.PRIVATE_DATASOURCE.un:Administrator, name=Administrator) Http Session Id tCJhFjXUItrW3M0cACKdKt9MDaBiM0upJwFiszAA_SAP Client Window Id Application Session Id b2a8d9023b4011dfb81f001b7889332c Web Dynpro Code Generation Infos ides.com/soacmpssc~salsord WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:22+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:22+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) sap.com/tcwdapi WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:32+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:55+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) Detailed Error Information Detailed Exception Chain com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session b2a8d9023b4011dfb81f001b7889332c. The causing exception is nested. RID=b2a8d9003b4011dfbdb7001b7889332c at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:606) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:335) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87) at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:98) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:79) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:566) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1438) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:603) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:71) ... 48 more Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'ERP_META' and WS interface 'SalesOrderBasicDataByBuyerAndBasicDataQueryResponse_In'. One possible reason is that the metadata destination 'ERP_META' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:558) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:457) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:425) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:399) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:334) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:307) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:93) at com.ides.soa.cmp.ssc.salsord.findsomodel.FindSOModel.<init>(FindSOModel.java:114) at com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd.<init>(CreateSalesOrd.java:732) at com.ides.soa.cmp.ssc.salsord.createsalesord.wdp.InternalCreateSalesOrd.<init>(InternalCreateSalesOrd.java:8892) ... 53 more

Hi Anixan
Please update the SAP AS Java at windows >> Preference >> SAP AS Java >> Add new SAP >> Put instance Hostname like 'CE1' and Instance Number like '00'. Then please verify that is connected or not in NWDS at windows >> show view >> Others >> Server >> Servers
**Also update the Update your server IP address and host name in host file entry at (Start > RUN > drivers > etc > host file)
and update JAVA_HOME system enviromental variable in my computer (My computer > Priperties >> Advance >> Startup and Recovery >> Enviromental Variable >> System Variables >> Add new JAVA_HOME parameter with path for installed Java JDK)
Please check here http://help.sap.com/saphelp_nw70/helpdata/EN/43/3976df43b33575e10000000a11466f/content.htm
Hope it helps
Regards
Arun

Error is in example "How to Create Online and Offline Forms in Web Dynpro"

Hi,
I am developing " How to Create Online and Offline Forms in Web Dynpro " in nwds 7.0. This is standard example which is available at sdn. but when i run it gives me error like "
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.travelrequestapp.TravelRequestComView.wdDoInit(TravelRequestComView.java:97)
    at com.travelrequestapp.wdp.InternalTravelRequestComView.wdDoInit(InternalTravelRequestComView.java:133)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
    ... 34 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Thu Feb 15 10:23:57 IST 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Mon Oct 29 12:13:24 IST 2007 (Java Time: 1193640204484)
Web Dynpro Code Generation Infos
local/TravelRequest
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:59:42[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates (unknown)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:48:59[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:10[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:57:39[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:02:09[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:33[UTC], changelist=384368, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:21[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:33[UTC], changelist=384368, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.travelrequestapp.TravelRequestComView.wdDoInit(TravelRequestComView.java:97)
     at com.travelrequestapp.wdp.InternalTravelRequestComView.wdDoInit(InternalTravelRequestComView.java:133)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:793)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
So please help me to correct this error .....
Help will be rewarded.
Regards,
Gurprit Bhatia

Hi Gurprit,
A null value is being passed at runtime. Make sure that you enter values when filling in the form.
Also check for the cardinality of the nodes being used. You can also initiliaze your value attributes as follows:
In wdDoInit() method:
wdContext.currentNodeAElement.setValueA("");
Context is as follows:
RootNode
|____NodeA
        |_____ValueA
Hope it helps.

Deploying my first web dynpro java application through NWDS 7.3 giving error

hi all,
i am new to webdynpro java. i am basically a xi consultant, but due to some work need to work on webdynpro java as well.
i went through the blog Web Dynpro Tutorial: Hello World
i am using NWDS 7.3
i created web dynpro project as per above blog. on the last step, it says to deploy it on SAP system.
now i have access to PI7.1 system only, though in our landscape, we have ECC system, EP system, BI system etc.
i guess the above webpage is referring to getting it deployed on EP system - but i have access to only PI7.1 system - in NWDS 7.3 in window - preferences - SAP AS Java - i have added PI7.1 system and it is showing there.
now on right-clicking web dynpro application, and selecting deploy new archive and run - it is not deploying and the web-page gives error 404 - not found. The requested resource does not exist.
can the web dynpro application be deployed on PI7.1 system?
pls suggest how to resolve this error. thanks.

i have downloaded NWDS7.1 through this link
https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/ce/
used the first option - Download latest NWDS_platform.zip release
the zip file got downloaded.
on trying to install through IDEsetup.exe - now i am getting error in installation - The installer cannot run in the 32-bit sub-system on a 64-bit architecture.
how to solve this error - i tried installing jdk-6u7-windows-x64.exe and jdk-6u18-windows-x64.exe - but still the error remains same.
So how to install NWDS7.1 on my system? please tell. thanks.

Using EJBs in Web Dynpro

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Thanks for your reply and your suggestion. I have posted in the Web Dynpro Java forum... and suggest those wishing to participate in this thread to refer to the Web Dynpro Java forum.
As for your answer, I'm afraid it doesn't satisfy me.
Reuse is hardly an issue, since the CommandBean is specifically tailor-made for the Web Dynpro application that needs to use it. I could hardly imagine building another application that would just happen to have the exact same needs as far as data structure and processing is concerned...
As for the right Eclipse environment... the CommandBean is not an EJB artifact - it is an EJB client. The aforementioned tutorial in fact suggests creating it in the Java perspective.
But thanks anyway for your time and suggestion

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Calling a Method in Web Dynpro ABAP

Hi Experts,
I have created a class in se24 and called its methods in web dynpro by simply creating its object. It is working fine. After that i came to know that method should be called through creating a service call in WD.
What is the standard way and why?
Thanks
Ravindra.

Hello Ravindra ,
I think the better way is to create an assistance class ( Say A1) and create an attribute (Say AC1) as object of your class ( Say C1 ).
In the costructor of you assistance class A1 you can instanciate the object of C1 .
Now inside a method of assistance class you can call the method of C1 any time because AC1 is already instantiated .
MVC architecture recommends you should have separate method to aceess the data and you write your business logic in assitance class methods .
Hope this will help you .
Regards
Vivek

Architecture of web dynpro

Similar Messages

Maybe you are looking for