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

Similar Messages

Portal Event name and namespace (ECM)

Hi Experts
I want to register for the Portal Event that gets triggered when an employee is selected.
In the Compensation Information page, there is an employee search iview. I need to know what Portal Event name and namespace is triggered when an employee is selected.
Does somebody already know what the name and namespace is?
thanks in advance
Anton Kruse

Found the solution here: Parameter Passing from WDJ iview to WDABAP Iview
call function 'HR_ASR_WDA_GET_EMPLOYEE'
   exporting
      id = 'MSS01'   "ABAP Memory ID To get the PERNR Selected.
   importing
      pernr = gv_pernr.

Subscribe to Portal Events

Hi
Im tryng to make a AbstractPortalComponent subscribe to a Client-side Portal event raised by EPCM. I know this is possible using javascript code as EPCM.subscribevent but i need to run some Java Logic when the event happens.
Basicly i want every Portal Navigation ( EPCM.Navigate Event) to raise a eventhandler on my portal component/service that will validate if i have to pass aditional parameters to the navigation node). This parameters are based on an array of correspondencies Navigation_Node_Path / Parameters in Java. The Parameters are generated used a number of portal services methods like navigation helperservice etc.
Thanks in advance

Hi Jason,
EPCM.raiseEvent('urn:com.sapportals:framework','CollapseNavPanel', "");
EPCM.raiseEvent('urn:com.sapportals:framework','ExpandNavPanel', "");
Best regards, Maksim Rashchynski.

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.

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 or FPM - navigate to diff comp controller view and ....

Hi,
   The query is simple, i guess -
From a particular component controller ( not from its view ) how can i navigate to a view of different component controller.
Also how can i navigate to diff view ( within the same controller ) by the same controller.
I tried Portal Eventing and FPM -
WDPortalEventing.fire( "urn:com.sap.xss.hr.per.tw.bank.overview.Vc...Overview.Eventing","send","N");
and at receiver
WDPortalEventing.subscribe("urn:com.sap.xss.hr.per.tw.bank.overview.VcPerBankTWOverview",
     "send", wdThis.wdGetPortalEventAction() );
it didn't worked.
Also tried FPM after creating an FPM view , but need inputs from you to link it in event links as target.
ECC6.0 - mysaperp2005.
EP7
THanks,
Regards,
Ankit

Vishwas.. / Chaitanya -
Thanks for the reply -
-   I want to navigate to CompB's view from Component Controller A ( not frm the view ).
- Another query was - how can i get to View2 of comp controller A via Comp Controller A itself.
Your answers were helpfull but i need some more info..
The forums link u mentioined had some body mentioned this -
" 2 ways to do this...
The first way:
1) Create a separate window in Comp B for each view that you need to navigate directly to (an interface view is created for each window)
2) Embed the multiple interface views of Comp B into Comp A
3) Use a separate outbound plug in Comp A for each Comp B interface view
AFTER STEP 2 ON STEP 3 HOW CAN I HAVE AN OUTBOUND PLUG FROM COMP CONTROLLER A ( not from the view ). i.e., outbound plug from Comp A to the Comp B inteface view
Lokesh -
Trying same namespace didn't worked , - i guess Portal eventing might work between views , but here i have a component controller and a view.

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

Embedded WD and portal eventing

Hi,
In MSS-> Equipment I have the standard Employee Search wd component and a custom web dynpro component that displays obejcts on loan(pa0040) embedded in an iView. The PERNR is being successfully passed to the custom application when the user clicks on the employee name. Is there any way I can clear the objects displayed if a user clicks on anything else in the standard wd component. For example, if they click on a company name in the Organisation structure?

Probably the whole thing works based on Portal events. I assume they have no other means to know what is being selected. Best way forward is subscribe in custom component to other events such as Organisation. If there are no events fired in that cases then you may have problem here. You can try enhance the existing component and fire a clear event. Subscribe this event in your custom component.
Handle this clear event in your custom component and invalidate the node for loan.

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.

Portal event not working

