Web Server Filter Debugging Support Java Code Debugging Support DataBinder Dump Facility

8-90 Application Administrators Guide for Content Server ■ Web Server Filter Debugging Support on page 8-90 ■ Setting the Debug Plugin on page 8-90 ■ Java Code Debugging Support on page 8-90 ■ DataBinder Dump Facility on page 8-90 ■ Accessing the DataBinder Object Dump File on page 8-92 ■ Setting the Debugging Configuration Variables on page 8-92

8.8.1 Web Server Filter Debugging Support

The web server filter honors PLUGIN_DEBUG. Enable PLUGIN_DEBUG on the Content Server Filter Administration page and the Content Tracker web server filter will issue 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, and then send the log segments to Customer Service for evaluation. Otherwise, PLUGIN_DEBUG should be left turned off.

8.8.2 Setting the Debug Plugin

To set PLUGIN_DEBUG:

1. In Content Server, click the Admin Applets link in the Administration tray.

The Administration page is displayed.

2. Click the Filter Administration icon or link.

The Configure Web Server Filter page is displayed. 3. Select the PLUGIN_DEBUG option check box. 4. Click Update.

8.8.3 Java Code Debugging Support

You can use the System Audit functionality in Content Server for debugging support. See System Audit Information in the Oracle Fusion Middleware System Administrators Guide for Content Server for more details. Add contenttracker to the Active Sections list. When the list is updated, the Content Tracker execution trace information appears with the other active sections.

8.8.4 DataBinder Dump Facility

This section covers the following topics: ■ Values for the DataBinder Dump Facility on page 8-90 ■ About DataBinder Object Dump Files on page 8-91 ■ Location of the DataBinder Object Dump Files on page 8-91 ■ Names of the DataBinder Object Dump Files on page 8-91

8.8.4.1 Values for the DataBinder Dump Facility

The values for this configuration variable include: ■ SctDebugServiceBinderDumpEnabled=False prevents the Content Tracker service handler filter from writing out the DataBinder objects into dump files. This is the default value. Managing Content Tracker 8-91 ■ SctDebugServiceBinderDumpEnabled=True configures the Content Tracker service handler filter to write out the DataBinder objects into dump files. Consequently, you can use a dump file as a diagnostic aid when you are developing field maps for extended service logging. If you are creating field maps for services, the dump files enable you to see what data is available at the time the service events are recorded.

8.8.4.2 About DataBinder Object Dump Files

As soon as Content Tracker records a specific service in the log file, the contents of that services DataBinder object are written to a serialized dump file. The contents of these files are useful for debugging when you are creating field maps to 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. For more information about this file, see About the Service Call Configuration File on page 8-75.

8.8.4.3 Location of the DataBinder Object Dump Files

The serialized DataBinder objects are written to: IntradocDirdataContentTrackerDEBUG_BINDERDUMPdump_file_name

8.8.4.4 Names of the DataBinder Object Dump Files

The dump file of DataBinder Objects are text files and their names consist of three parts as follows: service_name_filter_function_serial_number.hda Where: ■ 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. May happen in addition to End. ■ serial_number is the unique identification number assigned to the file. This enables Content Tracker to create more than one DataBinder object dump file for a given service. Example: GET_SEARCH_RESULTS_End_1845170235.hda Caution: The dump files for DataBinder objects will continue to accumulate until you manually delete them. Therefore, it is recommended that you are careful to use the SctDebugServiceBinderDumpEnabled configuration variable only as necessary. 8-92 Application Administrators Guide for Content Server

8.8.5 Accessing the DataBinder Object Dump File