If you use the IBM® Portlet
API Remote Web Content Viewer portlet in your source environment,
you must complete the following task after migration to convert to
the JSR 286 Web Content Viewer.
About this task
The Remote Web Content Viewer portlet that is based on the IBM Portlet API was removed from IBM Web Content Manager Version
8.5 and is no longer supported. The migration process transfers the
portlet and the portlet instances from your portal pages to the target
environment. After migration, you must replace the IBM Portlet API Remote Web Content Viewer portlet
with the JSR 286 Web Content Viewer portlet.Procedure
- Check if you installed the IBM Portlet
API Web Content Viewer portlet and identify potential portlet clones.
- Click the Administration menu icon. Then, click .
- Search for the web module with the file name ilwwcm-remoterendering-portlet.war.
- If the search result is empty, then you do not have
the IBM Portlet API Remote Web
Content Viewer, and you can skip this task.
- If the search result is not empty, then click .
Note: If you do not use clones of the portlet, the displayed
table will contain only a single portlet with the title Remote
Web Content Viewer.
- If you use the IBM Portlet
API Remote Web Content Viewer portlet, choose one of the following
methods to deliver your web content after completing the post migration
steps:
- Option 1: If you 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, you must
use the JSR 286 Web Content Viewer and the WSRP support in the portal.
- Option 2: If you 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 your web content is to locally render it with the JSR 286
Web Content Viewer.
- Option 3: If your source rendering portal includes IBM Web Content Manager, the target
rendering portal will also include IBM Web
Content Manager. The preferred way to display your 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.
Table 1. Preferred
way to display web content in your portal after migrationSource 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 |