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 and cc.traceConfig in the WP CommonComponentConfigService. This resource environment provider manages many of the configurable options for the common component.
To enable logging and tracing for client side rendering...
- Access the WAS administrative console.
- Navigate to Resources -> Resource environment -> Resource environment providers -> WP CommonComponentConfigService.
- To view and edit the custom properties for this resource environment provider, click the Custom Properties link.
- Set the value of the property cc.isDebug to true.
- Set the value of the property cc.traceConfig property to a value that represents a correctly formatted javascript array of strings. Each string in the array is the name of the component that you want to trace. You can 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.
- Save and persist the changes to the master configuration.
- Restart the portal server.
Examples: To activate all iWidget related logging and tracing, you use the following line:traceConfig: ["com.ibm.mm.iwidget.*"]To set multiple patterns, you separate them by commas like this:
traceConfig: ["com.ibm.mm.iwidget.*", "com.ibm.portal.*", "com.ibm.portal.wps.*"]By alternative, you can also achieve the same result by using scripting tools that WAS provides. For more information refer to the WAS information center under topic about Configuring custom properties for resource environment providers using wsadmin scripting.
Parent
Logging and tracing client side rendering