Not Catching Portal Event

[Former Member]

I have a problem catching the portal events in our ABAP Dynpro application. I can debug the code and see the trigger executing the portal-Fire method in the sender application. However on the receiver application the event is not being raised/caught. I have tried using Thomas Jung's simple Sender-Receiver example ( http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/eae111e7-0b01-0010-6cb7-e0dd2b... ) and still it only works in our prototype system, not our development system.

I am trying to determine why there is a difference between the environments, perhaps it is because of the load balancing exists in development and not in the prototype environment. That is currently the only difference I see.

We are currently using ECC 6, EP 7.01 on both environments.

I'm assuming that this may be a server config issue, but I am not sure.

Any ideas on what to look at?

Thanks for the help.

[ChrisPaine · Accepted solution]

Hello,

not sure if it is the case, but it is always worth checking if you have the full domain specified EVERYWHERE in both portal and ABAP server - also when you are registering events etc.

I've had issues with domain name being fully specified in one place and only short version (both which resolve to same IP) in another - SAP and possibly other apps then refused to allow communication between the two systems as they were not part of the same domain (even though they were the same machine).

Hope this helps,

Cheers,

Chris

[thomas_jung]

From the online help:

All participating iViews must also belong to the same domain. Otherwise portal eventing cannot work due to JavaScript restrictions.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f6/7d6f4151dc5758e10000000a1550b0/frameset.htm

This is the most common reason for Portal Eventing not working.

[Former Member]

We have checked and the namespace and event name is the same everywhere.

We tried for portal eventing -

- Created a new connection which uses same abap server instance ( which we use ) u2013 Didnu2019t help.

- Created a new connection eliminating the http/ https mixture u2013 Didnu2019t help.

- For testing, Created a new folder and iviews .. etc. . . from the root as the folder we were working in had com.elc.portal namespace u2013 keeping name space same everywhere u2013 Didnu2019t help.

- Domain names are all same and correctly done.

As a result of these findings unless we find a solution, we are trying to implement the components by using a view composition.