WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Troubleshoot Personalization

This section contains information that can assist you in preventing, identifying, and correcting problems related to IBM® WebSphere® Portal Express. For information related to specific components, see the appropriate troubleshooting topic. For troubleshooting installation problems, refer to the pzninstall.log file in the temp directory. For uninstallation, refer to temp/pznuninstall.log.

 

Note for Windows users: The temp directory is typically located in a hidden directory named Documents and Settings\user\Local Settings. For example, C:\Documents and Settings\Administrator\Local Settings\Temp. You may need to set your folder options appropriately in order to view hidden files and directories.

 

Problem: MovieSite installation fails on LikeMinds database

In order to install MovieSite, have an unused LikeMinds database. Once LikeMinds is installed and running, trying to install MovieSite will return sql errors because users with conflicting IDs will already be present in the database.

 

Solution: Create another LikeMinds database to use MovieSite with, or remove all users, items, and ratings from the LikeMinds database on which you are attempting to install MovieSite.

 

Problem: LikeMinds does not run with j2ee 1.2

By default, LikeMinds code uses the datasource named jdbc/lmDS to connect to its database. This is a 5.0 datasource, and cannot be used by j2ee 1.2 applications.

 

Solution: In order to use LikeMinds with a j2ee 1.2 application, create a 4.0 datasource pointing to the LikeMinds database, and set the system property lm.db.dsname to the name of the 4.0 datasource.

 

Problem: The menus in the Personalization Navigator portlet do not appear when their menu launcher is clicked

 

Solution: If you click the New or More Actions menu launcher and the menu does not appear, you might need to click your primary mouse button somewhere else in the page (other than the menu launchers) before clicking on the menu again. Clicking the left mouse button on any non-link or non-button element (such as empty areas of the browser window or in regular text) will reactivate the menu. This only occurs when one of the menus is open and the other menu launcher is clicked.

 

Problem: Security message is repeatedly displayed when creating or editing a rule

When SSL is enabled in Internet Explorer, creating a new rule or editing an existing rule may display a message which says "This page contains both secure and nonsecure items. Do you want to display the nonsecure items?" This is a known defect with Internet Explorer that falsely indicates the page is not secure.

 

Solution: There are two possible solutions.

 

Problem: Personalization will no longer open documents from Document Manager

If the context root of the server running WebSphere Portal Express is changed after any user has visited Document Manager, a Document Manager administrator must re-enable the ability to open Document Manager documents from Personalization.

 

Solution: The Document Manager administrator must perform the following steps to re-enable linking:

  1. Enter the Document Manager configuration mode for the document library containing the documents you wish to link to. Disable Search Center registration and submit your changes.

  2. Enter the configuration mode again and re-enable Search Center registration.

 

Problem: A rule does not return the correct resources

A rule that uses the Folder path or Name attribute of a CmResource does not always return the correct resources. Specifically, if the rule contains a mixture of OR and AND operations with Folder path or Name attributes, incorrect results may be returned. The problem will be fixed in a future release.

Using the AND operator between Folder path or Name will either result in no results, or in some cases cause an exception to be thrown. Since an object can only have one name and one path, an object can never be in one path AND another path or have one name AND another name.

 

Problem: LikeMinds recommendation rules do not return instances of CmResource

Running LikeMinds recommendations rules to return instances of CmResource is not supported in this release. Support will be provided in a future release.

 

Problem: There are broken links in Personalization

In many places in the user interface, Personalization will let you know when there are broken links. For instance, when a rule mapping references a rule that has been deleted, a red X displays next to the rule name when viewing the rule mapping. In some places, such as inside of a rule, references which are broken do not currently display the broken link indicator. When changing the name of an artifact, or when changing the session key of an application object, it may be necessary to edit all artifacts which reference that object in order to correct the links.

 

