Data Collection Operational Overview

8-10 Application Administrators Guide for Content Server

8.3.2 Data Collection

Content Tracker data collection includes collecting information from static URL references along with Content Server service call events. Both types of data are recorded in a combined output table SctAccessLog. However, service calls are inserted into the log in real time whereas the static URL information must first undergo the reduction process either manual or scheduled. This section covers the following topics: ■ Service Handler Filter on page 8-10 ■ Web Server Filter on page 8-11 ■ Content Tracker Logging Service on page 8-11

8.3.2.1 Service Handler Filter

The Content Server service handler filter is the primary Content Tracker data collection mechanism. This filter makes it possible for Content Tracker to obtain information about dynamic content requests that come through the web server, and also about other types of Content Server activity, such as calls from applications. The service request details are obtained from the DataBinder that accompanies the service call, and the information is stored in the combined output table SctAccessLog in real time. For more information about the SctAccessLog table, see Combined Output Table on page 8-12. There is a user-modifiable configuration file that is used to determine which Content Server service calls are logged. This file SctServiceFilter.hda uses a ResultSet structure that includes one service definition entry for each service to be logged. If you are using the extended service logging function, the SctServiceFilter.hda file also contains field maps that correspond to various service definition entries, see Services Tab on page A-161. For more detailed information about configuring service calls using the service handler filter, see Service Call Configuration on page 8-75. The ResultSet included in the SctServiceFilter.hda file is named ServiceExtraInfo. This ResultSet contains one or more service entries that define the services to be logged. To support the extended service logging function, additional ResultSets are used. These are called field map ResultSets. Each service that will have additional data values Managing Content Tracker 8-11 tracked must have a corresponding field map ResultSet in the SctServiceFilter.hda file. Field map ResultSets define the data fields, locations, and database destination columns for the related service.

8.3.2.2 Web Server Filter

Managed content that is retrieved via a static URL does not usually invoke a Content Server service. Therefore, the Content Tracker web server filter collects the access event details static URL references and records them in raw event logs sctlog files. The information in these files requires an explicit reduction either interactive or scheduled before it is included in the combined output table SctAccessLog along with the service call data. For more information about the sctlog files, see Content Tracker Event Logs on page 8-11. For more information about the SctAccessLog table, see Combined Output Table on page 8-12.

8.3.2.3 Content Tracker Logging Service

The Content Tracker logging service is a single-service call that may be called directly via a URL or as an action in a service script. It may also be called from IdocScript using the executeService function. The calling application is responsible for setting any and all fields in the accompanying service DataBinder that need to be recorded, including the descriptive fields listed in the Content Tracker service filter configuration file SctServiceFilter.hda. For more detailed information about configuring service calls using the Content Tracker logging service, see Service Call Configuration on page 8-75.

8.3.3 Data Reduction