Portal eventing between Java WD iview to ABAP WD iview?

HI Experts ,
I have requirement on which,
The manager can select an employee from the EE Search iView (Object and Data Provider). All other iViews react on the selection and display data of the selected employee. Technically the personnel number is transferred from the search iView to the other iViews on the portal page, also to the related activity iView. This mechanism is called Eventing. The applications, started via the related activity iView, are launched with the personnel number as parameter. With other words the application, e.g. Manage Objects on Loan, can be directly started for the employee selected from the EE Search iView.
The Employee Information page is based on WD Java whereas the Objects on Loan application described in this specification is based on WD ABAP...........Due to different technologies used how to do the Pernr number transfer between these iviews?
If anybody have done this let me know the steps
Thanks in Advance,
Dharani

Hi Dharani,
You can use portal events to enable iViews running on the same page to communicate with each other. You just have to find out which event is fired by the WD Java iView and then you will have to register and handle the event in your WD ABAP application : http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f6/7d6f4151dc5758e10000000a1550b0/frameset.htm
You can use HttpFox (firefox plug-in) to find the details of the fired event (name, namespace...) by looking at the eventQueue parameter in the HTTP POST request.
Regards,
Pierre
Edited by: Pierre DOMINIQUE on Jul 9, 2009 11:16 AM

Similar Messages

Portal eventing between bsp and VC

Hi everybody
I need to use portal eventing to have a bsp and a VC iview communicate.
The bsp iview should be displayed within the VC iview as html view, raise a portal event with some sort of parameters inside, and then be dynamically hidden by the main iview.
I have often read about VC and bsp exchanging signals when belonging to the same page, but will this work even with bsp iview within VC iview? Has anyone ever achieved this?
thanks
Vincenzo

Hello Vincenzo,
It won't work, since the html view is implemented as an iframe on top of the model. If you want to use portal eventing, you should have the iViews inside a portal page which acts as a container and you also have the entire portal framework working for you.
Regards,
Natty

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 between Web DynPro Java iView and non-Web DynPro 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 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?

hi
Please write the below code snippet in ur jsp for notifyTestjavascriptfunction
function notifyTest( eventObj ) {
     eventParameter=eventObj.dataObject;
     // code to print the parameter "eventParameter"
Thanks
Harsimran

Client side event between Java iView and BSP application

Hi,
I am developing a BSP iView which listen to event raised by standard SAP HR TeamViewer iView. The TeamViewer iView raise a event when user click on the employee list.
EPCM.raiseEvent { "urn:com.sap.pct.hcm.orgmanagement:CurrentObject", "objectChanged", concatenatedKey);
My BSP is subscribing to the event and perform the myreceiveEvent function.
EPCM.subscribeEvent
( "urn:com.sap.pct.hcm.orgmanagement:CurrentObject", "objectChanged", myreceiveEvent );
However, my BSP returns an error message saying that EPCM is undefined. I know that I have to included the java script file. I checked with my basis team guy and they said there is not any js file in ICF. Can someone let me know which file I need to include in my BSP code and where is the file locate?
Thanks,
Eric

Hi Eric,
> the ICF where the BSP is stored
> is in the Oracle database
Eric... the place where the JS fragment - within the BSP - appears, is retrieved by some http request. The script=epcfproxy.js forces the browser to send a http request just to the same relative location the original page came from. Doesn't matter if something is within a database...
> Do you know how to locate the
> epcfproxy.js file in the WAS?
I think:
> and the epcfproxy.js file is in the zip file
> that you suggested
you have found it?! Put it to any place on the BSP server you can access, if you can't set it with relative url, use "/some/.../dir/epcfproxy.js" as location.
> If I am only EPCM but not EPCMPROXY,
> do I need to include the epcfproxy.js in my code?
Have a look at epcfproxy.js. It's no magic at all, you have to call top or parent (just look) and do some minor things. For sure, you can live without the proxy file, you have just to put the neede scripts explicitely on your page, that's not that fine, but it works.
Hope it helps
Detlev

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 pages

Hi,
I read around that portal eventing can be done only on the same page and not between pages, is this correct? if so, how do we make events between pages after all?
Thanks in advance,
Aviad

Hi Aviad,
Portal eventing takes place between different iviews of the same page only.
To pass between values between different pages, you can store the required value in a Portal Request object or Session object.
Also you can refer to this link,
iView to iView communication with EPCF
This link contains the code to establish connection between pages .Finally obtaining paramaters through request.getParamater().
Hope this helps,
Regards
Uma.
Note: It will be better from next time if you could post portal related queries in the EP forum to get quicker responses and ep related guidances.

Portal Eventing: communication betn BSP - WD iView

Hi All,
i am doing portal eventing between WD Abap iView and BSP iView with the help of blog <a href="/people/thomas.jung3/blog/2005/12/15/portal-eventing-a-solution-for-global-peace-and-harmony:///people/thomas.jung3/blog/2005/12/15/portal-eventing-a-solution-for-global-peace-and-harmony.
i have created page which has both iViews.
but i am not able to trigger the event from BSP to WD.
please suggest me some direction regarding this.
Regards,
Chandra

Hi,
the domain is the first part in your URL, for example www.sdn.sap.com.
In your case it will probably the hostname of your computer.
The reason for this is security. The portal eventing is build in Javascript and in Javascript it is not allowed to access other frames that are not in the same domain.
Best regards
Renald

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

Simple WD4A Portal Eventing does not work

Hello togehter,
I'm trying to get a simple Portal Eventing to work with two WebDynpro ABAP components. I read several threads as well as a blog from Thomas Jung about this but still have no eventing. What am I doing wrong? I think that it might be only a little obstacle but I can't get it. So what I didi is:
1.) Created 1st WD4A application with a button and an action behind that button:
DATA: l_api_component TYPE REF TO if_wd_component,
        l_portal_manager TYPE REF TO if_wd_portal_integration.
