Linking portlets

 

+
Search Tips   |   Advanced Search

 

Many Rendering Portlets can be added to a single IBM WebSphere Portal Server page, or a series of pages. Sometimes it will be necessary for different Rendering Portlets to interact with each other.

For example, A IWWCM Menu Component could be placed in one Rendering Portlet, and a WCM Content item in another. If you would like the content item to change when a different link is clicked in the menu, "link" the two portlets. This type of behavior is enabled by setting different "broadcasting" and "receiving" parameters in the Links section of the Rendering Portlet configuration view.

 

Broadcasting links

The state or context of a Rendering Portlet is not sent directly from one portlet to another. Rendering Portlets can be configured to broadcast their current state or context to other Rendering Portlets on the same WebSphere Portal page, or to Rendering Portlets on other pages. Any information broadcast by a Rendering Portlet will only be received by Rendering Portlets configured to receive this information.

 

Receiving links

A Rendering Portlet can receive information on the state or context of the current WCM content item or component being displayed within it, or from WCM content items or components displayed within other Rendering Portlets that are "broadcasting".

 

Stand-alone components

Stand-alone components are WCM Components displayed within Rendering Portlets that:

  • Do not broadcast links

  • Receive Links from themselves

If a stand-alone component contains a link, when clicked the WCM component will be replaced by the content of the link. The Rendering Portlet will then take on the behavior of the displayed content. The originally displayed WCM component will not be displayed again until a new portal session is started.

When adding a stand-alone component to a Rendering Portlet, it is possible to also select an alternative presentation template in the content view of the content section. When a link is clicked in the stand-alone component, the content that is then displayed will use the alternate presentation template.

 

Example 1 - Menu and content

In this scenario, one portlet would contain a WCM Menu and another portlet would contain some WCM content. Links would need to be created between the two portlets to enable the displayed content to change when a different links in the menu were selected.

Portlet Broadcast Links to: Receive Links from:
Menu This Page None
Content None Other Portlets and This Portlet

 

Example 2 - Navigator and content

In this scenario, one portlet would contain a item views navigator and another portlet would contain some WCM content. Links would need to be created between the two portlets to enable the displayed Content to change when a different links in the navigator were selected. The navigator would also change to reflect the current state of the content being displayed.

Portlet Broadcast Links to: Receive Links from:
Navigator This Page Other Portlets and This Portlet
Content This Page Other Portlets and This Portlet

 

Parent Topic

Displaying content in a rendering portlet