+

Search Tips   |   Advanced Search

Convert the IBM Portlet API Remote Web Content Viewer to the JSR 286 Web Content Viewer

If we use the IBM Portlet API Remote Web Content Viewer portlet in the source environment, complete the following task after migration to convert to the JSR 286 Web Content Viewer. The Remote Web Content Viewer portlet based on the IBM Portlet API was removed from IBM Web Content Manager v8.5, and is no longer supported. The migration process transfers the portlet and the portlet instances from the portal pages to the target environment. After migration, we must replace the IBM Portlet API Remote Web Content Viewer portlet with the JSR 286 Web Content Viewer portlet.

  1. Check if we installed the IBM Portlet API Web Content Viewer portlet and identify potential portlet clones.

    1. Go to Administration > Portlet Management > Web Modules.

    2. Search for the web module with the file name ilwwcm-remoterendering-portlet.war.

    3. If the search result is empty, then we do not have the IBM Portlet API Remote Web Content Viewer, and we can skip this task.

    4. If the search result is not empty, then click ilwwcm-remoterendering-portlet.war > Web Content Management - Remote Content Viewer.

      If we do not use clones of the portlet, the displayed table will contain only a single portlet with the title Remote Web Content Viewer.

  2. If we use the IBM Portlet API Remote Web Content Viewer portlet, choose one of the following methods to deliver the web content after completing the post migration steps:

    • Option 1: If we migrate from a source rendering portal that does not include IBM Web Content Manager to a target rendering portal that does not include IBM Web Content Manager, use the JSR 286 Web Content Viewer and the WSRP support in the portal.

    • Option 2: If we migrate from a source rendering portal that does not include IBM Web Content Manager to a target rendering portal that includes IBM Web Content Manager, the preferred way to display the web content is to locally render it with the JSR 286 Web Content Viewer.

    • Option 3: If the source rendering portal includes IBM Web Content Manager, the target rendering portal will also include IBM Web Content Manager. The preferred way to display the web content is to locally render it with the JSR 286 Web Content Viewer.

    The following table summarizes the preferred options depending on the source and target rendering portal.

    Source rendering portal Target rendering portal Preferred option
    Includes the IBM Web Content Manager Includes the IBM Web Content Manager Option 3: Local web content rendering with JSR 286 Web Content Viewer
    Includes the IBM Web Content Manager Does not include the IBM Web Content Manager Unsupported migration path
    Does not include IBM Web Content Manager Includes the IBM Web Content Manager Option 2: Local web content rendering with JSR 286 Web Content Viewer
    Does not include IBM Web Content Manager Does not include the IBM Web Content Manager Option 1: Remote web content rendering with JSR 286 Web Content Viewer via WSRP


Parent Web Content Manager

Option 1: Remote web content rendering with JSR 286 Web Content Viewer via WSRP

The source rendering portal of the migration does not contain the web content it delivers. Instead the IBM Portlet API Remote Web Content Viewer connects to another portal of the source environment to retrieve the web content. As the target rendering portal does not include IBM Web Content Manager, we must continue displaying web content remotely. To perform remote rendering with IBM Web Content Manager v8.5, configure the target environment to use the JSR 286 Web Content Viewer with WSRP.

The target rendering portal that does not include IBM Web Content Manager and still uses the IBM Portlet API Remote Web Content Viewer becomes the WSRP consumer. It consumes the JSR 286 Web Content Viewer from the target authoring portal that includes IBM Web Content Manager and contains the web content.

  1. To configure remote rendering, follow the instructions at Perform remote rendering with WSRP and the Web Content Viewer.

  2. On the target rendering portal that acts as WSRP consumer:

    1. Add instances of the consumed JSR 286 Web Content Viewer portlet to portal pages containing instances of the IBM Portlet API Remote Web Content Viewer portlet.

    2. Configure the consumed JSR 286 Web Content Viewer portlet instances to match the configuration of the IBM Portlet API Remote Web Content Viewer portlet instances on each of the portal pages.

    3. After replacing all instances of the IBM Portlet API Remote Web Content Viewer portlet and of its portlet clones, uninstall the ilwwcm-remoterendering-portlet.war web module.

    This option has limitations that do not exist when rendering web content locally. See Perform remote rendering with WSRP and the web content viewer.

Options 2 and 3: Local web content rendering with JSR 286 Web Content Viewer

The source rendering portal of the migration does not contain the web content it delivers. Instead the IBM Portlet API Remote Web Content Viewer connects to another portal of the source environment to retrieve the web content. If we choose this option, we will change the web content delivery model from remote rendering to local rendering. After you make the web content libraries available on the target rendering portal, use the JSR 286 Web Content Viewer portlet for local rendering.

  1. To make the web content available on the target rendering portal, syndicate the web content libraries from the target authoring portal to the target rendering portal. See Syndication.

  2. On the target rendering portal:

    1. Check if we installed the JSR 286 Web Content Viewer portlet.

      1. Go to Administration > Portlet Management > Web Modules.

      2. Search for the web module with the file name ilwwcm-localrendering-portlet-jsr.war.

      3. If the search result is empty, install the JSR 286 Web Content Viewer portlet from PortalServer_root/pzn.ext/portlet.localrendering.jsr/localrendering.war/installableApps/ilwwcm-localrendering-portlet-jsr.war.

    2. To convert the instances of the IBM Portlet API Remote Web Content Viewer portlet to the JSR 286 Web Content Viewer portlet, follow the steps given at Converting an IBM API web content viewer to the JSR 286 API.

      If we use clones of the IBM Portlet API Remote Web Content Viewer portlet, we also need to convert their instances.

    3. After replacing all instances of the IBM Portlet API Web Content Viewer portlet and of its portlet clones, uninstall the ilwwcm-localrendering-portlet.war web module.