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 remotely from the server...
- Make sure that debugging is enabled in the portal Web 2.0 theme.
To do this, edit head_extras.jspf and ensure that djportalConfig and ibmPortalConfig contain isDebug:true.
- Load a portal page that uses the PortalWeb2 theme.
- After the page has completed loading, type one of the following strings into the browser address bar and press Enter:
- javascript:toggleDebugConsole();
- For a custom theme that does not define the javascript:toggleDebugConsole(); function, type...
javascript:com.ibm.portal.debug.NewWindow.startLogging()
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.
In this context Javascript debugging tools can be helpful.
For Firefox browser, install the Firebug add-on.
Parent topic:
Log and tracing