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:

The logging parameters that follow can take the following values:

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.