The instance-name/conf/logging-tomcat.properties file sets the logging properties for Tomcat components.

The following Tomcat logging components can be configured in logging-tomcat.properties:
  • catalina.out—core Tomcat console logging output file.
  • catalina.date.log—Tomcat server or any of the deployed web application activity log.
  • localhost.date.log—web application activity. The default Tomcat hostname log.
  • manager.date.log—activity of the Tomcat manager web application.
  • host-manager.date.log—activity of the Tomcat manager web application for virtual hosts.
  • oehealth-collector.date.log—activity of the OpenEdge HealthScanner web application.
  • localhost-access.date.log—activity of requests processed by the web server.

The following table defines the instance-name/conf/logging-tomcat.properties configuration file that permits control of logging for the Tomcat server and its distributed web applications:

Tomcat subsystem Log file name Property name Value definition
Java stdout catalina.out psc.as.logging.console.pattern Defines the output format for what is logged, in which columns, and with what static content.
psc.as.logging.console.level Defines the logback logging level for all console logging.
Tomcat server catalina.date.log psc.as.logging.catalina.fileName Defines the output filename format and how often new instances of the log file are created.
psc.as.logging.catalina.level Defines the amount of logging detail to output for the subsystem.
Tomcat server client connectors localhost-access.date.log psc.as.logging.access.fileName Defines the output file name format and how often new instances of the log file are created.
psc.as.logging.access.pattern Defines the output format for what is logged, in which columns, and with what static content.
Tomcat server virtual host localhost.date.log psc.as.logging.localhost.fileName Defines the output filename format and how often new instances of the log file are created.
psc.as.logging.localhost.level Defines the amount of logging detail to output for the subsystem.
Tomcat manager web app manager.date.log psc.as.logging.manager.fileName Defines the output filename format and how often new instances of the log file are created.
psc.as.logging.hostmanager.level Defines the amount of logging detail to output for the subsystem.
Tomcat OpenEdge HealthScanner oehealth-collector.date.log psc.as.logging.oehealth.fileName Defines the output filename format and how often new instances of the log file are created.
psc.as.logging.oehealth.pattern Defines the output format for what is logged, in which columns, and with what static content.
psc.as.logging.oehealth.level Defines the amount of logging detail to output for the subsystem.
Tomcat server common Common to all Tomcat log files psc.as.logging.tomcat.pattern A common log file output format if one is not explicitly defined in the logging subsystem.
psc.as.logging.maxhistory The maximum number of log file versions that will be kept in the logging destination directory.
psc.as.logging.tomcat.level Common logging level if not explicitly defined in the above logging subsystems.
Note:
  • Logback product logging levels include: OFF | ERROR | WARN | INFO | DEBUG | TRACE
  • Logback product logging pattern token definitions are fully described in the Logback product documentation.
  • The property value may include tokens for MDC, OS process environment variables (case sensitive), and properties defined in the logging property files