IN Compsition Environment: interface controller in web dynpro

Hi All,
I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
Any clues on this?
Regards
Satish.

Hi All,
I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
Any clues on this?
Regards
Satish.

Similar Messages

  • Compsition Environment: interface controller in web dynpro

    Hi All,
    (I know this is not right place to raise this question but if anyone know)
    I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
    Any clues on this?
    Regards
    Satish.

    Since one dedicated link is there between
    Comopnent  and Interface controller.

  • Local interface of each controller in web dynpro abap

    Hi everyone,
    Anybody please give some idea what is local interface of each controller in web dynpro abap??
    Thanks,
    Sonali..

    Hi,
    There will be three controllers in webdynpro
    1) Component controller which provides data and processing logic that it should be possible to display or change for all views of a component. It is the main component. All the data of the iview can be shared using this controller. Custom controller is also component controll. The only differnce is it is custom made.
    2) Inteface Contorller which is used as in interface for communication other components.
    3) View Controller which will be having data and functions and visible in the same iview and is associated with the iview. its lifetime is also limited and only during it is shown.
    Please go through the link also
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b9/b82c4142aef623e10000000a155106/frameset.htm
    Also please go through the below pdf link.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2eb11b59-0a01-0010-dfa3-8292abdf9c4f
    hope it helps you.
    Raghu
    Raghu

  • Interfaces concept in web dynpro

    Hi all
    Can anyone tell me a way of approaching the interfaces concept in web dynpro?
    Thanks n regards
    chaitanya

    Hi,
    Check this links and work on it.
    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#13 [original link is broken]
    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#12 [original link is broken]
    http://help.sap.com/saphelp_nw70/helpdata/en/20/a5f7416e61212be10000000a155106/frameset.htm

  • Component Interface , INterface controller in WEB UI

    Hi Experts,
    Can anyone tell me what is a component interface, component usage , Interface controller and interface view?
    I am a beginner in WEB UI and is getting confused with these terms.
    Please help.
    Many Thanks,
    Neeraj

    Hi,
    component interface -> interface view:
    Here you can define which Comp/Window should be accessable from outside the component
    For example: COMP_1/MainWindow in component interface means this can be accessed as usage from other component
    component interface -> interface controller:
    In this node there is 2 child nodes: Context and Events:
    I don't know how to use Events. But in Context you can add context node from component controller, which can be accessed from outside. This is specially important, when you want to bind two context nodes from two different components.
    You can see how this can be used in component controller class in the method WD_USAGE_INITIALIZE
    component usage:
    Here you can define a usage of of other component.
    For example: In your COMP_2 you can create a usage from other component (COMP_1/MainWindow).
    Regards,
    Steve

  • Environment for working with web dynpro

    Hi All,
    I am new to web Dynpro and would like to work on this. Please let me know what software i need to install to work on web dynpro. PLease provide all the necessary information.
    Thanks,
    Ramana Kishore.

    Hi.  THere are two flavors of webdynpo, you have the java side, and the ABAP side?  Which do you want to work with? 
    For the java side, you will need to download and install a Netweaver Sneak Preview Java system as well as the Netweaver Developer Studio.  The studio is the IDE which you will use to create your webdynpro applications, you then deploy to this java system to run the app.
    For the ABAP side, you will need to download and install the Netweaver Sneak Preview ABAP system.  Of course the IDE here is SE80 in the ABAP system.  Webdynpro is built directly into SE80.
    You can download all of this good stuff here on SDN at the following link.
    https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/cfc19866-0401-0010-35b2-dc8158247fb6
    The ABAP system is on the far right.
    You can also check out the help on both.
    http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/frameset.htm
    Hope this helps.
    REgards
    Rich Heilman

  • 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

  • Use of interface controller

    HI
    can u please explain me use of interface controller with simple example along with the code
    Thanks
    kishore

    Hi Kishore,
    Here r the few facts abt interface controller:-
    Used to control access from other components.
    Is created automatically when a component is created.
    Exists as long as its component is embedded in another
    component.
    This controller contains data, methods, and events that can be used by other Web Dynpro components.
    A componentu2019s interface controller can be used by the embedding component for mappings, eventing, etc.
    Interface for external users of a component: data transfer,
    eventing.
    Interface Controller
    One Web Dynpro Component may declare the use of another Web Dynpro Component to form a u201CParent-Childu201D usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the childu2019s interface controller.
    There is a usage declaration arrow pointing from the component controller to a child component. Notice that the arrow joins the child component at the top right-hand corner. This is the location of the childu2019s interface controller.
    At no time does the Web Dynpro Runtime interact with a componentu2019s interface controller. It is only ever used to form a Parent-Child relationship between two Web Dynpro Components.
    Check the links:-
    http://help.sap.com/saphelp_nw70/helpdata/EN/47/45641b80f81962e10000000a114a6b/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/44/0dcafa2d9d1ca2e10000000a11466f/frameset.htm
    hope dat may help u..
    Regards,
    Deepak

  • Regarding Component interface controller

    hi all
    Can anyone explain me use of Component Interface Controller under Component with example.
    Thanks in advance
    Imityaz

    Hi,
    Interface Controller
    One Web Dynpro Component may declare the use of another Web Dynpro Component to form a u201CParent-Childu201D usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the childu2019s interface controller.
    if an interface controller is part of a component interface, the controller editor is in change mode and the context, the events and the methods can be implemented and edited directly.
    Refer this thread,step by step procedure is there.
    /docs/DOC-8061#61 [original link is broken]
    http://help.sap.com/saphelp_nw70/helpdata/EN/47/45641b80f81962e10000000a114a6b/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/44/0dcafa2d9d1ca2e10000000a11466f/frameset.htm
    Regards,
    Sunaina Reddy T

  • Purpose of Interface controller

    Hi,
    What is the purpose of Interface controller in webdynpro?

    hi
    Interface Controllers
    Interface Controller
    One Web Dynpro Component may declare the use of another Web Dynpro Component to form a “Parent-Child” usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the child’s interface controller.
    There is a usage declaration arrow pointing from the component controller to a child component. Notice that the arrow joins the child component at the top right-hand corner. This is the location of the child’s interface controller.
    At no time does the Web Dynpro Runtime interact with a component’s interface controller. It is only ever used to form a Parent-Child relationship between two Web Dynpro Components.
    SAP strongly recommends that no application coding be written directly into the methods of the interface controller. Instead, the public methods of the interface controller should simply delegate their functionality to a method of the same name in the component controller. This will greatly reduce the conversion task required when upgrading to the next release
    Interface View Controller
    The visual interface of a Web Dynpro component is supplied via the Interface View. This behaves much like a UI element in so much that it can be embedded into the view layout of a parent view as a single, reusable entity.
    Once the interface view of the child component has been embedded into a view layout belonging to the parent component, the parent component then has programmatic access to the visual interface of the child component through the child’s interface view controller.
    you can also see more details in this link
    http://help.sap.com/saphelp_nw04/helpdata/en/9c/a5863f455f3417e10000000a114084/frameset.htm
    Regards
    Chandran S

  • Context from Web-Dynpro-Component-Interface & Customer Extention Fields

    Hello all,
    A main component uses a Web-Dynpro-Component-Interface and defines an external maping to it. Web-Dynpro-Component-Interface has a context and a window. At runtime implementaion of Web-Dynpro-Component-Interface is provided.
    All works fine, but how can i create an implementation with view which contains customer extention fields? Unfortunately only fields from context of Web-Dynpro-Component-Interface are visible. I can not even extend the context of Web-Dynpro-Component-Interface via enchancement framework.
    I assume, it is possible with dynamic programming, but why is it not possible in declarative way?
    thanks
    regards
    Paul

    Hello,
    I found this documentation:
    Implementation of Interfaces for Customer Developments
    Using interfaces in a Web Dynpro component benefits customers by giving them a clean basis for their own further developments. When creating a local development, you can implement a used interface in a separate component and add your own aspects to an application delivered by SAP.
    http://help.sap.com/saphelp_nw70/helpdata/en/a9/19eebc1e2943dbb2d443095d017ae9/content.htm.
    I think it must be a correct way to extend SAP programms with customer fields. Please reply, issue is very important.
    Regards
    Paul

  • 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

  • How to create a method in Interface Controller

    Hi Guys,
            I am working with webdynpro ABAP sample application "Component usage" . There i got a issue like i am not able to create a method in Interface controller. There i am not able to edit anything. Can anybody please let me know how to do that.
                Thanks In Advance
    Regards
    Ravikumar

    Hi Ravi,
              Check This
    If one Web Dynpro component (parent component) needs access to another Web
    Dynpro component (child component) the parent component can declare the use
    of the child component. A specific component usage instance is then created and
    the parent component accesses the functionality of the child component via its
    component interface controller.
    The only parts of a Web Dynpro component that are visible to the user, are the
    interface controller and the interface view(s).
    All Web Dynpro components have only one interface controller. Via the
    interface controller, data, methods, and event handlers can be exposed to
    other components.
    Interface views represent the visual interface of a Web Dynpro component.
    There is a one-to-one relationship between a Window and an interface view.
    Each time a window is defined, a related interface view is automatically
    generated, which makes the window accessible from outside the component.
    The interface view only exposes those inbound and outbound plugs to the
    component user that have the interface property checked. Methods and
    context data of the window are not accessible via the related interface view.
    If the component has no views, there is no need to have Windows. In this
    case, the component will not implement an interface view. Such components
    having no visual interface are known as faceless components.
    Regards
    Sarath

  • RE:Web dynpro in ABAP

    Hi all,
    What is the use of component controller,custom controller and interface controller.In wht senarios we use them.Also please explain about its visibility with other components..
    Regards,
    Alex.

    hi
    What is the use of component controller,custom controller and interface controller.In wht senarios we use them
    Component controller
    There is only one component controller per Web Dynpro component. This is a global controller, visible to all other controllers. The component controller drives the functionality of the entire component. This controller has no visual interface. The lifetime of the component controller equals the lifetime of the component. When starting a Web Dynpro application, the component controller is instantiated by the Web Dynpro runtime
    Custom controllers
    Custom controllers are optional. They have to be defined at design time and can be used to encapsulate sub-functions of the component controller. Multiple custom controllers can be defined in a component. Custom controllers are instantiated automatically by the Web Dynpro framework and the instantiation order is undefined; therefore, the coding in a custom controller should make no assumptions about the existence of any other custom controller. The instantiation of a custom controller is delayed until the first method of the controller is called. Custom controller instances cannot be deleted explicitly.
    Interface Controller
    The interface controller is used for cross-component communication. It defines the controller part of the interface of a Web Dynpro component. The interface controller itself does not contain any implementation.
    For the interface controller of a Web Dynpro controller, the methods are implemented in the related component controller.
    For the interface controller of a component interface definition, the implementation is performed in the component controller of the embedding component.
    go through this WIKI :
    Introduction to controllers
    http://wiki.sdn.sap.com/wiki/display/WDABAP/Introductiontocontrollers
    and SAP online help :
    http://help.sap.com/saphelp_nw70/helpdata/en/b9/b82c4142aef623e10000000a155106/content.htm
    regards,
    amit

Maybe you are looking for