Arbortext Publishing Engine uses the Java Apache log4j package to trace its internal operation. By default, this information is entered in the servlet log. Administrators can control the level of detail entered in the log by setting the global debug variable to true in the e3config.xml configuration file. Enabling the debug parameter is the first step in trying to diagnose problems with the Arbortext Publishing Engine.

With debug set to true, the Arbortext PE Request Manager will make several log entries for every transaction, specifying the start of each transaction, whether a cache manager, queue manager, or request handler generated a response, whether the transaction was queued or processed immediately, how the transaction response was transmitted, and whether the transaction was archived before it was deleted from the active transaction area.