Adding an Active Site Analytics aggregator to a portal page | HCL Digital Experience
Portal administrators can manage the aggregators. They can assign an aggregator to one or more portal labels or pages.
About this task
As a portal administrator, you assign an aggregator to a page by editing the page properties and adding a new parameter. To do this by using the portal administration portlets, proceed by the following steps:
Procedure
- Add the aggregator to the directory js in
the theme directory. For example, for the portal theme, the WebDAV location is as follows:
Take a note of the name of the aggregator file. You need it in later steps. Go to the Analytics section of Modules that are provided with the modularized theme for information.mycontenthandler/dav/themelist
- To open the Manage Pages portlet, click the Administration menu icon. Then, click .
- Locate the page to which you want to assign the aggregator.
Use the Manage Pages portlet to locate the page. Note: The page must be located as a child of the portal content root.
- Click Edit Page Properties for the
page that you selected. Note: You cannot add an Active Site Analytics aggregator to the content root. Edit Page Properties is not available for the content root.
- To expand the available choices, click the plus sign (+) icon next to Advanced Options.
- Click I want to set parameters.
- In the field New parameter, type
a string that starts with asa_aggregator or asa_dependency.
Values that correspond to names that start with the string asa_aggregator are
added to the page body, names that start with asa_dependency are
added to the head. Both the aggregators and dependencies are added
to the portal page in alphabetical order according to the Java method
Collections.sort()
. - In the New value field, type the name of the aggregator script file.
- Click Add.
- Verify that the new parameter is added to the list.
- Repeat steps 6 - 9 for all aggregators and dependencies.
- Click OK to return to the main Page Properties screen.
- Click OK to save your changes and return to the Manage Pages screen.
What to do next
Note: Children pages inherit the script that is set on the
parent page. If you want to use a different aggregator on a child
page, follow the same procedure that is previously addressed for the
child page to make the appropriate assignment. If you want to block
inheriting the aggregator setting from the parent page, follow the
same procedure, but leave the value empty. As a result, the page has
no aggregator that is assigned anymore and all children of the page
inherit the new setting.