Setting Up Forms Aggregation - Client
Forms aggregation lets you gather all of the floating and document-attached form instances being generated on multiple client systems onto a single server so that you can analyze them.
About this task
Note: If you change the configuration parameters while the scheduled job is running, it will use the new parameters the next time it runs.
Note: Remember that all servers need to be part of a group with the same authorization seed. This is done by setting the lc.properties file to have the same value for "lc_auth_seed=" in line 1 (as described in the security chapter).
Tip: As you hover over an icon its label appears.
Procedure
- Log on to Content Delivery as a user with the Manage application permission.
- If you are in a Content Delivery tool, click Home in the breadcrumb trail.
The Content Delivery landing page appears.
- In the Administration Tools pane, click Manage Application.
The Manage Application page appears.
- In the left navigation pane, click Global Config.
- Set the values on the following config items:
Name Value xforms.aggregation.keyA unique string. This must match the same config value on the server. xforms.aggregation.urlURL of the server, in the following format: http://server_host_id:server_port_#/ContentDelivery/ where server_host_id is the server host name and server_port_# is the port on which the server Content Delivery instance is running. server_port_# is specified if you need to replace the standard port, in most cases this is not needed. A standard example would be http://aggregation.lc.example.com/ContentDelivery/ (where lcrefers to an example related to Content Delivery, andaggregationspecifies it further as a server dedicated to aggregation)host.idHost ID of the client. This is a unique key that identifies the client. If you have already set up audit trail aggregation, you do not need to add this configuration item again.
xforms.aggregation.enableSet to Yesto enable Forms aggregation. - Click Save.
- Do one of the following:
- For Content Delivery systems that use the built-in web app server, edit ContentDelivery_home/conf.xml.
- For Content Delivery systems that use Apache Tomcat as the web app server, edit Tomcat_home/webapp/LiveContent/WEB-INF/conf.xml
- Un-comment the line that defines the job for aggregation:
<job name="xforms.aggregation" type="user" xquery="/db/LiveContent/ui/skins/base/xql/xforms_aggregation.xql" period="1800000" delay="0"/> - Adjust the following values to set the timing of aggregation:
Option Description period Frequency, in milliseconds, that the aggregation occurs. delay Delay, in seconds, before aggregation occurs after restarting the Content Delivery service. - Do one of the following:
- On Windows, restart the LiveContent XML Database service.
- On Linux, log in as the root user, and type the following at a command prompt:
/etc/init.d/SDL_LiveContent restart
- Validate that XForms aggregation is occurring by viewing the logs.
- For Content Delivery systems using the built-in web app server, on the client, view ContentDelivery_home/logs/wrapper.log.
- For Content Delivery systems using Tomcat, look for Tomcat_home/logs/tomcat7std-out*.log or tomcat7std-err*.log
The success and failure messages appear like one of the following:XForms Aggregation: status=FAIL message=required URL not defined XForms Aggregation: status=DISABLED XForms Aggregation: status=SUCCESS enable=yes selected=3 stored=3 marked=3 serverURL=http://aggregation.lc.example.com/ContentDelivery/
Related tasks