Parameters that Control Application Logging
• com.arbortext.e3.applicationLog
Sets the default level for tracing in all applications
• com.arbortext.e3.applicationLog.compose
Sets the log level for publishing requests submitted from a Arbortext Editor client.
• com.arbortext.e3.applicationLog.convert
Sets the log level for requests submitted using the f=convert function.
• 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
These application logging parameters can take the following values. By default, By default, the value is set to WARN, meaning messages are logged for levels FATAL, ERROR, and WARN.
• OFF
• FATAL
• ERROR
• WARN
• INFO
• DEBUG
• TRACE
• ALL
In addition, an application log is always included in the set of files saved to a transaction archive. However, you can specify an additional location for sending application log messages:
• com.arbortext.e3.applicationLog.display
If set to true (the default), application log messages are written to the Arbortext Diagnostics window. If set to false, messages are only logged in the transaction archive.
• com.arbortext.e3.applicationLog.displayPatternLayout
Specifies the Java log4j pattern to use when constructing log entries written to Arbortext Diagnostics window on Windows.