ShowTable of Contents
A local rendering portlet displays Web content on the same portal server as the instance where Web Content Manager is installed.
Example of a local rendering configuration
A remote rendering portlet displays Web content on a different portal server than the instance where Web Content Manager is installed.
Example of a remote rendering configuration
You can use the WCM API with remote rendering, but the JSP just needs to be on the Web Content Manager servers in Cluster B.
If you are using portal document manager integration, ensure that the portal document manager documents exist on the Web Content Manager servers in Cluster B.
If you are using personalization integration, ensure that the personalization rules exist on the Web Content Manager servers in Cluster B.
Supporting remote rendering portlets on backlevel WebSphere Portal Servers
Where possible IBM will support each version of the remote rendering portlet on older versions of WebSphere Portal. This is useful when performing upgrades of WCM as you can leave your delivery servers on the older version (for example if you have portal applications which would have to be rewritten if the portal server was upgraded). The current list of supported configurations are:
WCM 5.1.0.x RRP Portlet: Is supported on WPS 5.1.0.x server
WCM 6.0.x RRP Portlet: Is supported on WPS 6.0.x and 5.1.0.x servers
WCM 6.1.0.x RRP Portlet: Is supported on WPS 6.1.0.x and 6.0.x servers
WCM 7.0.0.x RRP Portlet (Deprecated): Is supported on WPS 7.0, 6.1.0.x and 6.0.x servers
WCM 8.0.0.x RRP Portlet (Deprecated): Is supported on WPS 8.0.x servers only
When to use Remote versus Local Rendering
The following table describes the considerations that you should take into account when determining whether to use local or remote rendering portlets, broken into suggested Primary and Secondary considerations. Based on your own requirements, you should determine which considerations are primary for you.
Note: From WCM 7.0 the RRP portlet is officially deprecated and therefore its use is now discouraged.
|WCM Request throughput|| Lower volume of requests || Higher volume of requests|
|Portal Request throughput|| Higher volume of requests || Lower volume of requests|
|Total (WCM and Portal) Request throughput|| Higher volume of requests || Lower volume of requests|
|Cost|| Less Web Content Manager licenses required || More Web Content Manager licenses required|
|Dynamic Linking using Web Content Pages|| No || Yes, JSR 286 Portlet only|
|Tagging and Rating support|| No || Yes, JSR 286 Portlet only|
|Mobile Portal Accelerator support|| No || Yes, JSR 286 Portlet only|
|WCM Authoring Tools (ie. Inline Edit) support|| Yes, but requires custom building of inline-edit URLs to redirect back to remote WCM server. See |
for more information | Yes, out of the box
|WCM Basic Cache Support|| No || Yes|
|WCM Advanced Cache Support|| Yes || Yes|
|Upgrade Web Content Manager independent of WebSphere Portal|| Yes || No|
|WSRP (For rendering content)|| Yes || No|
|Web Content Manager can be placed behind a firewall|| Yes, but only when redirection is set up and fully qualified URLs are disabled || No|
|Web Content Manager CPU activity on delivery portal nodes|| Low || High|
|Complexity of administration|| More servers to administer || Less servers to administer|
|Network traffic|| Because the path is longer, the network congestion is higher || Less network activity|
|System CPU requirement|| Less CPU speed required (as you have two servers, one for Portal and another for WCM) || Higher CPU speed required (as you have a single server for both WCM and Portal)|
|Additional Security configuration required || Yes (for authentication between Portal and WCM server) || No|
|Location and execution of WCM JSP Components || Remote WCM Server || Local WCM Server|
|Location and execution of PZN Rules || Remote WCM Server || Local WCM Server|
NOTE: These tables were based on 'Remote Rendering' including one Portal server (with the Remote Rendering Portlet on it) and one WCM server and 'Local Rendering' including a single server for both Portal and WCM