45 Troubleshooting Content Tracking Issues

Content Tracker has two execution trace mechanisms: the Web server filter plug-in and the Java code. These are intended for diagnosing problems at customer installations and are not to be used in production.

Hanging browser: If Oracle WebCenter Content Server terminates while the Data Engine Control Center is running, the browser can also hang. To resolve the issue, close the browser window.

This chapter includes the following topics:

45.1 Web Server Filter Plug-in Debugging Support

The Web server filter plug-in honors PLUGIN_DEBUG. Enable PLUGIN_DEBUG on the Filter Administration page and the Content Tracker Web server filter plug-in issues execution trace information. The trace is only meaningful to someone with access to the source. Customers with a problem are expected to enable PLUGIN_DEBUG, run the test scenario, then send the log segments to Customer Service for evaluation. Otherwise, turn PLUGIN_DEBUG off.


  1. Choose Administration then Admin Applets from the Main menu.

  2. Click Filter Administration.

  3. On the Configure Web Server Filter Plug-in page, select PLUGIN_DEBUG.

  4. Click Update.

45.2 Java Code Debugging Support

Use the System Audit functionality in Content Server for debugging support. For more information, see "System Audit Information" in Oracle Fusion Middleware Administering Oracle WebCenter Content. Add contenttracker to the Active Sections list. When the list is updated, the Content Tracker execution trace information appears with the other active sections.

45.3 DataBinder Dump Facility

When Content Tracker records a specific service in the log file, it records the contents of the service's DataBinder object in a serialized dump file. The contents of these files are useful for debugging field maps that use the extended service call tracking function. These dump files allow you to see the available LocalData fields for the recorded service.

The Content Tracker service handler filter only creates dump files for DataBinder objects if the associated services are defined in the SctServiceFilter.hda file.


The dump files for DataBinder objects continue to accumulate until manually deleted. Use the SctDebugServiceBinderDumpEnabled configuration variable only as necessary.

Set the SctDebugServiceBinderDumpEnabled configuration variable to true to configure the service handler filter to write out the objects into dump files. For more information about Tracker Configuration variables, see Oracle Fusion Middleware Configuration Reference for Oracle WebCenter Content.

The files are stored in the /ContentTracker/DEBUG_BINDERDUMP directory. File names consist of three parts: service_name_filter_function_serial_number.hda

  • service_name is the name of the logged service (such as, GET_FORM_FILE).

  • filter_function is one of the following:

    • End: Filter Event on EndServiceRequestActions. Normal end-of-service event.

    • EndSub: FilterEvent on EndScriptSubServiceActions. Normal end-of-service for service called as SubService.

    • Error: Filter Event on ServiceRequestError. End of service where an error occurred. Can happen in addition to End.

  • serial_number is the unique identification number assigned to the file. Content Tracker can create multiple DataBinder object dump files for a given service.