Servlet Tracing

How to:

Servlet tracing enables tracing for all ReportCaster servlets deployed in the web application, including the ReportCaster API. Servlet tracing provides information about queries to, and maintenance of, the Repository. This includes events that occur when a schedule is created.

Note: You should also view the Application Server log files. By default, Apache Tomcat trace files are located in the \logs directory of the Apache Tomcat installation. If Apache Tomcat was installed by the Client, Apache Tomcat is installed under the ibi directory path. If ReportCaster is configured with Managed Reporting, you should also view the Client session trace files. In the Administration Console, you can access these trace files by clicking Configuration, Diagnostics, and then Session Monitor.

Procedure: How to Access Servlet Tracing

  1. Navigate to the Administration Console.
  2. Click the Diagnostics tab.
  3. On the Diagnostics tab, under the Diagnostics folder, click Log Files.

    The list of log files appears, as shown in the following image.

    Log Files list in Administration Console Diagnostics tab
  4. In the Log Level column, select the type of information from the log file that you would like to access, as shown in the following image.

    The ReportCaster Log Level option provides the following levels of diagnostics information:

    • OFF. Capture no events.
    • FATAL. Capture only events that disrupt system operations.
    • ERROR. Capture events that generate error messages in addition to fatal events.
    • WARN. Capture events that generate warning messages in addition to fatal and error events.
    • INFO. Capture events that generate informational messages in addition to warning, error, and fatal events.
    • DEBUG. Capture events that generate trace messages in addition to informational, warning, error, and fatal events.
    • TRACE. Capture events that generate trace messages in addition to debug, informational, warning, error, and fatal events.
  5. Click the log file for which you would like to view traces.

    The following image shows an example where the event.log file is selected.