Using LiveCycle ES3 and Application Server Log Files

Log files are useful for LiveCycle ES3 and application server failure analysis and may be required when dealing with Adobe Enterprise Support.

This section lists the common log files that you can use to diagnose LiveCycle ES3 problems. It also describes some of the most common errors that may be included in the LiveCycle ES3 log file.

LiveCycle ES3 log files

You can use log files to troubleshoot problems with LiveCycle ES3 installation or operation:

• LiveCycle ES3 log file: By default, the LiveCycle ES3 log file is located in the [LiveCycleES22 root] directory and named log.txt.
• LiveCycle Configuration Manager log file: By default, the LiveCycle Administration Console log file is in [LiveCycleES2 root] /ConfigurationManager/log and is named lcm.0.log or similar (the higher the number, the more recent the logs). The log files are useful for LiveCycle Configuration Manager failure analysis.

Application server log files

The application server log files are useful for application server and LiveCycle ES3 bootstrapping failure analysis. The default log files are in the following location for your application server:

JBoss: [LiveCycleES2 root] /jboss/server/all/log or [JBoss root] /server/all/log and named boot.log and server.log

WebLogic: /var/log/httpd/error_log

WebSphere: [WebSphere root] /logs/server1/trace.log

If the log file does not provide enough information to help you troubleshoot problems, you can specify the level of tracing in the log file to increase logging details. (See "Troubleshooting" in LiveCycle ES3 Administration Help .)