Home

Developing eventing portlets

 

+

Search Tips   |   Advanced Search

 

Events communicate between JSR 286 portlets, exchanging data between portlets and triggering portlet activity such as updates to back-end systems. Events can work with other communication mechanisms such as cooperative portlets and click-to-action portlets.

RAD v7.5 provides wizards and user friendly editors to create and configure events.

Wizards help portlets publish and receive events. You specify a unique name for the event that has to be published or processed, using either the default name space or a custom name space. In addition, the alias address in the name space indicates that these events are compatible with any events of another portlet that has the same alias and can therefore work with input or output values of the provided address type.

Events subscribe to a server-side model or to a client-side model (IBM API and JSR API portlets targeted to WebSphere Portal v6.1) for declaring, publishing, and sharing information. Events can be distributed between local and remote portlets.

Server-side model portlets communicate with each other using the WebSphere Portal property broker. These portlets subscribe to the broker by publishing typed data items, or properties, that they can share as a provider or as a recipient.