IBM WebSphere Portal 6.1.0.6/6.1.5.3 Known Runtime Issues

Content

---

Known issues for Runtime WebSphere Portal 6.1.0.6/6.1.5.3

Problem: Application of the fix pack updates the Domino Web Access portlet with the Privileged User role for All Authenticated Users. While this is the default access control for the portlet, any administrator who had previously removed such access will have their efforts reversed. The effect of such setting is creation of implicit private pages for each user who attempts to personalize the portlet.
Solution: Manually remove All Authenticated Users from the Privileged User role on the Domino Web Access portlet via the administration portlets or via XMLAccess. This will prevent any further personalization and creation of private pages. To address the private pages already in the system, delete them via XMLAccess.

Problem: Pre-rendering service could fail to initialize following upgrade to 6.1.0.6.
Solution: Run the following ConfigEngine task to update and enable pre-rendering service.
./ConfigEngine.sh update-wcm -DWasPassword=<password> -DPortalAdminPwd=<password>

Problem: Ephox application may not be deployed on the server when upgrading to 6.1.0.6
Solution: The issue can be resolved by running the tasks outlined in the following technote.
https://www.ibm.com/support/docview.wss?uid=swg21469874

Problem: For 6.1.5.3, WCI feeds are not displayed in the feed configuration portlet when the feature pack is applied following an upgrade path that does not involve 6.1.0.3. For example, if a customer upgrades from 6.1.0.2 to 6.1.0.6 and then move on to 6.1.5.3.
Solution: Run the following ConfigEngine task to create the required WAS variables which will resolve the issue.
./ConfigEngine.sh ce-action-create-was-variable-wcm-schema-wp6103 -DWasPassword=<password> -DPortalAdminPwd=<password>

Problem: For 6.1.5.3, after changing user repositories, or the administrator user (via the task ConfigEngine task wp-change-portal-admin-user) the Portal administrator no longer has access to the Web Content Integrator Servlet user interface.
Solution: Run the following ConfigEngine task to refresh the security on the Web Content Integrator Servlet user interface.
./ConfigEngine.sh update-wcm-fp615 -DWasPassword=<password> -DPortalAdminPwd=<password>

Problem: For 6.1.5.3, Portal Administrator users are not automatically granted access to the Web Content Integrator (WCI) Servlet. Users accessing the WCI servlet will receive a 403 (not authorized) response.
Solution: Access can be manually granted to the wcmadmin role on the FeedService application through the WAS Admin console.

Problem: After upgrading to 6.1.0.6, when configuring lookaside, ConfigEngine.sh (or bat) wp-configure-la-complete, the following exception may occur:

[wplc-create-la-repository] trimSpaces= *** NOT_SPECIFIED ***
Result: [com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5020E Could not connect to the jdbc:oracle:thin:@hostname.yourcompany.com:1521:wps6102 repository using properties: [dbAdminPassword=****],[dataSourceName=jdbc/vmmladbDS],[dbURL=jdbc:oracle:thin:@hostname.yourcompany.com:1521:wps6102],[databaseType=oracle],[entityRetrievalLimit=50],[JDBCDriverClass=oracle.jdbc.driver.OracleDriver],[dbAdminId=lauser],.]
[wplc-create-la-repository] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5020E Could not connect to the jdbc:oracle:thin:@hostname.yourcompany.com:1521:wps6102 repository using properties: [dbAdminPassword=****],[dataSourceName=jdbc/vmmladbDS],[dbURL=jdbc:oracle:thin:@hostname.yourcompany.com:1521:wps6102],[databaseType=oracle],[entityRetrievalLimit=50],[JDBCDriverClass=oracle.jdbc.driver.OracleDriver],[dbAdminId=lauser],
Solution:

1. Stop the nodeagent.
2. Stop the Deployment Manager.
3. Start the Deployment Manager.
4. Start the nodeagent.
5. Clean up your property extension database user registry and then rerun the wp-configure-la-complete task. See Re-running the wp-configure-la-complete task fails page for more information on re-running the wp-configure-la-complete task.

Problem: After upgrading to Portal 6.1.0.6, the default theme changed to the "Portal" theme. This may for instance happen when a Portal 6.0.1.x is migrated to a Portal 6.1.0.x which has a default theme that is not the "Portal" theme and then the Portal 6.1.0.x is upgraded to Portal 6.1.0.6.
Solution: Goto "Administration -> Themes and Skins" and change back to your previous theme