Hi,
I am try to handle portal event in my WD ABAP i view. The event is fired by WD Java team viewer iView in MSS. What I want is when someone select an employee from team viewer iview from MSS, my WD ABAP iview should react accordingly.
I check SAP note 1112733 for corresponding solution to handle event but it didnt worked. My WD ABAP application is not able to subscribe to the event.
I wrote the following code in WDINIT method of my view
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:com.sap.mss.employeesearch'
portal_event_name      = 'selection_changed'
view                   = view
action                 = 'RECIEVE_EMP_DATA' ).
and the code written in event handler method is:
METHOD onactionrecieve_emp_data .
DATA: evt_name TYPE string.
DATA lo_nd_gc_event_data TYPE REF TO if_wd_context_node.
DATA lo_el_gc_event_data TYPE REF TO if_wd_context_element.
DATA ls_gc_event_data TYPE wd_this->element_gc_event_data.
DATA lv_event_string LIKE ls_gc_event_data-event_string.
navigate from <CONTEXT> to <GC_EVENT_DATA> via lead selection
lo_nd_gc_event_data = wd_context->get_child_node( name = wd_this->wdctx_gc_event_data ).
get element via lead selection
lo_el_gc_event_data = lo_nd_gc_event_data->get_element( ).
get single attribute
lo_el_gc_event_data->set_attribute(
    EXPORTING
      name = 'EVENT_STRING'
      value = 'before handle' ).
evt_name = wdevent->get_string( name = 'PORTAL_EVENT_NAME' ).
IF evt_name = 'selection_changed'.
    lv_event_string = wdevent->get_string( name = 'PORTAL_EVENT_PARAMETER' ).
get single attribute
lo_el_gc_event_data->set_attribute(
    EXPORTING
      name = `EVENT_STRING`
      value = 'handled' ).
ENDIF.
ENDMETHOD.
In debugging mode, I am not able to go inside my event handler method.
Please help why this event is not getting handled .
Thanks
Vishal Kapoor

>
Jon MB wrote:
> Hi Thomas
>
> Please, can you confirm the restriction above applies to the following scenario?
>
> - We have an ECC system with the following URL: ecchost.domain.suffix
> - We have a portal with the following URL: portalhost.subdomain.domain.suffix
>
> We have configured the portal for domain relaxing and SSO is working fine.
>
> Each system is under the same domain (domain.suffix), but in different subdomains.
>
> Shoudl this be the cause of ABAP WD applications not working? Is there any way to fix this without changing the URLs?
>
> Thanks in advance,
> Jon
I'm not a portal consultant, so I can only related the requirement from the WDA side that the domains must be the same. I don't know if the domain relaxation on the portal sise will take take of the subdomain. My guess is that if you are having problems, that it doesn't. You would probably need to ask this question in the portal forum or discuss with a portal consultant.
> Is there any way to fix this without changing the URLs?
I don't know of any.
>Shoudl this be the cause of ABAP WD applications not working?
What do you mean, not working? Is the portal eventing just not work or are you not able to load the WDA applications at all.

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

WD Abab - Portal Events from Employee Search

Hi guys,
I want to get the PERNR selected in Employee Search.
I have two ivews,
Employee Search and WD Abap.
I´m using this source to subscribe the portal event.
method WDDOMODIFYVIEW .
data l_api_component type ref to if_wd_component.
data 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( ).
data l_wd_view type ref to if_wd_view_controller.
l_wd_view ?= wd_this->wd_get_api( ).
call method l_portal_manager->subscribe_event    exporting
      portal_event_namespace = 'urn:com.sap.pct.hcm.orgmanagement:CurrentObject'
      portal_event_name      = 'objectChanged'
      view                   = view
      action                 = 'PORTAL_EVENT'.
endmethod.
What´s the action I have to implement ?
And How I could get the PERNR selected ?
Best Regards,
Silvio Galery

Do i understand you correctly that you are not getting the portal event ?
This can be several reasons ?
Both portal system and WDA server has to be in same domain and same proptocol to communicate with Portal event.
Please check in that direction and search posts on this topic.

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

Determine Portal event namespace on subscribe event

Similar Messages

Maybe you are looking for