IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Previous Known Issues

Release notes


Abstract

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

Content


Known issues for previous WebSphere Portal 7.0.0.2 Combined Cumulative Fixes





V7.0.0.2 Combined WP & WCM CF028 (PI10705):


Problem: When using versions earlier than 'Java 6 update 45' or 'Java 7 update 51', a security pop-up dialog or error will be seen every time the WCM FileTransferApplet or Ephox EditLive editor is instantiated.
Solution: It is recommended to upgrade the Java runtime environment level to either 'Java 6 update 45' or 'Java 7 update 51' or later. Please refer to the following URL: http://www.ibm.com/support/docview.wss?uid=swg21663838


Problem: After you enter a number into the number element/component, and then save the content/component more than twice, you will notice that the number field gets populated with some dots, i.e. 123.456.78. If you then click on Save again, you will get the following error:
'Enter a valid number. ( content/component name here)'
Solution: The workaround is to remove the dots and save again.


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: After upgrading to a 7.0.0.2 Cumulative Fix and "Portal 7.0.0.2" theme has been set as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer.
Solution: Perform the following steps to resolve the issue:

  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management'.
  3. On the 'Edit page: Web Content Management' page, extend 'Theme:' drop-down list and select "-----Inherit Parent Theme-----".


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF027 (PI07279):


Problem: When using versions earlier than 'Java 6 update 45' or 'Java 7 update 51', a security pop-up dialog or error will be seen every time the WCM FileTransferApplet or Ephox EditLive editor is instantiated.
Solution: It is recommended to upgrade the Java runtime environment level to either 'Java 6 update 45' or 'Java 7 update 51' or later. Please refer to the following URL: http://www.ibm.com/support/docview.wss?uid=swg21663838


Problem: After you enter a number into the number element/component, and then save the content/component more than twice, you will notice that the number field gets populated with some dots, i.e. 123.456.78. If you then click on Save again, you will get the following error:
'Enter a valid number. ( content/component name here)'
Solution: The workaround is to remove the dots and save again.


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: After upgrading to a 7.0.0.2 Cumulative Fix and "Portal 7.0.0.2" theme has been set as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management'.
  3. On the 'Edit page: Web Content Management' page, extend 'Theme:' drop-down list and select "-----Inherit Parent Theme-----".


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF026 (PM99534):


Problem: After you enter a number into the number element/component, and then save the content/component more than twice, you will notice that the number field gets populated with some dots, i.e. 123.456.78. If you then click on Save again, you will get the following error:
'Enter a valid number. ( content/component name here)'
Solution: The workaround is to remove the dots and save again. This will be fixed in CF27.


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF025 (PM96258):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF024 (PM93215):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF023 (PM89415):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF022 (PM86511):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF021 (PM82594):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF020 (PM78582):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF019 (PM75291):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF018 (PM73172):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF017 (PM70496):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF016 (PM67998):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF015 (PM65284):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF014 (PM63010):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF013 (PM60003):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc.


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF012 (PM58390):


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: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the 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.2 Combined WP & WCM CF011 (PM53921):


Problem: After upgrading to 7.0.0.2 and applying the "Portal 7.0.0.2" theme as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer 9.
Solution: Perform the following steps to resolve the issue:
  1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
  2. Select "Edit Page Properties" for the hidden page named 'Web Content Management' and select the Theme: -----Inherit Parent Theme-----


Problem: WCM Authoring Search not working after an upgrade to 7.0.0.2 from 7.0.0.0
Solution: Perform the following steps to resolve the issue if these steps were not already run after upgrade to 7.0.0.2:
  1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor
  2. Set jcr.textsearch.enabled=true
  3. Change jcr.textsearch.indexdirectory to a different location in the filesystem
  4. Restart your Portal Server.
  5. Create a new library or make changes in existing libraries


Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:

CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;

where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.

Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.


Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.


Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.


Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc


Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.


Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc


Problem: The WPVersionInfo for Portal 7.0.0.2 CF11 will show WCM Version level as 7.0.0.1.
Solution: This will be corrected in the next Portal Cumulative Fix.


Problem: The Portal Search functionality does not work with the 7002 Theme when using Microsoft Windows Internet Explorer 8.
Solution: This will be corrected in the next Portal Cumulative Fix.


Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.


Problem: On a system migrated directly to Portal 7.0.0.2 CF11, the New Page button in Administration->Manage Pages results in : "This portlet is unavailable."
Solution: This will be corrected in the next Portal Cumulative Fix. As an alternative, new pages can be created thru the Actions menu.


Problem: On a system migrated directly to Portal 7.0.0.2 CF11, and when deploying and setting the "7002 Theme" as default, portlets do not display on a new page.
Solution: This will be corrected in the next Portal Cumulative Fix.


Problem: When executing Portal 6.1.x to Portal 7.0.0.2 CF11 Migration, you will see an exception about Class Not Found when running ConfigEngine task upgrade-profile.
Solution: Install APAR PM56244 after 7.0.0.2 CF11 upgrade and before running Migration.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=All&platform=All&function=aparId&apars=PM56244


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.2 where the date of the 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.



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal

Software version:

7.0.0.2

Operating system(s):

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

Software edition:

Enable, Express, Extend, Server

Reference #:

7023912

Modified date:

2014-05-05

Translate my page

Machine Translation

Content navigation