How to identify and resolve problems with your aggregator | HCL Digital Experience
If your custom aggregator is not working correctly, perform the checks listed here.
- Verify that the HTML markup of the portal page contains the microformats that the aggregator expects.
- Verify that the tagging method that is used in the themes, skins, and portlets matches the
expected behavior of the aggregator. For example, the Page Builder theme shipped with the portal tags all metadata with CSS
classes whose names start with an
asa
prefix. - If you use the SiteAnalyticsMediator API and your aggregator is not notified about DOM changes
as expected, you can enable client side tracing by using the resource environment provider
WP CommonComponentConfigService. Set the following two configuration
properties:
After you have done this, save your changes and restart the portal server.cc.isDebug=true cc.traceConfig=["com.ibm.wps.analytics.*"]
- To review what occurs in the server side aggregator inclusion
code, specify the trace
com.ibm.wps.theme.extensions.*=debug
.