Solution: In some cases, as when an artifact is simply moved, opening the editor and resaving is all you will need to do to fix a broken link. In other cases, such as inside the rule editor or when an item is deleted, you may need to bring up the appropriate sub-dialog, such as the resource.attribute dialog, and reselect the appropriate item.

 

Problem: Personalization Navigator is empty

This issue might be a problem on Linux platforms.

 

Solution: The number of file handles might need to be increased.

  1. Open a command prompt and enter ulimit -n 4096.

  2. Stop and restart WebSphere Portal Express .

 

Problem: Personalization rule events may not fire in the Rational Unit Test Environment.

When using the Portal Unit Test Environment, Personalization rule events may fail to fire.

 

Solution: There may be an error in the logs for the test environment: 

[3/7/05 13:33:00:174 CST] 5b171091 EJBContainerI I WSVR0207I: Preparing to start EJB jar: 
	pznscheduler.jar 
[3/7/05 13:33:00:199 CST] 5b171091 BeanMetaData  E CNTR0075E: The user-provided class 
	"com.ibm.websphere.startupservice.EJSRemoteStatelessPznSchedulerInitializerBeanHome_
   92051795" 
	needed by the EnterpriseBean could not be found or loaded. 
[3/7/05 13:33:00:212 CST] 5b171091 EJBContainerI E WSVR0209E: Unable to prepare EJB jar 
	pznscheduler.jar [class com.ibm.ws.runtime.component.DeployedModuleImpl], enterprise 
	bean com.ibm.etools.ejb.impl.SessionImpl(PznSchedulerInitializerBean) (transactionType: 
	Bean, sessionType: Stateless)  
java.lang.NoClassDefFoundError: Error while defining class: 
	com.ibm.websphere.startupservice.EJSRemoteStatelessPznSchedulerInitializerBeanHome_92051795
This error indicates that the class: com.ibm.websphere.startupservice.AppStartUpHome could not be located while defining the class: 

com.ibm.websphere.startupservice.EJSRemoteStatelessPznSchedulerInitializerBeanHome_92051795
. This is often caused by having the class at a higher point in the classloader hierarchy.

To eliminate the error, the pznscheduler.ear may be uninstalled.

 

Problem: Smart delete does not work for folders

If a folder is deleted on the authoring server using the smart delete mode, the same folder in the publish server is not deleted. The children of the folder are deleted on the publish server, unless they are sub-folders.

 

Solution: This is a permanent restriction.

 

Problem: Personalization authoring portlets do not support Parallel Portlet Rendering

Using Parallel Portlet Rendering on the Personalization authoring portletsPersonalization Navigator and Personalization Editor can generate database-related exceptions because they do not support Parallel Portlet Rendering. You may get an exception similar to the following: 

com.ibm.icm.ci.data.impl.dautils.PLockNode _executeJCRLock DSRA9110E: Connection is closed.
com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Connection is closed.
.
.
.
com.ibm.websphere.personalization.ui.managers.PznAuthoringRepositoryManager.
isLocked(PznAuthoringRepositoryManager.java:393)com.ibm.websphere.personalization.
ui.managers.AbstractArtifactManager.isLocked (AbstractArtifactManager.java:370)
com.ibm.websphere.personalization.ui.details.views.item.PznArtifactItemHandler.canEdit (PznArtifactItemHandler.java:156)

 

Solution: Disable Parallel Portlet Rendering for these two portlets. This should not impact performance of the Personalization runtime portlet Personalized List. Parallel Portlet Rendering is intended to be used for runtime portlets. Perform the following steps to disable Parallel Portlet Rendering for the Personalization Navigator and Personalization Editor:

  1. Select Portal Administration > Portlet Management > Portlets.

  2. Search for the Personalization Navigator and Personalization Editor portlets.

  3. For each, select the Configure portlet icon.

  4. Ensure the Enable parallel rendering check box is unchecked.

  5. Click OK to save your settings.

 

Parent topic:

Search the product documentation for a solution