Gathering additional logging information
IBM WebSphere or JSP engine logging provides more insight on issues where the mid tier application is not successfully deployed. IBM Webserver or JSP engine logs also provide information about an un-handled run time exception or external factors such as Apache Tomcat issues.
The following table describes details about gathering additional information:
|Source||Location of logs|
Apache Tomcat logs are present in the <tomcat installation dir>\logs folder.
c:\Program Files\Apache Software Foundation\Tomcat#\logs
Hash (#) indicates the log file version.
Configuration files are available at the following location:
Oracle WebLogic logging infrastructure supports a logger on each server that collects the log events generated by the application server. By default, logs are sent to the following three destinations:
Log File — Messages sent to the server Log file.
By default, the server log file is located in the logs directory under the server instance root. DOMAIN_NAME\servers\SERVER_NAME\logs\SERVER_NAME.log.
For example, the log file for the Admin Server of the base_domain is C:\Weblogic\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log
|IBM WebSphere||The WebSphere runtime logging covers the administration of the server and of the applications deployed on it. |
It is located in the $WAS_HOME/profiles/logs folder.
|JBoss||JBoss logs include the server.log. The logs are located in the <jboss installation dir>/standalone/logs folder.|
|Mid tier configuration files|
The mid tier configuration files are located at the following location:
<mid tier installation directory>\WEB-INF\web.xml