+

Search Tips   |   Advanced Search

Perform remote rendering with WSRP and the Web Content Viewer

To display web content on a portal that does not include IBM Web Content Manager, use the Web Content Viewer and the WSRP support in the portal. The Web Content Viewer can then retrieve and display content from a web content system on a different server.

Note that the preferred way to render content on one server from another server is to syndicate the content to the delivery server. On the delivery server, we can then locally render the content with a Web Content Viewer. However, remote rendering with WSRP is appropriate for service-oriented architecture (SOA) scenarios where to incorporate specific pieces of content into the website.

When using the Web Content Viewer for remote rendering with WSRP, the following conditions apply:

  • The remote web content server acts as the producer.
  • The portal with the Web Content Viewer acts as the consumer.

Remote rendering with WSRP is supported only when rendering content from the default virtual portal.

  1. Set up the WSRP environment between the Producer portal and the Consumer portal

    To use the Edit Shared Settings mode or the Configure mode in the portlet with WSRP, configure web service security between the Producer and the Consumer portals.

  2. Provide the Web Content Viewer Portlet as a WSRP service hosted on the remote web content server acting as the producer.

  3. Consume the remote Web Content Viewer provided as a WSRP service on the portal acting as the consumer.

  4. Configure the Web Content Viewer to display content, just as we would configure a local Web Content Viewer.

    When using the viewer with WSRP, settings for selecting content from a web content library show content from the remote web content system. Depending on the configuration of the Web Content Viewer, resources like resource bundle files or content processor plug-ins might be required. In such cases, the resources must be available on the remote web content server acting as the producer.


Limitations when using WSRP with the Web Content Viewer:

  • Because the concept of pages and web content pages does not exist in WSRP, we cannot use the dynamic link broadcasting feature with web content pages. When specifying how to broadcast links, do not select Dynamically select a web content page in the Broadcast links to field. Selecting this option has the same effect as broadcasting links to the current page.

  • Web content inline editing for the web content is not supported with WSRP.

  • The use of remote authoring action URLs in the web content is not supported with WSRP.

  • Tagging and rating for web content is not supported with WSRP.

  • Personalization elements are not supported with WSRP. Therefore, we cannot use features that require personalization rules. Examples: content targeting, federated documents, social rendering, and IBM Digital Data Connector (DDC) for HCL WebSphere Portal.

Limitations when using WSRP with the Web Content Viewer with other non-HCL WebSphere Portal consumers

In addition to the generic limitations when using the Web Content Viewer with WSRP, the link broadcasting feature of the viewer is not supported for the consumers of other vendors. This limitation is due to the fact the concept of pages and web content pages does not exist in WSRP. When specifying how to broadcast links, we can only select the option None.


Subtopics


Parent Delivering web content on a portal page

Related:

Web Content Viewers
WSRP services
Provide WSRP services as a Producer
Configure security on the Consumer portal