Configuring tracking_conf.xml file

The tracking_conf.xml file is the configuration file for the Tracking Core.

About this task

The Tracking Core handles requests from Synchronization Targets configured in the Content Manager for session data collected. The Tracking core stores each user request is separately, and these requests are bundled into batches. Synchronization Targets pick up these batches when they poll the Tracking Core.

Procedure

  1. Open the tracking_conf.xml file in a text editor.
  2. In the <Synchronization> section, configure the following attributes:
    • maxAttempts—(integer) specify the number of attempts made before a synchronization batch is considered permanently failed (failed batches are stored in the Content Data Store, whereas after a batch has been successfully retrieved the data is deleted).
    • maxRequestsPerBatch—(integer) specify the number of requests that make up a synchronization batch .
    • sessionTimeoutSeconds—(integer) the number of seconds that must have elapsed after a session's last tracking entry to mark it as a full session. By default, the Tracking Core keeps track of sessions that have not changed for 20 minutes.
    • processingTimeoutSeconds—(integer) the processing timeout in seconds: if tracking does not get a response from the Content Manager Server within this time frame, the batch is marked as failed.
    Set the maxRequestsPerBatch setting according to the available Java heap size. For example, a heap size of 256 MB may cause OutOfMemory errors if set to 60,000 records per synchronization batch. If OutOfMemory errors occur during synchronization, it is recommended to increase to the JVM heap size on the synchronization Web server.
    <?xml version="1.0" encoding="utf-8"?>
      <Configuration>  
        <Synchronization maxAttempts='5' maxRequestsPerBatch='100' sessionTimeoutSeconds='1200' processingTimeoutSeconds='1800'/>
         ...
    </Configuration>
  3. Save and close the file.
  4. Restart your Web application server.