There are two ways to debug module information. First way is to enable a trace string. In this case, debugging is enabled for all users. Second way is to set a specific cookie. In this case, debugging is only enabled for the user who set the cookie.
- Enable tracing via trace string
- To debug a module or theme, enable Portal tracing using the following trace string:
This will load the modules using separate links and script tags, isolating each one independently. It will also load debug versions of each contribution if the module definition has defined a debug version. Typically, the debug version is an uncompressed version of the script tag containing the same data as the normal version.
Both using separate links and using uncompressed script tags will make it easier to debug a running Portal environment from the browser.
- Enable tracing via cookie
If you choose this way, then debugging information is only logged for the user which set the cookie. All other users do not generate debug information when rendering portal pages.
To enable this tracing, first set a property in a resource environment provider:
- Open WebSphere Application Server administrative console.
- Select Resources -> Resource Environment -> Resource Environment Providers
- Select resource environment provider WP ConfigService.
- Click custom properties.
- Change the resourceaggregation.client.debug.mode.allowed entry to true.
- Save the changes.
- Restart the portal server.
Now, if a user sets a cookie named com.ibm.portal.resourceaggregator.client.debug.mode
, debug versions of module contributions will be loaded if defined and modules will be loaded using separate links and script tags.
Parent topic: Administering the theme modularization framework