HTTP Listener logging

HTTP Listener trace and audit logs capture details about listener events, socket activity, connections, and HTTP communications.

You can enable HTTP Listener tracing and audit logs through the listener Status browser or Management Console interface, the Launcher Administration utility or command, or the httplsnr command.

Note: Binary data is not logged.

The following table describes HTTP Listener logging.

Table 1. Listener logging details
Logging type	Logged information	Log name
Standard	HTTP Listener events such as client requests	`listenername`_`timestamp`_`hostname`.log
Verbose	Socket activity	`listenername`_socket_`timestamp`_`hostname`.log
Audit	Details about individual connections and map executions	`listenername`_audit_`timestamp`_`hostname`.log

Each listener has one audit log. The audit log is in XML format that can be queried with XSLT transformations. The audit log schema is LHL-Audit.xsd, installed in the Transformation Extender installation directory on Windows systems or the /bin directory on UNIX systems.

The location of the log files depends on how you start the listener:

When you start the listener by using Launcher Administration or the Management Console, the listener creates the log files in the tx_install_dir/logs directory.
When you start the listener from the command line and specify a fully qualified log file name, the listener creates the log files in specified path. If you omit the log file name or specify a relative path to the log file, the listener creates the log in the current working directory.