WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

 

Troubleshooting Web 2.0 issues

Learn how to troubleshoot and debug issues that result from using the portal Web 2.0 theme.

As the CSA aggregator performs on the client rather than on the server, troubleshooting problems with the portal Web 2 theme requires a different approach than with traditional themes. If the error occurred on the server, an exception can be written to the server log. An error on the client is logged on the client. In order to view errors logged on the client proceed by the following steps: Load a portal page with the PortalWeb2 theme. 3. Once the page has completed loading, type the following into the browser's address bar and hit enter: javascript:toggleDebugForm(); This will display a form at the bottom of the page which will allow you to then launch the debug console in a new window. The debug console will now log debug/trace statements which will help identify the problem. 3rd party Javascript debugging tools are an invaluable resource in troubleshooting: Firebug, Firebug Lite, Fiddler. Can we reference these in the InfoCenter? Probably not. Are they FreeWare, or how are they available, by license ?

  1. Make sure that debugging is enabled in the portal Web 2.0 theme. To do this, edit the file head_csa.jspf and ensure that djportalConfig and ibmPortalConfig contain isDebug:true.

  2. Load a portal page that uses the PortalWeb2 theme.

  3. After the page has completed loading, type the following into the browser address bar and press enter: javascript:toggleDebugForm() . As a result, the portal displays a form at the bottom of the page that allows you to launch the debug console in a new window. The debug console will then log debug and trace statements that help you identify the problem.
Parent topic: Logging and tracing
Library | Support | Terms of use |