Troubleshoot portlets

 

+

Search Tips   |   Advanced Search

 

This section contains information that can assist you in preventing, identifying, and correcting problems related to IBM WebSphere Portal. For information related to specific components, see the appropriate troubleshooting topic.

• Problem: European comma format for numbers not available in Retirement Planner

• Problem: IBM NetMeeting portlet not available if the Microsoft NetMeeting application not already installed

• Problem: Configure proxy for MarketWatch portlets

• Problem: Export XML does not work when "Popup Block" is active (Netscape only)

• Problem: Click-to-Action menu shown in English, not Chinese

• Problem: The administration portlets do not officially support the browser 'Back' or 'Refresh' functions.

• Limitation: The properties portlet does not list all shareable pages.

• Limitation: Privileged user cannot set page properties or Personalization rules.

• Problem: Buttons in Adminstration portlets may not function.

• Problem: Formatting and JavaScript problems occur in rendered Portal page

 

Problem: European comma format for numbers not available in Retirement Planner

Retirement Planner only allows users to use the format x.xx when entering non-whole number values.

 

Problem: IBM NetMeeting portlet not available if the Microsoft NetMeeting application not already installed

If you are using Internet Explorer 5.5 on Windows, and Microsoft NetMeeting is not already installed, the NetMeeting portlet will not be available.

Solution: Upgrade to Internet Explorer 6 or install the Microsoft NetMeeting application (as provided by Microsoft Corporation) on the machine.

 

Problem: Configure proxy for MarketWatch portlets

The MarketWatch portlets...

• My News
• My Weather
• My Stocks

...assume that you have direct access to the Internet to retrieve content for rendering in the portlets. If access is only possible through a proxy, then the proxy must be configured in the portlet by modifying its web.xml file.

Solution: There are four context level parameters in web.xml, and by default they are all empty:

<context-param>
     <param-name>proxyHost</param-name>
     <param-value></param-value>
  </context-param>

  <context-param>
     <param-name>proxyPort</param-name>
     <param-value></param-value>
  </context-param>

  <context-param>
     <param-name>proxyUserName</param-name>
     <param-value></param-value>
  </context-param>

  <context-param>
     <param-name>proxyPassword</param-name>
     <param-value></param-value>
  </context-param>

The values for these parameters should be:

proxyHost	Host name of proxy server (dns name or static IP address).
proxyPort	Proxy server port, such as 8080.
proxyUserName proxyPassword	If the proxy server requires authentication, specify the user ID and password for the proxyUserName and proxyPassword parameters, respectively.

 

Problem: Export XML does not work when "Popup Block" is active (Netscape only)

In Netscape/Mozilla, when "Popup Block" is active, if you try to use the "Export XML" function within the Manage Pages portlet, nothing happens. An "Export successful" message is displayed though no export has occurred. With Popup-Blocker disabled, pages can be exported normally.

Solution: In order to disable "Popup Block" in Netscape/Mozilla, perform the following steps:

1. Open Preferences window by going to Edit > Preferences.

2. Select Privacy & Security > Popup Windows.

3. Un-check Block unrequested popup windows.

4. Click OK.

 

Problem: Click-to-Action menu shown in English, not Chinese

After configuring the Click-to-Action menu of the JDBC portlet in English, when you change the language of the browser to zh_CH, the menu still displays in English.

Solution: Replace the Click-to-Action menu items with local language strings.

 

Problem: The administration portlets do not officially support the browser 'Back' or 'Refresh' functions.

For a listing and description of the administration portlets, refer to Portal administration portlets.

 

Limitation: The properties portlet does not list all shareable pages.

The list of shareable pages displayed by the Properties portlet is limited to those pages that the user can navigate to. As a result, a user might not be able to create explicitly derived pages from some shareable pages.

 

Limitation: Privileged user cannot set page properties or Personalization rules.

A user must have at least Editor privileges on a page to be able to edit the properties on that page. Privileged users will not be able to edit a page's properties or edit personalization rules, because Personalization rules are part of a page's properties.

 

Problem: Buttons in Adminstration portlets may not function.

Solution:Enable scripting in Microsoft Internet Explorer using the following steps:

1. Select the Tools menu.

2. Select Internet Options.

3. Select the Security tab.

4. Click the Custom level button.

5. Enable the entire Scripting section.

 

Problem: Formatting and JavaScript problems occur in rendered Portal page

Formatting problems and JavaScript console errors and warnings occur when a page is rendering. Formatting problems may include such things as excess white space, alignment issues, and truncation. These problems may occur due to inconsistencies in the way different browsers render markup as well as differences due to the DocType specified for the page. This can be a particular problem when a "strict" DocType is specified but the markup is created based on an older "transitional" ("quirks" mode) DocType.

Solution: Ensure that theme and portlet output are consistent with the DocType specified by the theme the page uses. Either set the theme to use a different DocType or update the rendered markup to be compatible with the selected DocType.

 

---