Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Display content in a rendering portlet
Rendering portlets are used to display IBM® Workplace Web Content Management content and components within a portal page.
There are two types of rendering portlets:
- Local Rendering portlet
- Display content within a portlet. Used with the same instance of WebSphere Portal Express where WCM is installed.
- Remote Rendering portlet
- Display content within a portlet located on a different portal server than the instance of IBM WebSphere® Portal Express where WCM is installed.
Only published content can be displayed with a rendering portlet. Draft content cannot be displayed and cannot be selected when configuring a rendering portlet.
Link elements cannot be displayed in remote rendering portlets.
- Install rendering portlets
- Configure the local rendering portlet
A Local Rendering portlet is used to display Web content on the same portal server as the instance of IBM WebSphere Portal Express where WCM is installed. - Configure the remote rendering portlet
A Remote Rendering portlet is used to display Web content on a different portal server than the instance of IBM WebSphere Portal Express where IBM Workplace WCM is installed. - Link portlets
Many Rendering Portlets can be added to a single IBM WebSphere Portal Express Server page, or a series of pages. Sometimes it will be necessary for different Rendering Portlets to interact with each other. - Rendering Portlet best practice
This topic describes some best practice tips for using rendering portlets. - Enable session handling
The default IBM Workplace WCM session handling works by initiating a new WCM session for each WCM portlet instance that is on a page. This can cause performance issues if many users access a page containing a large number of WCM portlets.