Managing Service Call Information

8-82 Application Administrators Guide for Content Server

8.6.3 Managing Service Call Information

This section provides information and task procedures for mapping and logging data from Content Server services to the combined output database table SctAccessLog. This section covers the following topics: ■ Manually Editing the SctServiceFilter.hda File on page 8-82 ■ Setting Required DataBinder Fields to Call the Content Tracker Logging Service on page 8-83 ■ Calling the Content Tracker Logging Service from an Application on page 8-84 ■ Calling the Content Tracker Logging Service from IdocScript on page 8-84

8.6.3.1 Manually Editing the SctServiceFilter.hda File

To add or change entries in the SctServiceFilter.hda file: 1. In a text editor, open the SctServiceFilter.hda file: cs_rootdatacontenttrackerconfig...SctServiceFilter.hd 2. Edit an existing entry or add a new service entry. For example, to add the GET_ FILE_FORM service, enter the following service entry to the ServiceExtraInfo ResultSet in the file: GET_FORM_FILE Threaded Discussion Content Access optional_reference_value optional_field_map_link_value where the optional_field_map_link_value is used if you are implementing the extended service call tracking function. In this case, you must also add or edit the corresponding field map ResultSet. Otherwise, if you are implementing extended service tracking, skip Step 3. 3. If you use extended service tracking, you must add or edit the corresponding field map ResultSet. For example, to add the SS_GET_PAGE service and track additional data field values, enter the following service entry and corresponding field map ResultSets to the file: 4. Save and close the file. Service Entry Field Map ResultSet SS_GET_PAGE Site Studio Web Hierarchy Access web SSGetPageFieldMap ResultSet SSGetPageFieldMap 3 dataFieldName 6 255 dataLocation 6 255 accessLogColumnName 6 255 DataBinder_field_name data_field_location_name access_log_column_name end Note: Include as many sets of DataBinder field, location, and table column names as necessary. Managing Content Tracker 8-83 5. Restart the Content Server to apply the new definitions.

8.6.3.2 Setting Required DataBinder Fields to Call the Content Tracker Logging Service

The following table provides the SctAccessLog column names and the corresponding DataBinder fields that Content Tracker looks for when the Content Tracker logging service SCT_LOG_EVENT is called. When an application calls the Content Tracker logging service, the application is responsible for setting the necessary fields in the service DataBinder for Content Tracker to find. For more detailed information about the SctAccessLog fields, see the Combined Output Table on page 8-12. Note: Search request events are logged into the SctAccessLog table in real time and do not need to be reduced. Optionally, you can add or edit services with the user interface included in the Data Engine Control Center. For more information, see the Data Engine Control Center on page A-154 and the Services Tab on page A-161. SctAccessLog Column Name Service DataBinder LocalData Field SctDateStamp [computed] SctSequence SctSequence SctEntryType S eventDate [computed] SctParentSequence SctParentSequence c_ip REMOTE_HOST cs_username HTTP_INTERNETUSER cs_method REQUEST_METHOD cs_uriStem HTTP_CGIPATHROOT cs_uriQuery QUERY_STRING cs_host SERVER_NAME cs_userAgent HTTP_USER_AGENT cs_cookie HTTP_COOKIE cs_referer HTTP_REFERER sc_scs_dID dID sc_scs_dUser dUser sc_scs_idcService IdcService or SctIdcService sc_scs_dDocName dDocName sc_scs_callingProduct sctCallingProduct sc_scs_eventType sctEventType sc_scs_status StatusCode sc_scs_reference sctReference also ... comp_username [computed - HTTP_INTERNETUSER or ...] sc_scs_isPrompt na sc_scs_isAccessDenied na 8-84 Application Administrators Guide for Content Server

8.6.3.3 Calling the Content Tracker Logging Service from an Application

You can call the SCT_LOG_EVENT service from an application. This can be done by the application developer, or by a user willing to modify the application service scripts. The application can call SCT_LOG_EVENT from Java. Or, the application can include calls to SCT_LOG_EVENT in the service script.

8.6.3.4 Calling the Content Tracker Logging Service from IdocScript

You can call the SCT_LOG_EVENT service indirectly from IdocScript, using the executeService function. This is the same as calling the SCT_LOG_EVENT service from an application except that it occurs from IdocScript instead of the application Java code. Content Tracker cannot distinguish whether the SCT_LOG_EVENT service is called from Java or from IdocScript.

8.7 Configuration and Customization