Problem: If you are using WebSphere Portal 6.1.5.3 and use the Spaces functionality (Composite Application containing Mashup pages) and after the application of WebSphere Portal 6.1.5.3 the Create Space button may not show up.
Solution:
If you did not customize the file contextmenu.xml run the following config task (NOTE for i5/OS platforms put "MMImportFileProviderName=WP Mashup ContextMenu" in the wkplc.properties file and run the config task without the -DMMImportFileProviderName="WP Mashup ContextMenu" ):
ConfigEngine.sh|bat import-config-file -DMMImportFile="$WP_HOME/base/wp.mmi.deploy/config/binaries/contextmenu.xml" -DMMImportFilePropertyName="contextmenu.xml" -DMMImportFileProviderName="WP Mashup ContextMenu"

If you customized the file contextmenu.xml you will need to merge your changes and the changes that are part of the fix pack. The file additions are attached with this technote in the file named contextmenu.xml. Once you merged the changes into your customized the file execute the following config task (NOTE for i5/OS platforms put "MMImportFileProviderName=WP Mashup ContextMenu" in the wkplc.properties file and run the config task without the -DMMImportFileProviderName="WP Mashup ContextMenu" ):
ConfigEngine.sh import-config-file -DMMImportFile="<your temporary location>/contextmenu.xml" -DMMImportFilePropertyName="contextmenu.xml" -DMMImportFileProviderName="WP Mashup ContextMenu"

Problem: Slow responses in the People Picker application
Solution: Starting with 6.1.0.3 the People Picker application searches not only for the cn attribute but additionally for the description, viewIdentifiers and displayName attribute. In configurations with slow LDAPs this might cause slower responses in the People Picker application.

Problem: Opera® Web browser only: Enter key cannot focus on the Search button if some other button lies above it.
Solution: This is a current limitation of the product.

Problem: Spellchecker function does not work in Common PIM Portlet Mail when used through Apple Safari browser.
Solution: This is a known issue in this release.

Problem: After migration from wp60x to wp610x, the out of the box non admin pages are lost in wp610x.
Solution: Any out of the box non admin pages will be deleted as part of migration.If you want to use these pages,you have to re-add these pages and portlets on them.

Problem: When using Portal via webserver, you may not be able to change portlet position via drag and drop in a web2theme page.
Solution: The webserver may not allow PUT and DELETE requests, so you need to configure HTTP tunneling. In Portal admin console, Navigate to Resources->Resource Environment->Resource Environment Providers->WP_ConfigService->Custom properties. Add a new property named "x-method-override.enabled" and set the value to "true". Restart WAS and Portal. Refer to
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v6101/dev/uprof_rest_wp_tnlhttp.html for more information.

Problem: When PortalServer is installed in HP-UX machine with non-root user, Warning messages occurs in Portal logs when Configure Webserver:
prefs W Could not lock User prefs. Unix error code 2.
prefs W Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
Solution: Create this directory /home/<non-root username> manually,make sure that non-root user owns this directory.

Problem: When Portal is configured with Microsoft ADAM 2008 federated LDAP, and use cn as personAccountRdnProperties. You may get an error and fail to update user first name and last name on Edit User profile portlet.
com.ibm.portal.puma.UpdateReadOnlyAttributeException: EJPSG0044E: Updating the rdn attribute cn is not supported.
Solution: Login WAS Admin console, under Resources > Resource Environment > Resource Environment Providers. Add a property in WP PumaStoreService: store.puma_default.user.fbadefault.filter=cn. Then restart Portal Server.

Problem: If Portal 6.1.0.x is configured for searching federation to a remote Lotus Quickr server after the upgrade to Portal 6.1.0.6/6.1.5.3 some configuration steps need to be redone.
Solution: Steps 1e through 1i from "Search across Lotus Quickr Server" section from the 6.1.x InfoCenter must be redone.

Problem: In 6.1.0.x cluster, there are some portal exceptions regarding PMI modules under the <Profile_root>\logs\ffdc
[8/11/09 16:14:08:031 CST] FFDC Exception:java.util.MissingResourceException SourceId:com.ibm.ejs.sm.client.ui.NLS.getString ProbeId:353 Reporter:com.ibm.ejs.sm.client.ui.NLS@6d146d14
java.util.MissingResourceException: Can't find resource for bundle com.ibm.ws.pmi.properties.PMIText, key Hits
at java.util.MissingResourceException.<init>(MissingResourceException.java:45)
at java.util.ResourceBundle.getObject(ResourceBundle.java:395)
at java.util.ResourceBundle.getString(ResourceBundle.java:416)
at com.ibm.ejs.sm.client.ui.NLS.getString(NLS.java:353)
at com.ibm.ejs.sm.client.ui.NLS.getString(NLS.java:377)
at com.ibm.ws.pmi.stat.StatsConfigHelper.translate(StatsConfigHelper.java:472)
at com.ibm.ws.pmi.stat.StatsConfigHelper.translateAndCache(StatsConfigHelper.java:510)
at com.ibm.ws.pmi.server.ModuleConfigParser.loadDescriptor(ModuleConfigParser.java:247)
at com.ibm.ws.pmi.server.ModuleConfigParser.loadDescriptor(ModuleConfigParser.java:117)
at com.ibm.ws.pmi.server.ModuleConfigParser.parse(ModuleConfigParser.java:112)
at com.ibm.websphere.pmi.PerfModules$1.run(PerfModules.java:326)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.websphere.pmi.PerfModules.getConfigFromXMLFile(PerfModules.java:320)
at com.ibm.websphere.pmi.PerfModules.getConfig(PerfModules.java:160)
at com.ibm.websphere.pmi.server.PmiAbstractModule.<init>(PmiAbstractModule.java:129)
at com.ibm.websphere.pmi.server.PmiAbstractModule.<init>(PmiAbstractModule.java:107)
at com.ibm.websphere.pmi.WpsModule.<init>(WpsModule.java:70)
at com.ibm.wps.services.pmi.PmiServiceImpl.init(PmiServiceImpl.java:57)
at com.ibm.wps.services.Service.init(Service.java:107)
at com.ibm.wps.services.Service.init(Service.java:83)
at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:365)
at com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:271)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:173)
at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:115)
at com.ibm.wps.engine.Servlet.init(Servlet.java:248)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:333)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:165)
Solution: These exceptions could be ignored.

