Web content viewers
Overview
Web content viewer portlets display content from a web content library as part of a portal page.
A single web content viewer can be sufficient for simple content. You can use multiple web content viewers to aggregate content from different libraries.
The JSR 286 web content viewer is suited to nearly all situations for local and remote rendering. For a few special cases, the older IBM Portlet API web content viewer can still be used.
JSR 286 web content viewer
Based on the Java Portlet Specification 2.0 (JSR 286).
Web content pages are supported. Because you attach content to a web content page when you create it, the JSR 286 web content viewer automatically displays that content without requiring configuration when you add the web content viewer to the page.
The portlet does not create a portlet session for rendering web content for both anonymous and authenticated portal users.
Support for portal site analysis is available to measure how frequently content items are visited.
Performance is improved over the traditional web content viewer.
Remote rendering is performed using WSRP.
Deprecated IBM Portlet API web content viewer
Although the JSR 286 web content viewer is recommended for the majority of uses with Web Content Manager, there are limited situations where the JSR 286 web content viewer cannot be used. For these situations, the traditional web content viewer, based on the IBM Portlet API, can be used.With version 7, the IBM Portlet API web content viewer has been deprecated and removed from the default installation. Wherever possible it is recommended that you adapt web content environment to use the JSR 286 web content viewer to ensure future compatibility. If you have migrated from a previous version of the product to version 7, you can also convert existing instances of the IBM Portlet API web content viewer to the JSR 286 web content viewer, as described in the topic "Converting instances and settings of the IBM API Web Content Viewer portlet to the standard API Web Content Viewer Portlet."
The traditional web content viewer is available for the following cases:
URLs built on unsupported format
The JSR 286 web content viewer uses an updated URL format for links to web content that is not compatible with the URL format used with the IBM Portlet API web content viewer. Because of this, the JSR 286 web content viewer cannot process the following URLs:
- URLs generated by the IBM Portlet API web content viewer.
- URLs from external web sites or from third party applications that use the WCM_GLOBAL_CONTEXT query parameter.
If web content environment still requires support for the previous URL format, you can install the IBM Portlet API web content viewer to process those links.
Remote rendering from portals older than version 7
Remote rendering in version 7 is generally performed using the WSRP support of the JSR 286 web content viewer. However, if you still need to display web content from a server that is running a version older than version 7, you can install the IBM Portlet API remote web content viewer.
Remote rendering with authoring tools components or remote authoring action URLs
The WSRP support in the JSR 286 web content viewer does not support the use of authoring tools components or remote authoring action URLs. If web content system uses either of these features, you will need to use the IBM Portlet API web content viewer to display this content on a remote server.
To install the IBM Portlet API web content viewer, install the appropriate file from...
PORTAL_HOME/wcm/prereq.wcm/installableApps
where...
Local rendering ilwwcm-localrendering-portlet.war Remote rendering ilwwcm-remoterendering-portlet.war Refer to the version 6.1.5 product documentation for details on installing portlets and configuring the web content viewer.
Displaying content with web content viewers
Related concepts
Work with web content pages
Converting an IBM API web content viewer to the JSR 286 API
WebSphere Portal 6.1.5: Install a portlet
WebSphere Portal 6.1.5: Writing links to Web Content Management content