PAS for OpenEdge creates log files at three distinct levels:

  • Tomcat logs contain logging information for the web server and JSP servlet container of a particular PAS for OpenEdge instance. These logs include Catalina logs for the core server, localhost logs for the Tomcat virtual server, server access logs, and Tomcat Manager logs.
  • ABL application-level logs contain logging information for ABL applications running on a PAS for OpenEdge instance. This includes Spring Security authentication and authorization process event logs, and multi-session agent logs containing logging information for the ABL Session Manager running on a PAS for OpenEdge instance.
  • Instance-level independent logs include remote management and server support logs, and user-deployed Java web applications.

For more information, see Configure logging in PAS for OpenEdge in Manage Progress Application Server (PAS) for OpenEdge.

PAS for OpenEdge logs and their contents

The following tables list the log files produced by each component of PAS for OpenEdge, and the kind of information found in each log file.

The default location for all these log files is $CATALINA_BASE/logs.

The $CATALINA_BASE environment variable defines the root directory of a PAS for OpenEdge instance. On a UNIX-machine, reference the logs directory as $CATALINA_BASE/logs. On a Windows machine, reference %CATALINA_BASE%\logs.

Table 1. Tomcat logs
Filename Description
catalina.date.log Activity log of the Tomcat server or any of the deployed web applications.
catalina.out A UNIX-only, catch-all log file that contains everything written to the Tomcat console output, for every application or process.
localhost.date.log Web application activity. The default Tomcat host name log.
localhost-access.date.log Requests processed by the web server.
manager.date.log Activity from the Tomcat Manager.
host-manager.date.log Activity from the Tomcat Manager for virtual hosts.
Table 2. Multi-session agent logs
Filename Description
instance-name.agent.log Activity from the ABL sessions, including ABL application startup and shutdown procedures.
Table 3. ABL application logs
Filename Description
ABL-app-name.date.log Each interaction that the ABL application has with the agent.
ABL-app-name.agent.date.log The ABL application agent process log output.
ABL-app-name_authn.date.log A log file that contains the audit trail of failed and passed Spring Security authentication process events. The log is shared by all deployed web apps and transports mapped to the ABL application. This log file can help detect possible server attacks, and track users who access the application.
ABL-app-name_authz.date.log A log file that contains the audit trail of failed and passed Spring Security URL access control process events. The log is shared by all deployed web applications and transports mapped to the ABL application. This log file can help detect possible intruder scanning.
oests.date.log The Spring Security and Security Token Service web application log that is found only in the OpenEdge Authentication Gateway server.
Table 4. Independent web application logs
Filename Description
oemanager.date.log The log file of the remote ABL application administration API.
oehealth.date.log The log file of the OpenEdge HealthScanner web application.
oedbg.date.log The log file of the OpenEdge Debugger web application.