Perform remote rendering with WSRP and the web content viewer

To display web content on a portal that does not include Web Content Manager, we can use web content viewer and WSRP.

The preferred way to render content on one server from another server is to syndicate the content to the delivery server. Remote rendering with WSRP is appropriate for SOA scenarios.

Conditions:

• The remote web content server acts as the WSRP Producer.

• The portal with the web content viewer acts as the WSRP 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 Edit Shared Settings or Configure modes, set up 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 WSRP Producer.

3. Consume the WSRP service on the portal acting as the WSRP Consumer.

4. Configure the web content viewer to display content.

   Settings for selecting content from a web content library show content from the remote web content system.

   Resources like resource bundle files or content processor plug-ins might be required. In such cases, the resources must be available on the remote WSRP Producer.

   Limitations:

   • We cannot use the dynamic link broadcasting feature with web content pages. In the field...
     Broadcast links to

     ...do not select...

     Dynamically select a web content page

     Selecting this option has the same effect as broadcasting links to the current page.

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

   • All tagging and rating features for web content are not supported with WSRP.

   • Personalization elements using selection rules based on the federated documents resource collection cannot be used with WSRP.

Parent: Deliver web content on a portal page

Related: Web content viewers