IBM WebSphere Portal 7.0.0.1 Combined Cumulative Fix Previous Known Issues

Release notes


Abstract

This document contains a list of known issues for previous WebSphere Portal 7.0.0.1 Combined Cumulative Fixes. For current known issues for the latest WebSphere Portal 7.0.0.1 Combined Cumulative Fix, please see the WebSphere Portal 7.0.0.1 Combined Cumulative Fix Readme.

Content


Known issues for previous WebSphere Portal 7.0.0.1 Combined Cumulative Fixes








V7.0.0.1 Combined WP & WCM CF020 (PM78581):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.






V7.0.0.1 Combined WP & WCM CF019 (PM75289):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.







V7.0.0.1 Combined WP & WCM CF018 (PM73171):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.





V7.0.0.1 Combined WP & WCM CF017 (PM70495):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.




V7.0.0.1 Combined WP & WCM CF016 (PM67997):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.







V7.0.0.1 Combined WP & WCM CF015 (PM65283):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.







V7.0.0.1 Combined WP & WCM CF014 (PM63009):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.







V7.0.0.1 Combined WP & WCM CF013 (PM60002):


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.


Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.






V7.0.0.1 Combined WP & WCM CF012 (PM58389):


Problem: If using Microsoft Windows Internet Explorer 8, moving a page before the one prior to it in Customize shelf fails with an error:
BMWMB0075E: A new position is required to reorder the page.
Solution: A fix for this issue is scheduled to be included in a future Combined CF. The workaround would be to reorder the page in "Manage Pages" portlet


Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.






V7.0.0.1 Combined WP & WCM CF011 (PM53918):


Problem: The Sitemap portlet is not available after upgrade to Cumulative Fix 11.
Solution: This will be corrected in the next Portal Cumulative Fix.
The Site map portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the sitemap.war. Use the PortalServer/ap/wp.ap.sitemap/installableApps/sitemap.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.






V7.0.0.1 Combined WP & WCM CF010 (PM51141):

Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.






V7.0.0.1 Combined WP & WCM CF009 (PM49013):

Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.





V7.0.0.1 Combined WP & WCM CF008 (PM46623):

Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After migrating from Portal 6.1.x.x to Portal 7.0.0.1 CF006, accessing the migrated Portal fails with an exception being logged in the Portal SystemOut.log file similar to the one below:
---
Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
...
Caused by: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
at com.ibm._jsp._Default._jspx_meth_r_url_1(_Default.java:3324)
at com.ibm._jsp._Default._jspService(_Default.java:810)
... 73 more
---
Solution: Install PM43528 to re-establish access to the migrated Portal. Alternatively, you can re-compile your theme's JSPs.


Problem: After uninstall of combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.





V7.0.0.1 Combined WP & WCM CF007 (PM44212):

Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After migrating from Portal 6.1.x.x to Portal 7.0.0.1 CF006, accessing the migrated Portal fails with an exception being logged in the Portal SystemOut.log file similar to the one below:
---
Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
...
Caused by: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
at com.ibm._jsp._Default._jspx_meth_r_url_1(_Default.java:3324)
at com.ibm._jsp._Default._jspService(_Default.java:810)
... 73 more
---
Solution: Install PM43528 to re-establish access to the migrated Portal. Alternatively, you can re-compile your theme's JSPs.


Problem: After uninstall of combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.





V7.0.0.1 Combined WP & WCM CF006 (PM41442):

Problem: The paging navigation component does not render during the pre-rendering.
Solution: A fix for this issue is scheduled to be included in a future Combined CF.


Problem: The WCM CF17 was integrated into the combined cumulative fix CF006. This CF does not contain the fix for PM32581 which addresses a NullPointerException issue.
Solution: The issue is scheduled to be fixed in WCM CF19.


Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


Problem: After migrating from Portal 6.1.x.x to Portal 7.0.0.1 CF006, accessing the migrated Portal fails with an exception being logged in the Portal SystemOut.log file similar to the one below:
---
Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
...
Caused by: java.lang.NoSuchMethodError: com/ibm/wps/resolver/tags/ResolvedUrlTag.setUri(Ljava/lang/String;)V
at com.ibm._jsp._Default._jspx_meth_r_url_1(_Default.java:3324)
at com.ibm._jsp._Default._jspService(_Default.java:810)
... 73 more
---
Solution: Install PM43528 to re-establish access to the migrated Portal. Alternatively, you can re-compile your theme's JSPs.


Problem: After uninstall of combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.





V7.0.0.1 Combined WP & WCM CF005 (PM38934):

Problem: The paging navigation component does not render during the pre-rendering.
Solution: A fix for this issue is scheduled to be included in a future Combined CF.

Problem: The WCM CF14 was integrated into the combined cumulative fix CF005. The WCM CF13 introduced a performance regression with APAR PM32581. The APAR PM32581 was therefore removed from the combined cumulative fix CF005. The problem fixed by PM32581 is therefore evident again after CF005.
Solution
: A fix for both the performance issue and the issue fixed by PM32581 is scheduled to be included in a future Combined CF.

Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.

Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.

Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.




V7.0.0.1 Combined WP & WCM CF004 (PM37009):

Problem: The paging navigation component does not render during the pre-rendering.
Solution: A fix for this issue is scheduled to be included in a future Combined CF.

Problem: The WCM CF14 was integrated into the combined cumulative fix CF004. The previous WCM CF13 introduced a performance regression with APAR PM32581. The APAR PM32581 was therefore removed from the combined cumulative fix CF004. The problem fixed by PM32581 is therefore evident again after CF004.
Solution
: A fix for both the performance issue and the issue fixed by PM32581 is scheduled to be included in a future Combined CF.

Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.

Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.

Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.





V7.0.0.1 Combined WP & WCM CF003 (PM35462):


Problem: The WCM CF13 was integrated into the combined cumulative fix CF003. The WCM CF13 introduced a performance regression with APAR PM32581. The APAR PM32581 was therefore removed from the combined cumulative fix CF003. The problem fixed by PM32581 is therefore evident again after CF003.
Solution
: You can install WCM CF14 on top of the combined cumulative fix CF003 - it contains PM32581. This will introduce the performance regression though. A fix for both the performance issue and the issue fixed by PM32581 is scheduled to be included in a future Combined CF.

Problem: WCM items scheduled to publish or expire on a future date fail to do so after migration from 6.0 to 7.0
Solution
: A fix for this issue is scheduled to be included in a future Combined CF.

Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.

Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.

Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.





V7.0.0.1 Combined WP & WCM CF002 (PM34759):


Problem: When an authoring tools component is rendered on a non-JSR286 local rendering portlet and a content with rich text element is edited, the "browse content" button in the "insert link" dialog will be greyed out (disabled)
Solution: A fix for this issue is scheduled to be included in WCM CF13 for 7.0.0.1.

Problem: WCM items scheduled to publish or expire on a future date fail to do so after migration from 6.0 to 7.0
Solution
: A fix for this issue is scheduled to be included in a future Combined CF.

Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution
: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.

Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.

Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.





Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

7.0.0.1

Operating system(s):

AIX, IBM i, Linux, Solaris, Windows, z/OS

Software edition:

Enable, Express, Extend, Server

Reference #:

7021504

Modified date:

2013-02-12

Translate my page

Machine Translation

Content navigation