Portal event webdynpro

hi can u tell me how event can be triggered of portal with screen sot  with example

Hello,
Could you please clarify your question?
Thanks and Regards
Francisco

Similar Messages

  • PCUI - portal event - webDynpro Abap

    Hello,
    From standard PCUI, which used to create partner, I want to get a value partner and send it to a view that content Webdynpro Abap through portal Event.
    Is it possible? How?
    Thanks.

    Hello,
    Could you please clarify your question?
    Thanks and Regards
    Francisco

  • Settings Portal eventing - WebDynpro for Abap iView communication

    To connect two WD4A's using portal eventing; what work is to be done inside the portal environment.
    All manuals on SDN provide information action to be done within WD4A, Do we need to configure/set values in the Portal environment at al...

    Hi Marco,
    Check the url:
    [help.sap.com - Client-Side Eventing|http://help.sap.com/saphelp_nw70/helpdata/EN/ce/3e98408d953154e10000000a1550b0/frameset.htm]
    Best regards,
    G. Leurs

  • Java Portal Event not received correctly by ABAP Webdynpro

    We have a page that contains 2 iviews. 
    iView 1 contains the MSS Employee Search that raises portal event:
    Namespace: "urn:com.sap.mss.employeesearch"
    Name: "selection_changed"
    The second iview contains an ABAP Webdynpro program that subscribes to the Portal event. 
    The issue is that the event in the ABAP webdynpro is not being triggered.  It does get triggered if we first fire the event from the Java program, unsubscribe the event in the ABAP program them subscribe to the event in the ABAP program.  The event gets triggered at this time and the parameter can be retrieved. 
    If the event is fired a second time, nothing happens in the ABAP program. 
    The abap program works fine when another abap program triggers the same portal event.
    Also, the portal event is being picked up correctly by other SAP delivered JAVA programs.  I just cannot get a custom ABAP Webdynpro program to work...
    Any ideas, comments?
    Glenn

    Hi Glenn,
    Are you using https? Is your j2ee stack and abap stack in the same domain? In the past I have found that https can cause issues in the event communication between different applications.
    Cheers,
    Dion

  • Portal Eventing in Webdynpro ABAP

    Hello,
    I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
    In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
    But still the value sent in Com1 is not displayed in the Com2 Inputfield.
    Any help would be highly appreciated.
    Thanks.

    >
    SAPEPDeveloper wrote:
    > Hello,
    >
    > I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
    >
    > In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
    >
    > But still the value sent in Com1 is not displayed in the Com2 Inputfield.
    >
    > Any help would be highly appreciated.
    >
    > Thanks.
    Hi I assume the following, please correct me if my understanding is not correct.
    1.First of all you try this in Portal.
    2.The moment you fire the event, the comp-2 view is active and subscribed to the portal event.
    If the above are true then tell me if the portal eventing enter into the action ?Have you checked in bebug that your action is triggerred on portal_event ?
    If portal event is action handler is called then if you have a importing parameter portal_event_parameter then your input value should be there.

  • Webdynpro proxy page and portal event

    Hello there,
    is it possible to capture the event from employee search iview into my custom webdynpro ABAP iview?
    Since it occurs to me that when a portal page is developed as a "Default page template" I am able to capture the event whenever manager clicks on any employee in the list.  But when i create a page with "Web dynpro proxy page" template, I cannot subscribe to the event.
    We are trying to use employee search ivew and general data iview provided by SAP plus a custom WDA iview.  But when I do a default page template, I am able to caputre the event but general data iview does not show any data...and when I use the proxy page template...I get data in general data iview but I am not able to capture the event....and my custom WDA iview does not show anything...
    Employee search iview (previously known as team viewer) and general data iview are standard SAP iviews.
    any ideas...
    appreciate the help!
    Thanks....
    J.

    Hi Srivastava,
    The scenario is like this....
    page lay out:
    Team viewer iview here----provided by SAP
    General data iview here-----provided by SAP
    my WDA iview here-----custom iview
    if the page template is default template....I get data in my WDA iview for selected employee in the team viewer...but I go not get any data in General data iview
    if the page template is web dynpro proxy page...i do not get any data in my WDA iview...but i get data in general data iview...
    after debugging this thing...i found that for webdynpro proxy page...the portal event is not getting caught in my WDA iview...
    how to subscribe to a portal event if the iview is embedded in  a page which is using web dynpro proxy page template...
    Just want to share this...that portal eventing is working fine...if the my iview is embedded in a page which is using default page template...
    any ideas????
    anyone???
    Thanks...

  • Portal Eventing in WebDynpro Java Pros and Cons

    Does anyone have a link to an article that discusses th epros and cons of using portal eventing between dynpro development components between iViews rather than using one larger web dynpro application.  I am clear that reuse can be an issue if you don't make each view t's own development component but I also find portal eventing to be very lacking.  What do others think about on this issue and is that an SAP recommendation?
    Shawn

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a3c57e19-0d01-0010-ad8b-9edde6d1fae7
    Please read the restriction section.
    I will make much more sense if we need a high degree of data interchange between WDP components, to use context mapping and thus internal WDP calls rather than portal eventing.
    hth

  • Calling Portal event from ABAP class

    Hi Experts,
    I need a following clarificatrion, Please help,
    1. Is it possible to call a webdynpro method from a normal ABAP class?
    2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
    Is there any alternative method which can be used in ABAP having the same functionality.
    3. Is there any ways with which we can call portal event from ABAP class?
    Thanks,
    Shabir

    >1. Is it possible to call a webdynpro method from a normal ABAP class?
    I wouldn't necessarily recommend this approach. You shouldn't try to trigger events or any of the standard WDDO* methods from outside the WD Component itself.  That said, you can pass the object reference (like the WD_COMP_CONTROLLER object reference or the View Object Reference) into methods of normal classes.  Be careful if you are finding yourself calling a lot of your added methods from outside WD.  This is probably a sign that these methods should be in the Assistance Class or some other Class functioning as a Model Object.
    >2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
    Is there any alternative method which can be used in ABAP having the same functionality.
    What exactly do you want to do here?  Do you just want to get the relaxation script?  For what purpose?  You should never need to inject the relaxation script into WDA. 
    >3. Is there any ways with which we can call portal event from ABAP class?
    To what purpose.  Do you just want to delegate the triggering of the event that is inside WD Component to be called from a class?  If so you can pass the portal API object reference into a class from the WD Component.  However this only works while running within WD.
    How is this class used?  Are you running in WD?  Are you trying to generate some HTML code that runs in the portal independent of WD?

  • Portal eventing in WD ABAP

    Hello ,
    We have an requirment to pass values from one WD ABAP application iView to another in the Enterprise portal.Is there any configuration that needs be done in WD ABAP or is there any setting in EP that we need to do ??
    Rahul

    Rahul,
    Though most of this stuff is of web dynpro for java. You can just replace java Code with ABAP.
    You need to use eventing functionality.In the SAP Enterprise Portal, different application types in specific iViews can be arranged on one page. To communicate between the different iView types the portal provides the Enterprise Portal Client Framework (EPCF), also known as client-side eventing. This document describes how Web Dynpro applications can use EPCF.
    http://help.sap.com/saphelp_nw04/helpdata/en/24/243ca46e1c334f8a6f8b0792656bc7/content.htm
    The following code shows the signature of the subscribe method:
    WDPortalEventing.subscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
    for example
    WDPortalEventing.subscribe (“urn:com.sap.tc.webdynpro.test.portal”,
        “TestEvent”,
        wdThis.wdGetTestEventAction());
    You have to define the event’s name and its namespace. The combination of these two names must be unique.
    The third parameter is the Web Dynpro action, which should be mapped to the portal event. The action event handler is called if the Web Dynpro application receives the specified portal event on the client side. The mapping between a portal event and a Web Dynpro action is done automatically and it is completely transparent for the Web Dynpro application developer.
    You can reuse a Web Dynpro action for several portal events. If you want to receive the portal event’s data you have to define the following parameters for your Web Dynpro action:
    ·        dataObject
    The dataObject parameter contains the portal event parameter.
    ·        nameSpace
    The namespace parameter contains the portal event’s namespace.
    ·        name
    The name parameter contains the portal event’s name.
    It is useful to add the nameSpace and nameparameters to the Web Dynpro action if the action is reused for several portal events because you can use this information to differentiate between the portal events.
    Note: In the current version a portal event subscription is valid for a Web Dynpro view. Therefore you should add the required Java coding, for example in the wdDoInit() method of the generated view class. If you navigate between different views, you have to subscribe to every view for the portal event required.
    Unsubscribe from a portal event
    Unsubscribing from a portal event is very similar to subscribing. The following code shows the signature of the unsubscribemethod:
    WDPortalEventing.unsubscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
    for example
    WDPortalEventing.unsubscribe (“urn:com.sap.tc.webdynpro.test.portal”,
        “TestEvent”,
        wdThis.wdGetTestEventAction());
    Note: You must unsubscribe every Web Dynpro view, because subscription and unsubscription is valid only for the current view.
    Raise a portal event
    The following example shows how to raise a portal event. The signature is:
    WDPortalEventing.fire(java.lang.String nameSpace, java.lang.String event, java.lang.String parameter);
    for example
    WDPortalEventing.fire (“urn:com.sap.tc.webdynpro.test.portal”,
         “TestEvent”,
        “AParameter”);
    You can fire a portal event anywhere in your Web Dynpro application. The event is sent to the client  with the next response. You can also raise more than one portal event in a request-response cycle. Typically, you will fire a portal event in a Web Dynpro action event handler (for example, as a response to pressing a button).
    The following step-by-step example shows how to carry out portal eventing within two simple Web Dynpro example applications.
    Example Description
    The user can enter an arbitrary string in an input field. If the user presses the pushbutton Click here in the sender view, the input string will be displayed in a TextView UI element of the listener application.
    Prerequisites
    You have built two Web Dynpro applications. How to build Web Dynpro applications is described in Creating a Simple Web Dynpro Application. In each application you have created a Web Component with a view that uses the portal eventing.
    You can find the detailed procedure describing how to insert UI elements into a view in Creating a Simple Web Dynpro Application.
    Further information about the integration of a Web Dynpro application into the SAP Enterprise Portal can you find under Running a Web Dynpro Application in SAP Enterprise Portal.
    Procedure
    Creating the Web Dynpro applications
           1.      Create the Web Dypro project. Call it webdynproexample_portal_eventing.
           2.      Create two Web Dynpro components. Call them:
                                a.      EventSenderComponent
                                b.      EventListenerComponent
           3.      Create two Web Dynpro applications. Call them:
                                a.      EventSenderApplication
                                b.      EventListenerApplication
    Creating the necessary views:
    Create the layout of the EventSenderView in the EventSenderComponent as follows:
    Create the context structure of the EventingSender View:
    The context value attribute Name must be of type String.
    Create an action “Show”
    Define the data binding of corresponding UI element properties:
    The appropriate properties of the UI elements must be bound to the context that contains and displays the data.
           4.      Define a text, for instance, “Enter a text:” for the label UI element (ID: NameLabel) using the property text.
           5.      Bind the property value of the input field (ID: NameInputField) to the context attribute Name.
           6.      Bind onAction of the button (ID:ShowButton) to the corresponding action Show.
    Implementation of the view controller
           7.      If you create an action declaratively within the SAP NetWeaver Developer Studio, the Web Dynpro framework automatically generates an onAction method in the controller’s implementation. The generated method enables you to write code to fetch the input string and to fire the portal event. The fire method of WDPortalEventing passes the data and the name of the event that should be handled by the second application as parameters. The following code shows the implementation of onActionShow method:
    public void onActionShow(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionShow(ServerEvent)
       String name = wdContext.currentContextElement().getName();
        WDPortalEventing.fire("urn:com.sap.tc.webdynpro.example.portaleventing",
                           "Show",
                           name);
        //@@end
    Create the layout of the EventListenerView in the EventListenerComponent as follows:
    Create the context structure of the EventingListenerView:
    The context attribute Name must be of type String.
    Create an action, for example, ReactPortalEventing which should be mapped to the portal event.
           8.      Create an action ReactPortalEventing.
           9.      Add the parameter dataObject. It should have the type java.lang.String.
    Define the data binding of the corresponding UI element properties:
    The corresponding properties of the UI elements must be bound to the context that contains and displays the data.
    10.      Define a text for the NameLabel for example, The entry is displayed in a TextView UI element:
       11.      Bind the property text of the TextView UI element (ID: TextViewShow) to the context attribute Name.
    Implementation of the view’s controller
       12.      You have to subscribe to the event within the wdDoInit method. You have to define the namespaceof the event and the name of the event, for example Show. The third parameter is the Web Dynpro action, which should be mapped to the portal event.
       13.      You have to implement the action (ReactPortalEventing) that passes the dataObjectand fills the context with data. The following code shows the implementation of the wdDoInit and the reactPortalEventing methods:
    public void wdDoInit()
        //@@begin wdDoInit()
        WDPortalEventing.subscribe("urn:com.sap.tc.webdynpro.example.portaleventing", "Show",
        wdThis.wdGetReactPortalEventingAction() );
        //@@end
    public void onActionReactPortalEventing(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent, java.lang.String dataObject )
        //@@begin onActionReactPortalEventing(ServerEvent)
        wdContext.currentContextElement().setName(dataObject);
        //@@end
    Deploying the Web Dynpro Application
    Before you can call the Web Dynpro application, you have to build the Web Dynpro project and deploy the application on the J2EE Engine.
    Simple Testing of the Portal Eventing and Calling the Web Application
       14.      Create two iViews in the newly-created example folder as described in Running a Web Dynpro Application in SAP Enterprise Portal.
       15.      Create a page and add the two iViews to the newly-created page.
    To preview the Web Dynpro applications, choose the button Preview in the Portal Content Studio.
       16.      Enter your input and choose button Click here.
    Result
    A page preview will demonstrate portal eventing.
    Also, Please refer to these links,
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/21fc3f82c2e469e10000000a155106/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/portal integration of web dynpro applications.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cfb80249-0801-0010-3eaa-829afeac170f
    Please let me know whether its useful.
    Thanks,
    Raj.

  • Portal eventing between WD java and BSP popup

    Hi guys,
    I have a WebDynpro application that opens a BSP popup like that :
    WDPortalNavigation.navigateAbsolute(
              wdContext.currentURLElement().getEvaluationURL(),
              WDPortalNavigationMode.SHOW_EXTERNAL,
              "directories=no location=no menubar=no resizable=yes status=no toolbar=no",
              "evaluationdeformation",
              WDPortalNavigationHistoryMode.NO_DUPLICATIONS,
              urlParam.toString()
    When the popup is closed, I want to update the content of my webdynrpo application. I tried using portal eventing but it didn''t worked because the popup doesn't seem to know its opener....
    Is anybody have an idea ?
    Thanks in advance.
    Julien.

    Hi Julien,
    have you made sure that your BSP application is using EPCF? There is a flag you need to set to X in your BSP app for this to take effect. Also, you can not add javascript to a WD app, so calling the window.opener will not make any difference. However, you can subscribe to an event raised by another application in your WD app. It is possible to raise events between windows, one being a bsp and the other a WD or portal application. Check the following threads.
    [Portal Eventing: EPCMPROXY calls between two browser windows;
    [Client side eventing between MSS teamviewer and BSP application;
    Cheers,
    Dion

  • Portal Eventing between WDP Java iView & non-WDP iView

    Dear Experts,
    I have 1 Web DynPro Java iView and 1 non-Web DynPro (using JSPDynPage and JSP) iView, both attached to a page. When Web DynPro Java iView fire a portal raise event, the portal iView did not execute the javascript function tied to the event subscribed.
    Here is the code snippet which reside in the Web DynPro Java iView that is used to fire the event
    String param = "test";
    WPortalEventing.fire("urn:com.company.Test1", "TestEvent", param);
    This the code snippet that is in the jsp page
    function notifyTest(param){ 
          // code to print param value is here
    EPCM.subscribeEvent("urn:com.company.Test1", "TestEvent", notifyTest);
    Note:
    1. When Web DynPro Java iView fire the portal event the entire page is refreshed, including the non-WDP iView.
    2. When EPCM is replaced with window.top.EPCM, the page is refreshed, it is totally hanged with progress bar.
    Can anyone help to solve this problem?
    Edited by: CloudSOmnislash on Apr 8, 2009 6:06 PM

    Kumar, Rui,
    I have all my code inside a web dynpro component. All that I have in dynpro to work with (or that's what I know so far) is a WDPortalEventing object that I can use to access the fire, subscribeEvent and unsubscribeEvent methods. I still haven't found a way to get to the actual EPCM object that the Portal runtime gives you through javascript. And even if I get there, how am I supposed to write javascript in my dynpro code and later pass the value stored in the client data bag to the web dynpro context ?
    Simon,
    I had tried a small app yesterday and it didn't work when the iViews were not assigned to the same page. I will see if I can change my code anymore and get it working. I will make fresh posts to this thread as and when I find anything that works. In the mean time, if you have webdynpro iViews that talk to each other across pages, do let me know how you are doing it!
    Thanks for your replies...
    - Navneet.

  • Portal Eventing JSP TreeView

    I am trying to refactor a piece of code that was originally designed using HTMLB to create a tree view role menu that invokes an event in another iView.
    My question is, can portal eventing be done with traditional  JavaScript as opposed to using HTMLB? We are not using WebDynPro for this project.
    I would like to use a jsp treeview to re-engineer the existing htmlb tree structure, but wanted to get some feedback on the options...thanks

    Hi Ryan,
    > whether or not the eventing
    > has to be done on the server side
    The eventing between iViews is done by EPCF, and this is, as said, a pure JS framework. Often it might be senseful for the iView which gets "informed" by some other iView about some event with some event data, to use this data and to refresh itself. This depends on the concrete use case.
    Having this said, it is obviously totally independent if you usue EPCF from some portal HTMLB-JSP, a "pure" JSP without HTMLB or a BSP - all of these things end up in HTML with the possibility to include JS - the EPCF calls.
    See http://help.sap.com/saphelp_nw04/helpdata/en/82/04b340be3dff5fe10000000a155106/frameset.htm for further details.
    > Can all of this be done without post backs
    > to the server,
    As said before, the eventing through EPCF works on client side, but in many cases it makes sense to refresh some iView with some data sent by the event.
    Imagine a List-Details iView combination. The user has one iView with a list of products and another iView with the details of one product. By choosing one product in the list iView, this iView could raise an event, which is subscribed by the details iView, for example passing some product-ID. Now it would make sense to refresh the details iView with the ID given. The alternative would be to load all details data and only to show up the chosen details and to switch on the event. Two disadvantages: It's much harder to code and you may have a very long transmission/network time for the inital call of this iView.
    > without using htmlb using JSP not BSP
    See above, it's independent from the HTML-Layer.
    > can you store a result set in a client side object,
    > like a cookie, and if so, how?
    For sure, somehow you can (at least some representation). But here I'm unsure again, in which direction this question aims, if this is really helpful.
    Hope it helps
    Detlev

  • Portal Eventing now working!!

    Hi ,
    I am following sap link for portal eventing: http://help.sap.com/saphelp_nw04/helpdata/en/cf/18721b4079334cac4a3bd3862b185b/frameset.htm
    1)I am facing problem passing data from Sender to Listener iview , however when i hardcode the value in Listener iview then it shows value(it suggest that portal eventing is taking place but data is not passed)
    2)Is there a problem with Namespace. from where i can find namespace of my webdynpro application ?
    Thanks in Advance,
    Regards
    Hemant

    Hi,
    Please post some code on how you have done this.
    There aren't a lot of relevant logging on the server, since the portal eventing is done client side on your browser using javascript.
    Dagfinn

  • Problem when handling Portal events

    Hi all,
    I am trying to handle portal events between two Iviews on a same page.For this I am using all the necessary parts from coding prospectives(eg. Event fire, Subscribe event and action handler method).
    But I am not able to handle portal events.I found some properties on Iview and page level as:
    1) Web Dynpro Client on Iview level - Default auto (Some threads suggest that events only works on HTML pages).
    I change it to plain HTML, but having doubt that is this value passed to this property.
    2) ID Prefix - Default blank (I-View level)
    I assign com.sap to it and also assign application name to ID.
    Is these will affect something on Portal handling.
    I also watch some e-learning sessions, I do similer to those sessions but at my end I still facing problem.
    Please suggest what I will do more to handle Portal events.
    Thanks
    Sanket sethi

    I am using this code to  fire and catch Portal events.Please look at the code and suggest where I am lacking.
    Fire:
    data node                               type ref to if_wd_context_node.
    data portal_event_namespace  type string value 'urn:com.sap.webdynpro.testApplications.testEvent'.
    data portal_event_name          type string value 'FMP_EVENT'.
    data portal_event_parameter   type string.
      data lr_componentcontroller type ref to ig_componentcontroller .
      data l_api_componentcontroller type ref to if_wd_component.
      data lr_port_manager type ref to if_wd_portal_integration.
      lr_componentcontroller =   wd_this->get_componentcontroller_ctr( ).
      l_api_componentcontroller = lr_componentcontroller->wd_get_api( ).
      lr_port_manager = l_api_componentcontroller->get_portal_manager( ).
      lr_port_manager->fire(
        exporting
          portal_event_namespace = portal_event_namespace
          portal_event_name      = portal_event_name
          portal_event_parameter = portal_event_parameter ).
    Catch: (Register and receive parameter)
      data node                                  type ref to if_wd_context_node.
      data subscribe_hello                   type wdy_boolean.
      data  view                                  type ref to if_wd_view_controller.
      data  portal_event_namespace    type string value 'urn:com.sap.bc.webdynpro.<namerspace>.<Name>.
      data  portal_event_name             type string value 'FMPEVENT'.
    here is the name of the action where the portal event will be received!
    you have to create this action in the application!!
    data  portal_event_action_name  type string value 'RECEIVE_PORTAL_EVENT'.
      data lr_componentcontroller type ref to ig_componentcontroller .
      data l_api_componentcontroller type ref to if_wd_component.
      data lr_port_manager type ref to if_wd_portal_integration.
    DATA lo_api_component  TYPE REF TO if_wd_component.
    DATA lo_portal_manager TYPE REF TO if_wd_portal_integration.
    lo_api_component = wd_comp_controller->wd_get_api( ).
    lo_portal_manager = lo_api_component->get_portal_manager( ).
    DATA lo_api_controller  TYPE REF TO if_wd_view_controller.
    lo_api_controller ?= wd_this->wd_get_api( ).
    CALL METHOD lo_portal_manager->unsubscribe_event
      EXPORTING
        portal_event_namespace = portal_event_namespace
        portal_event_name      = portal_event_name
        view                   = lo_api_controller
      lr_componentcontroller =   wd_this->get_componentcontroller_ctr( ).
      l_api_componentcontroller = lr_componentcontroller->wd_get_api( ).
      lr_port_manager = l_api_componentcontroller->get_portal_manager( ).
      view ?= wd_this->wd_get_api( ).
       call method lr_port_manager->subscribe_event
          exporting
            portal_event_namespace = portal_event_namespace
            portal_event_name      = portal_event_name
            view                   = view
            action                 = portal_event_action_name.
      data node                              type ref to if_wd_context_node.
      data portal_event_namespace type string.
      data portal_event_name          type string.
      data portal_event_parameter   type string.
      portal_event_namespace = wdevent->get_string('PORTAL_EVENT_NAMESPACE').
      portal_event_name          = wdevent->get_string('PORTAL_EVENT_NAME').
      portal_event_parameter   = wdevent->get_string('PORTAL_EVENT_PARAMETER').
      node = wd_context->get_child_node( name = 'PORTAL_EVENT_DATA' ).
      node->set_attribute( exporting name = 'PORTAL_EVENT_NAME' value = portal_event_name ).
      node->set_attribute( exporting name = 'PORTAL_EVENT_PARAMETER' value =                         portal_event_parameter ).

  • Determine Portal event namespace on subscribe event

    Hi all,
    I am handling the portal events.When I subscribe the fired portal event how to determine the Portal event namespace.
    Please suggest.
    Thanks
    Sanket

    HI Sanket,
    When you fire the event  with the following code, the combination of first 2 parameters in a method needs to be unique and the subscribe function should have similiar combination. Namespace is the first parameter, event name is the second and third is parameter variable(DataObject)
    WDPortalEventing.fire("urn:com.sap.tc.webdynpro.eventing","Send", name);
    Thanks
    Harsimran Kaur
    Edited by: Harsimran Kaur on Apr 6, 2009 12:03 PM

Maybe you are looking for

  • How to get the back button if we to go the 2nd drill down report??

    Hi, I have a drill down report for the main report. And have detailed drill down as in 1st report>2nd report>3rd report. But once i goto drill down, the return button is there which directs to main report i.e. 2>1, But once i goto 3rd, i do not get t

  • JSP page import problems

    Hi, i've got a problem with importing java classes into my jsp file. i use the following method: <%@ page import="Person" %> Person is originally a selfwritten class which lies in the subdirectory WEB-INF/classes of my webapps directory of my tomcat

  • In-Ear Headphones Applecare

    Hello, I wanted to ask, are actually in-ear headphones in the "apple care" for iphones with the Service & Support?

  • Oracle Dataguard issue

    Hi Could you please help me on this... We started Oracle data guard setup for a production database where primary is located in Europe Region and standby is located in Latin America. We configured dataguard parameters on primary and performed cold ba

  • Firefox rollover issue

    I have a PNG image that i intend to use as a "CLICK HERE" button. When I connect a link to the image either dreamweaver or firefox is adding a yellow border as a rollover to this image, however in Safari the button works as intended. Another result o