Problem: When federating an additional node into DM, in case that the property RegistrySynchronized was set to false, the task cluster-node-config-pre-federation will fail since local registry was out of synchronization.
Solution: Manually set the value of property RegistrySynchronized to true.
Then re-run the task again.

Problem: If you stop all java threads, including DM, nodeagents and portal server.Then restart DM, nodeagents and portal server.Check the ffdc log, there will be some exceptions:
Exception:com.ibm.websphere.management.exception.ConnectorNotAvailableException SourceId:com.ibm.ws.management.event.DownstreamServerManager.QueueConsumerThread.updateServers ProbeId:1303 Reporter:com.ibm.ws.management.event.DownstreamServerManager$QueueConsumerThread@41dc41dc
com.ibm.websphere.management.exception.ConnectorNotAvailableException
at com.ibm.ws.management.discovery.ServerInfo.getAdminClient(ServerInfo.java:218)
at com.ibm.ws.management.event.DownstreamServerManager.getRemoteProxy(DownstreamServerManager.java:289)
Solution: These exceptions could be ignored.

Problem: Task ./ConfigEngine.sh modify-servlet-path is not executable as a NON-ROOT user after upgrade.
Solution: If running the ./ConfigEngine.sh modify-servlet-path task as a NON-ROOT user it's necessary to change the PortalServer directories permission to 750. This can be done using the unix chmod command: chmod -R 750 <installlocation>/*
Example: chmod -R 750 /opt/IBM/PortalServer/*

Problem: After downgrade of Portal from 6.1.0.6 to 6.1.0.1 and try to create a new page, you may encounter the error "This portlet is temporarily disabled" and couple with the exception in SystemOut.log
[11/12/09 19:53:39:029 CST] 0000005b servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /WEB-INF/properties/html/addPlaceComposition.jsp in application PA_Properties. Exception created : java.lang.IllegalArgumentException: parentNodeID must not be null. Use getCreateSharedNodePermissions(DatabaseDomain domain) instead at com.ibm.wps.ac.impl.NodePermissionFactoryImpl.getCreateSharedNodePermissions(NodePermissionFactoryImpl.java:70)
Solution: Update Properties.war web module with <WPSInstallationDir>/ap/wp.ap.properties/installableApps/Properties.war by using Web Modules portlet or xmlAccess

Problem: After HTTP session expires, a login window will be prompted for user's credentials due to user's interaction with Resource Manager portlet on the Administration Site Management page.
Solution: This is a current limitation of the product.

Problem: If Profile Management Portlet is deployed on a new page, non admin user will see this error message
Users can not be enrolled in this portal, or you do not have permission to perform user enrollment.
Solution: The problem is happened on Portal with WAS 7.0.0.x only. Currently it's a limitation.


Problem: An error occurs when attempting to add a widget to the WebSphere Portal server through the mashup hub. If you experience this error: "An error occurred when opening the catalog. Check to make sure the URL to the WebSphere Portal server is correct. Also, make sure that your user ID and password are correct"
Solution: This error occurs because the 'Enable trust association' setting is not enabled. Run the following command:

• Windows: ConfigEngine.bat enable-http-basic-auth-tai-sitemgmt
• Unix/Linux: ./ConfigEngine.sh enable-http-basic-auth-tai-sitemgmt
• i5/OS: ConfigEngine.sh enable-http-basic-auth-tai-sitemgmt
  

In the admin console verify the following: Go to Security->Global security->Web and SIP security->Trust association. The checkbox for 'Enable trust association' is selected.