This article specifically seeks to summarize 'where to look for what' in PAS for OE logging and contains salient excerpts from the attached document which contains comprehensive information in full context: TroubleshootingPAS.docx
What and where are the log files associate with troubleshooting PASOE:
Three distinct and independent logging subsystems are used to record events.
1. Tomcat Logs
- catalina.out - system output and standard error messages
- catalina.<date>.log - entries that describe Tomcat server activity
- localhost.<date>.log - tracks Web Application activity
- localhost_access.<date>.log - tracks requests processed by the Web Server
- host_manager.<date>.log - Tomcat's host-manager.war Web application
- manager.<date>.log - Tomcat's manager.war Web application activity
Logging Configuration : <CATALINA_BASE>/conf/logging.properties.
2. PASOE Web App Log
- <Web App name>.<date>.log
Logging Configuration : <CATALINA_BASE>/webapps/<Web app name>/WEB-INF/logging.xml
Since OpenEdge 12, logging is no longer at the WebApp level. Refer to: How to configure PAS debug logging in OpenEdge 12.0?
3. PASOE Multi-session agent Log (<PAS instance name>.agent.log)
- <instance name>.agent.log
Logging Configuration : <CATALINA_BASE>/conf/openedge.properties
Since OpenEdge 12:
- [instance] $CATALINA_BASE/conf/logging-ablapp.xml
- [ABL App], $CATALINA_BASE/ablapps/[ABLAppName]/conf/logging-ablapp.xml
Other Logging Considerations:
How to begin troubleshooting PASOE
Start with the <application>.agent.log file:
- The Agent (MSA) is where the majority of activity occurs, which provides is the common place to begin investigating a problem
- Scan the file for the time of the error (time being based on the system time of the PASOE / Tomcat process).
If no errors are listed there go one level higher, <instancename>.<date>.log.
- Scan the file for the time of the error (time being based on the system time of the PASOE / Tomcat process).
If no errors are listed within these files search higher still to see if an error is recorded in either the catalina.<date>.log, the local_host.<date>.log, or the local_access_log.<date>.txt file.
Just as there is a means to configure how verbose and where Tomcat creates its logs there is also a way to configure the PASOE multi-session agent for where and how verbose it logs information, the conf\openedge.properties file.
PASOE configuration properties files:
Once created, a PASOE instance's configuration files are in: <CATALINA_BASE>/conf
Details are described in the corresponding "README", for example: appserver.properties.README, catalina.properties.README, openedge.properties.README .. etc
- jvm.properties - Tomcat Java Virtual Machine (JVM) options
- catalina.properties - sets standard Tomcat configuration options for ports, keystore location etc
- appserver.properties - custom PASOE properties called at startup by server.xml.
- server.xml - Tailored specifically for PASOE to use Java system properties that are defined externally in both catalina.properties and appserver.properties files.
- web.xml, content.xml - defaults common to all the Web applications deployed.
- openedge.properties - properties that govern the behavior of the Multi-Session Agent (_mproapsv) along with which transports are enabled and which webapps belong to which ABL application. Configuration for debugging, logging, and other properties are described in
- oeablSecurity.properties - properties and values for all abl (oeabl.war) based web applications in the PASOE instance (since OpenEdge 11.7)
- logging.properties - Tomcat logging
- logging-tomcat.properties - PASOE Tomcat logging (Since OpenEdge 12)
- logging-pasoe.properties - deployed ABL application logging (Since OpenEdge 12)
