Configuring Arbortext Publishing Engine > Setting Configuration Parameters > Arbortext Publishing Engine Global Parameters > The Global Application Logging Parameters
  
The Global Application Logging Parameters
The application logging parameters control the type and level of logging for all applications running on Arbortext Publishing Engine. All the logging parameters follow the convention of the Java Log4j 2 package. For information on log4j2.xml and how to use it, consult the standard documentation provided for Log4j 2, available from:
logging.apache.org/log4j/2.x/manual/index.html
The logging parameters that follow can take the following values:
OFF
FATAL
ERROR
WARN
INFO
DEBUG
TRACE
ALL
INHERIT
com.arbortext.e3.applicationLog
Specifies the log level for all applications. Beginning with Arbortext Publishing Engine 8.1.0.0, the level is controlled in log4j2.xml. By default, it’s explicitly set to ERROR. The log4j2.xml property file is located at PE_HOME\lib\resources.
com.arbortext.e3.applicationLog.compose
Specifies the log level for publishing requests submitted from a Arbortext Editor client. By default, it’s explicitly set to INHERIT, which means use the setting for com.arbortext.e3.applicationLog.
com.arbortext.e3.applicationLog.convert
Sets the log level for requests submitted using the f=convert function. By default, it’s explicitly set to INHERIT, which means use the setting for com.arbortext.e3.applicationLog.
After determining the logging level for an application, the Arbortext PE Request Manager and Arbortext PE sub-processes will ignore any attempt by the application to make log entries with a lower priority. For example, if the logging level is WARN, then messages with a level of INFO, DEBUG, and TRACE are ignored.
If the logging level is INFO, DEBUG, or TRACE, then intermediate files can be accepted and saved. Use the Transaction Archive link on the Arbortext Publishing Engine index page (described in Monitoring and Reporting Using a Web Browser) to view the archived transactions. An archived transaction can include intermediate files if the application saves them. Refer to Monitoring the Transaction Archive for more information.
Learn how to use logging from custom applications in the Programmer's Guide to Arbortext Publishing Engine.
com.arbortext.e3.applicationLog.acl
Sets the log level for tracing in ACL applications
com.arbortext.e3.applicationLog.acl.package.function
Sets the log level for the ACL application specified by package::function
com.arbortext.e3.applicationLog.java.class
Sets the log level for the Java application specified by class
com.arbortext.e3.applicationLog.javascript.function
Sets the log level for the JavaScript application specified by function
com.arbortext.e3.applicationLog.vbscript.function
Sets the log level for the VBScript application specified by function