Troubleshoot Personalization

This section contains information that can assist you in preventing, identifying, and correcting problems related to WebSphere Portal. 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: Drop-down menus are not active when using the Opera browser.

In order for the drop-down menu function in Personalization to be supported by the Opera browser, verify the browser identifies itself as Opera.

Solution: Set your browser to Opera by going to Tools > Quick Preferences > Identify as Opera.

 

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.

  • You may choose yes or no. Neither choice will send sensitive information over a connection which is not secure. If you choose no, you may momentarily see an error page before the rule editor is displayed.
  • You can disable the warning by completing the following steps (in Internet Explorer):

    1. Select Tools from the menu.
    2. Under Tools, select Internet Options.
    3. On the Security tab, determine the appropriate zone for your WebSphere Portal site. Consult the Internet Explorer documentation for more information about how websites are classified into zones.
    4. Select the appropriate zone, and then click the Custom Level button.
    5. In the Settings dialog, scroll down until you see the Miscellaneous category. Under the "Display mixed content" option, select the radio button Enable.
    6. Click OK to save your changes. The warning will no longer be displayed.

 

Problem: Personalization will no longer open documents from Document Manager

If the context root of the server running WebSphere Portal 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: The Order By rule element does not work for some DB2 Content Manager Runtime Edition resource attributes

For the Document Resource Collection provided with Personalization and for all DB2 Content Manager Runtime Edition resources, the properties Name, Folder Object, and Folder Path cannot be used in an Order By clause in a Select, Recommendation, or Binding rule.

 

Problem: LikeMinds recommendation rules do not return instances of CmResource

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

 

See also

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.