Fire A Portal Event With Source Id

Hi All,
I have this requirement where I need to fire an event from a Web Dynpro iView and a delivered iView (MSS Team Viewer) will receive it. The problem is the receiving iView (Team Viewer) need the source id parameter which is available in EPCF raiseEvent as an optional fourth parameter but the method WDPortalEventing.fire() method does not have it. Is there a workaround for populating this parameter? I wonder why it is omitted in the Portal Eventing API.
Thanks in advance.
Erwin

Hi Julia,
Yes, you can have 2 users with same uid in 2 different org but then, you must use 2 different authentication module and then your login url must be something like : .../UI/Login?org=yourOrgName
And then, this organization must have a Auth module.
Now, for the users, it's better to propose only the good login url.
ie, we have 5 differents login url based on 5 differents org. I'd change the login provider to alow the user to change its own organisation (with a list box). I've change the file under LoginProvider directory... (JES 2005Q4, Portal 6 : /etc/opt/SUNWps/desktop/default/LoginProvider/display.template
I think, in Portal 7, you have a jsp provider. Easier ;-)
a+
Philippe

Similar Messages

OT: Remind me, please, how to fire an onload event with javascript!

How do I do this without screwing with the body tag?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================

I just want to add a post in clarification -
1. I was using EasyFaq (a very nice extension from
ValleyWebDesigns) in a
non-standard way. Had I used it out of the box, so to speak,
I would not
have had these problems.
2. To reiterate, the problems I were trying to solve were, in
no way,
related to standard use of EasyFAQ.
3. My problems were solved both by following the suggestions
of Al Sparber,
and with help from E. Michael Brandt.
4. Indeed, I had some invalid code on the page, and it was
the presence of
that code that made things get a little cockeyed.
The page, if you care to see it, is here -
http://66.165.96.228/t_faq.php
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Murray *ACE*" <[email protected]> wrote
in message
news:enheq7$po6$[email protected]..
> You should know by now that I practice safe diddling.
>
> --
> Murray --- ICQ 71997575
> Adobe Community Expert
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
>
http://www.dreamweavermx-templates.com
- Template Triage!
>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
> ==================
>
>
> "Gary White" <[email protected]> wrote in message
> news:[email protected]..
>> On Wed, 3 Jan 2007 11:56:22 -0500, "Murray *ACE*"
>> <[email protected]> wrote:
>>
>>>But I'm still diddling.... 8)
>>
>>
>> Be sure to use protection!
>>
>> Gary
>
>

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

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 Parent-Child Explorer window

Hi experts,
I have a problem using the portal eventing.
A WebDynpro Abap application, embedded into the EP, opens a new browser window. I want to fire an event in the new browser window and handle it in the first one. So far so good. This works fine.
However if I want to close the new browser window in the same server round trip I fire the Portal Event, the event handler in the first window is not called. My question is: Is it possible to handle a portal event from a child browser window which closes itself in the server round trip, when the event is fired?
Thanks,
Thomas

Does sound like the child window is not propagating the portal event when it is also closing...
I'd suggest a work around (as I have no idea why that behaviour is occurring) perhaps firing the update event and also listening for it yourself? and then closing once the event has been received? If the child component receives the portal event, you'd assume that the parent would also.
Alternatively set a timed trigger after you fire the event - it shouldn't trigger until a screen refresh is done (which you'd hope would mean that the portal event was successfully fired) and close your window on the event fired by this UI element.
Do let us know if you find any other way around the problem!
Cheers,
Chris

I made a movie in iMovie then deleted the clips in it. I have reimported the clips in an event with the same name as previously and some clips in the movie are still saying source slip missing even though they are there. What can I do?

I made a movie in iMovie then deleted the clips in it. I have reimported the clips in an event with the same name as previously and some clips in the movie are still saying source slip missing even though they are there. Some clips are fine in the movie, but most are just black and when I hover over them, it says source clip missing. How to I fix this? Thank You

I did that too, then I did a migration assistant to a new Mac and ALL of my movies have Source Clip Missing now, even though the original clips are still in the iPhoto Videos. I can stand to re edit one or two projects, but not ALL.

Enterprise Portal integration with E-Sourcing Portal

Hi,
Has anyone done Enterprise Portal integration with E-Sourcing Portal.How can we use the E-Sourcing portal url in Enterprise Portal?
Thanks,
Rajani