l_api_component = wd_comp_controller->wd_get_api( ).
l_portal_manager = l_api_component->get_portal_manager( ).
l_portal_manager->fire(
    portal_event_namespace = 'urn:my.namespace'
    portal_event_name      = 'test_event'
    portal_event_parameter = 'testValue' ).
2.) Created 2nd WD4A application with the following code in the WDDOinit-Method:
DATA: l_api_component TYPE REF TO if_wd_component,
        l_portal_manager TYPE REF TO if_wd_portal_integration,
        view TYPE REF TO if_wd_view_controller.
l_api_component = wd_comp_controller->wd_get_api( ).
l_portal_manager = l_api_component->get_portal_manager( ).
view ?= wd_this->wd_get_api( ).
l_portal_manager->subscribe_event(
    portal_event_namespace = 'urn:my.namespace'
    portal_event_name      = 'test_event'
    view                   = view
    ACTION                 = 'CATCH_EVENT' ).
and an action.
method ONACTIONCATCH_EVENT .
data: EVT_NAME type STRING,
        evt_parameter type string.
EVT_NAME = WDEVENT->GET_STRING( NAME = 'PORTAL_EVENT_NAME' ).
if EVT_NAME = 'test_event'.
    evt_parameter = WDEVENT->GET_STRING( NAME = 'PORTAL_EVENT_PARAMETER' ).
    DATA:
      ls_text TYPE if_main=>element_main,
      node_main TYPE REF TO if_wd_context_node,
      elem_main TYPE REF TO if_wd_context_element.
    node_main = wd_context->get_child_node( name = `MAIN` ).
    evt_parameter = 'IT WORKED'.
else.
    evt_parameter = 'did not work'.
endif.
ls_text-text_receiver = evt_parameter.
node_main->bind_element( ls_text ).
endmethod.
3.) FInally I created two iViews (for each WD4A application) and a page, linked the iViews in the page and made a preview. Unfortunately nothing happend in the second iVIew with the 2nd WD4A application in it.
Any help?
Thanx in advance
Matthias

Hello,
thanks for your answers. But the problem is not yet solved, the link gives nothing new for me.
To amend my first post:
After having created and activated my both small WD4A applications, I created 2 similar iViews (iViews for WebDynpro -> and chose WD ABAP) in my portal. Both iViews have the same namespace (which is SAP - is this ok?) and no application parameter.
Then I created both a Standard SAP page and a WebDynpro proxy page and added the 2 iViews as deltalink. The page and the iViews have the same prefix (but this is not important, isn't it?).
--> In both pages the portal eventing does not work
The ABAP server and the Portal server are the same machine and I call the portal with the full qualified domain name:
http://<servername>.<domain>:50000/irj/portal
When I test my WD4A applications in se80 I get the path http://<servername>.<domain>:8000/sap/bc/webdynpro/sap/z_event_receiver?sap-language=EN
so this is the same domain.
I even have an entry in my hosts-file for
<myInternalIp> <servername>.<domain>
- Do I have to specify the domain explicitly in addition when integration the WD4A applications in the portal?
- Is there a correlation between the Portal Event namespace, the namespace of my iViews and page and the domain name of my server?
- Does the portal event namespave to have the prefix urn: or not?
Thanks again in advance

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...

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 ).

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

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

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 events 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 events 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 events namespace.
·        name
The name parameter contains the portal events 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 controllers 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 views 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 Java WD iview to ABAP WD iview?

Similar Messages

Maybe you are looking for