Enabling client side logging and tracing | HCL Digital Experience
Modify the custom properties cc.isDebug and cc.traceConfig in the WP CommonComponentConfigService to enable client-side logging and tracing.
Procedure
- Access the WebSphere® Integrated Solutions Console.
- Go to .
- 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:
This value adds client-side trace-logging for all components in the namespace["com.ibm.mashups.enabler.*","com.ibm.mashups.builder.model.ContextMenu"]
com.ibm.mashups.enabler
and the componentcom.ibm.mashups.builder.model.ContextMenu
. - Save and persist the changes to the master configuration.
- Restart the portal server.
Example
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.*"]