The Endeca Logging and Reporting System provides an application-level logging solution.
- The Logging API receives requests from the application modules, and passes them to the Log Server via HTTP.
- The Log Server translates the log requests into log files.
- The Report Generator uses the log files created by the Log Server to generate reports.
Logging API
The application is responsible for constructing and submitting all log requests to the Log Server via the Logging API. Log requests are completely independent of MDEX Engine requests. This architecture allows maximum flexibility when designing your application’s logging functionality.
Log Server
The Log Server translates application logging requests into log files that the Report Generator can process. You can use Endeca Workbench to:
- Specify the port on which the Log Server listens.
- Start and stop the Log Server.
- Determine if the Log Server is running.
Report Generator
The Report Generator uses the log files created by the Log Server to construct HTML and XML-based reports. The HTML reports can be viewed directly in a Web browser. The XML reports can be displayed on the View Reports page of Endeca Workbench.
The Report Generator uses two files to do its job:
- Report settings file—Determines which reporting data, if any, is excluded from a report. Also sets chart display increments and session queue size.
- XSLT stylesheet—Determines whether the Report Generator creates an HTML or XML report.
