If you are planning to migrate to WebSphere Portal 7.0 or higher, it is
very likely that you may not be able to view the WCM out of box page
or the WCM Authoring portlet. In some cases the user interface of WCM
authoring portlet might not work as expected and you might end up
getting the following exception in logs.
If you see the above exception, it's time to re-enable some of the WCM features manually post migration because he migration process sometimes disable some new out-of-the-box features if the feature did not exist in the previous version or if it was updated. To fix this issue, you have to re-enable the affected features manually after migration.
Navigate to folder \wp_profile_root\Config Engine directory and run the following config engine task.
Note: For clustered environment, run this task on the primary node of the server.
Few points to remember:
IWKAP0009E: Servlet not enabled
If you see the above exception, it's time to re-enable some of the WCM features manually post migration because he migration process sometimes disable some new out-of-the-box features if the feature did not exist in the previous version or if it was updated. To fix this issue, you have to re-enable the affected features manually after migration.
Navigate to folder \wp_profile_root\Config Engine directory and run the following config engine task.
Note: For clustered environment, run this task on the primary node of the server.
Windows:
ConfigEngine.bat install-wcm-hidden-authoring-page -DWasPassword=<password>
UNIX:
./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=<password>
Few points to remember:
- Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.
- Deploy the hidden Portal page on which the reserved authoring portlet is by default installed.
No comments:
Post a Comment