Enable client side logging and tracing

To enable client-side logging and tracing for console loggers in client web browsers, modify the custom properties...

• cc.isDebug
• cc.traceConfig

...in the WP CommonComponentConfigService. This resource environment provider manages many of the configurable options for the common component.

1. Access the WAS console and go to...
   Resources | Resource environment | Resource environment providers | WP CommonComponentConfigService

2. To set custom properties, click the Custom Properties link.

3. Set the value of the property cc.isDebug to true.

4. Set the value of the property cc.traceConfig property to a value representing a correctly formatted JavaScript array of strings. Each string in the array is the name of the component to trace. Use the wildcard character asterisk (*) for multiple matching. Example:
   ["com.ibm.mashups.enabler.*","com.ibm.mashups.builder.model.ContextMenu"]

   This value adds client-side trace-logging for all components in the namespace com.ibm.mashups.enabler and the component...

   com.ibm.mashups.builder.model.ContextMenu

5. Save and persist the changes to the master configuration.

6. Restart the portal server.

Example

Examples: To activate all iWidget related logging and tracing...

traceConfig: ["com.ibm.mm.iwidget.*"]

To set multiple patterns, you separate them by commas like this example:

traceConfig: ["com.ibm.mm.iwidget.*", "com.ibm.portal.*", "com.ibm.portal.wps.*"]

What to do next

We can also achieve the same result using scripting tools.

Parent Logging and tracing client side rendering

Related information

Configure custom properties for resource environment providers using wsadmin scripting