Portlet communication

IBM WebSphere Portal supports multiple ways for portlets to exchange or share information.

Select the topic about the programming technique that is most appropriate for the application requirements from the following links.

• Public render parameters
  Public render parameters allow JSR 286 portlets to share navigational state information. They are specially useful for coordinating the multiple navigation or viewer portlets that display different information items that are all related to the same parameter name. The portal stores all portlet render parameters, including public render parameters, as an encoded part of the current portal URL. Therefore, public render parameters are correctly preserved by typical browser navigation actions such as the Back button and bookmarking.

• Advanced URL generation for data exchange
  For data exchange, IBM WebSphere Portal supports cross-portlet links

• Standard portlets publish and subscribe mechanisms
  Both JSR 168 and 286 portlets provide communication capabilities that enable us to pass information from one portlet to another. For JSR 286 portlets, these capabilities are included in the JSR 286 standard. For JSR 168 portlets, an extension defined by IBM provides these capabilities. Portlet developers define these capabilities. Portal administrators then determine whether or not these capabilities are used to pass information between portlets.

• Known issues and restrictions related to standard portlets publish and subscribe mechanisms
  

• Special purpose techniques for data exchange
  IBM WebSphere Portal supports special purpose techniques for data exchange.

• Shared portlet sessions
  The following communication methods are based on shared state between multiple portlets. This means that two or more portlets read and write to the same data.

Parent Develop portlets

Related concepts:

Struts Portlet Framework