Portal Events 

In the SAP Enterprise Portal, you can process different application types in special iViews on the same portal page. Here, iViews can be included using different technologies (such as Web Dynpro ABAP, Java, or BSP). The communication between these iViews takes place through an event function – portal eventing (or client-side eventing).

A Web Dynpro ABAP application can be registered for portal events. In this way, the Web Dynpro application can react to an event that was triggered in another iView in the portal. Therefore, it does not matter what technique you used to set up the application that is the basis for the other iView. The assignment as to which event handler is to be called when this event occurs is stored In the Web Dynpro application that has registered itself on the portal event. 

Similarly to registration, a Web Dynpro application can trigger any portal event. In this case, the event is passed to the portal by the respective iView. The portal passes the event to all iViews that have registered for this event. The application that finally handles this event can, in turn, have been set up with a different technique than the Web Dynpro application triggering it.

 

 

Portal eventing functions between iViews that are on the same browser window.

iViews can also open new browser windows using JavaScript. The new browser window is then the subordinate window and the iView browser window is the superordinate window.

Events can be transferred from an iView in a subordinate browser window to iViews in all superordinate browser windows.

Events cannot be transferred from a superordinate browser window to a subordinate browser window.

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