Application server logs are available only when you use Orchestration Designer to create the speech application and are running it in a Tomcat environment.
All application server logs are in ASCII format. You can view them in any text editor.
Application server servlet container logs
The logs contain log data from the servlet container. You can find these log files in the following locations:
$CATALINA_HOME/logs/catalina.out
$CATALINA_HOMElocalhost.date.log.txt
For more information on setting the number of application server failover logs in the EPM settings, see theEPM Settings and View EPM Settings Page field descriptions topic in the Administering Avaya Experience Portal.
Note:
If you install or upgrade Experience Portal and this log already exists, Experience Portal automatically renames the existing file as catalina.nnn, where nnn is a unique sequential identifier starting with 000. It then creates a new version of catalina.out and writes all log entries from the current installation forward into that file.
Orchestration Designer errors and application reports log
This log file only exists if Orchestration Designer cannot write data to the EPM when its session ends. The next time Orchestration Designer ends, it again tries to write its log data to the EPM, so the information in this log is eventually transferred to the EPM.
You can find this log file in the following location: $CATALINA_HOME/webapps/app_name/data/logs/savereport.log
Note:
If application reporting is disabled, no data is logged. Otherwise, all report data is sent to the EPM.
Orchestration Designer trace log
If the query string includesddtrace=true, this log contains application specific trace data.
You can find this log file in the following location: $CATALINA_HOME/logs.log
You can change the location, format, and contents of this log, in the webapps/app_name/data/ddlog4j.properties file.