Hello Rajani,
For Connecting web based Application we have to use AppIntergator Application.
Please go thorugh the blog and implement the same thing its many connect to your java portal.
blog is Integrating your Web Front-ends into the SAP Enterprise Portal using the Application Integrator
Please go through the below blog where its define how to pass user and password it the url iview.
SP12/SP20: Setting URL Dynamically in URL iView
Thanks
Chittya Bej
Edited by: Chittya Bej on Apr 5, 2010 11:31 AM
Edited by: Chittya Bej on Apr 5, 2010 11:33 AM

Fire EPCF event with WD ABAP in EP

In EP 7 I want to fire an EPCF event. I use the code below. A similar example from WD java works, but here I never receive the event. The Javascript part is right since it works together with an HTML and WD Java iView. Only the WD example is not working. Any hints?
ABAP ("triggered by a 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:xxDemo' PORTAL_EVENT_NAME = 'simpleevent' PORTAL_EVENT_PARAMETER = 'HelloFromABAP' ).
JavaScript:
EPCM.relaxDocumentDomain();
EPCM.subscribeEvent('urn:xxDemo', 'simpleevent', handle_simpleevent_Event);

Good hint, it was not the domain, but the protocol (http/https).
One iView was on https while the other one was setup for http.
However, now the question is: Can I setup EPCF somehow to work with mixed http/https IViews. In my HTML page I can use EPCMProxy, but I have no idea how to change this on a WD ABAP.
Regards

Portal events are not getting loaded into the Analytics database tables

Analytics database ASFACT tables (ASFACT_PAGEVIEWS,ASFACT_PORLETVIEW) are not getting populated with data.
Possible diagnosis/workarounds tried:
-Checked the analytics configuration in configuration manager, Enable Analytics Communication option checked
-Registered Portal Events during analytics installation
-Verified that UDP events are sent out from the portal: Test: OK
-Reinstalled Interaction analytics component
Any inputs highly appreciated.
Cheers,
Sandeep
In collector.log, found the exception:
08 Jul 2010 07:12:54,613 ERROR PageViewHandler - could not retrieve user: com.plumtree.analytics.collector.exception.DimensionManagerException: Could not insert dimension in the database
com.plumtree.analytics.collector.exception.DimensionManagerException: Could not insert dimension in the database
at com.plumtree.analytics.collector.cache.DimensionManager.insertDB(DimensionManager.java:271)
at com.plumtree.analytics.collector.cache.DimensionManager.manageDBImage(DimensionManager.java:139)
at com.plumtree.analytics.collector.cache.DimensionManager.handleNewDimension(DimensionManager.java:85)
at com.plumtree.analytics.collector.eventhandler.BaseEventHandler.insertDimension(BaseEventHandler.java:63)
at com.plumtree.analytics.collector.eventhandler.BaseEventHandler.getUser(BaseEventHandler.java:198)
at com.plumtree.analytics.collector.eventhandler.PageViewHandler.handle(PageViewHandler.java:71)
at com.plumtree.analytics.collector.DataResolver.handleEvent(DataResolver.java:165)
at com.plumtree.analytics.collector.DataResolver.run(DataResolver.java:126)
Caused by: org.hibernate.MappingException: Unknown entity: com.plumtree.analytics.core.persist.BaseCustomEventDimension$$BeanGeneratorByCGLIB$$6a0493c4
at org.hibernate.impl.SessionFactoryImpl.getEntityPersister(SessionFactoryImpl.java:569)
at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1086)
at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:83)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:184)
at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:173)
at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:69)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:481)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:476)
at com.plumtree.analytics.collector.cache.DimensionManager.insertDB(DimensionManager.java:266)
... 7 more
In analyticsui.log, found the exception below:
08 Jul 2010 06:50:25,910 ERROR Configuration - Could not compile the mapping document
org.hibernate.MappingException: duplicate import: com.plumtree.analytics.core.persist.BaseCustomEventFact$$BeanGeneratorByCGLIB$$6a896b0d
at org.hibernate.cfg.Mappings.addImport(Mappings.java:105)
at org.hibernate.cfg.HbmBinder.bindPersistentClassCommonValues(HbmBinder.java:541)
at org.hibernate.cfg.HbmBinder.bindClass(HbmBinder.java:488)
at org.hibernate.cfg.HbmBinder.bindRootClass(HbmBinder.java:234)
at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:152)
at org.hibernate.cfg.Configuration.add(Configuration.java:362)
at org.hibernate.cfg.Configuration.addXML(Configuration.java:317)
at com.plumtree.analytics.core.HibernateUtil.loadEventMappings(HibernateUtil.java:796)
at com.plumtree.analytics.core.HibernateUtil.loadEventMappings(HibernateUtil.java:652)
at com.plumtree.analytics.core.HibernateUtil.refreshCustomEvents(HibernateUtil.java:496)
at com.plumtree.analytics.ui.common.AnalyticsInitServlet.init(AnalyticsInitServlet.java:104)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4045)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4351)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.plumtree.container.Bootstrap.start(Bootstrap.java:531)
at com.plumtree.container.Bootstrap.main(Bootstrap.java:254)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:238)
at java.lang.Thread.run(Thread.java:595)
08 Jul 2010 06:50:25,915 ERROR Configuration - Could not configure datastore from XML
org.hibernate.MappingException: duplicate import: com.plumtree.analytics.core.persist.BaseCustomEventFact$$BeanGeneratorByCGLIB$$6a896b0d
at org.hibernate.cfg.Mappings.addImport(Mappings.java:105)
at org.hibernate.cfg.HbmBinder.bindPersistentClassCommonValues(HbmBinder.java:541)
at org.hibernate.cfg.HbmBinder.bindClass(HbmBinder.java:488)
at org.hibernate.cfg.HbmBinder.bindRootClass(HbmBinder.java:234)
at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:152)
at org.hibernate.cfg.Configuration.add(Configuration.java:362)
at org.hibernate.cfg.Configuration.addXML(Configuration.java:317)
at com.plumtree.analytics.core.HibernateUtil.loadEventMappings(HibernateUtil.java:796)
at com.plumtree.analytics.core.HibernateUtil.loadEventMappings(HibernateUtil.java:652)
at com.plumtree.analytics.core.HibernateUtil.refreshCustomEvents(HibernateUtil.java:496)
at com.plumtree.analytics.ui.common.AnalyticsInitServlet.init(AnalyticsInitServlet.java:104)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4045)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4351)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.plumtree.container.Bootstrap.start(Bootstrap.java:531)
at com.plumtree.container.Bootstrap.main(Bootstrap.java:254)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:238)
at java.lang.Thread.run(Thread.java:595)
wrapper_collector.log
INFO | jvm 1 | 2009/11/10 17:25:22 | at com.plumtree.analytics.collector.eventhandler.PortletViewHandler.handle(PortletViewHandler.java:46)
INFO | jvm 1 | 2009/11/10 17:25:22 | at com.plumtree.analytics.collector.DataResolver.handleEvent(DataResolver.java:165)
INFO | jvm 1 | 2009/11/10 17:25:22 | at com.plumtree.analytics.collector.DataResolver.run(DataResolver.java:126)
INFO | jvm 1 | 2009/11/10 17:25:22 | Caused by: java.sql.SQLException: [plumtree][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (ANALYTICSDBUSER.IX_USERBYUSERID) violated
INFO | jvm 1 | 2009/11/10 17:25:22 |
INFO | jvm 1 | 2009/11/10 17:25:22 | at com.plumtree.jdbc.base.BaseExceptions.createException(Unknown Source)

Key words from the error msg suggests reinstallation of Analytics is needed to resolve this.Analytics database is failing to get updated with the correct event mapping and this is why no data is being inserted.
"Could not insert dimension in the database",
"ERROR Configuration - Could not configure datastore from XML
org.hibernate.MappingException: duplicate import: com.plumtree.analytics.core.persist.BaseCustomEventFact$$BeanGeneratorByCGLIB$$6a896b0d"
"ORA-00001: unique constraint (ANALYTICSDBUSER.IX_USERBYUSERID) violated",
"ERROR Configuration - Could not compile the mapping document

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.

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 Events in web dynpro

Hi All,
I have created two web dynpro application iviews on the same page.
Now there is a button on the first application and when that button is pressed then I am triggering an event TRIGGER from it using method FIRE.
There is a text edit element on the second application.
I have registered the event TRIGGER in the second application in method WDDOINIT using method SUBSCRIBE_EVENT and assigned an action RECEIVE to it.In the method ONACTIONRECEIVE I have set data to be displayed in the text edit element.
However the above scenario is not working.
In methods subscribe_event and fire there is a parameter to be passed which is PORTAL_EVENT_NAMESPACE.What exactly is this parameter and what value to be passed to it.
Please provide any source code if any.
Thanks in advance
Aman Gupta

Hi Aman,
If you are still not able to do the Portal eventing then to make portal eventing work you should access portal using FQDN (fully qualified domain name).
Check Sap help for [Fully Qualified Domain Names |http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm] also check the SAP note 654982.

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

Fire A Portal Event With Source Id

Similar Messages

Maybe you are looking for