WAS,IHS and Plugin log Details
IBM Http Server Logs.
=================
Default log Directory
————————–
<IHS_Install_Root>/logs
access.log –> Contains the logs of all requests process by IBM Http Server.
error.log —-> Contains the errors and diagnostics information while processing the requests.
Plugin Logs.
========
Default Log Directory.
—————————
<Plugin_Install_Root>/logs
http_plugin.log —> Contains the logs of plugin errors.
WebSphere Application Server Logs.
===========================
Default log Location.
————————–
<LOG_ROOT> = <WAS_Profile_Root>/logs/
<SERVER_LOG_ROOT> = <WAS_Profile_Root>/logs/
for Eg: If the WAS profile location is “/usr/IBM/WebSphere/AppSever/
<LOG_ROOT> = “/usr/IBM/WebSphere/AppSever/
<SERVER_LOG_ROOT> = “/usr/IBM/WebSphere/AppSever/
Trace Logs.
————-
<SERVER_LOG_ROOT>/trace.log —> Contains the trace information if the trace is enabled.
JVM Logs.
———–
These logs are created by redirecting output and error streams of JVM into independent log files. The SystemOut.log file contains the logs used to monitor the health of running application server. SystemErr.log contains the exceptions. Every application servers and all of its application will have these two sets of files.
<SERVER_LOG_ROOT>\SystemOut.lo
<SERVER_LOG_ROOT>/
Process Logs.
—————-
The application server writes output and error streams of native processes into these logs.This may also contain the information related to problemes in native codes.
If the Verbose GC is enabled, GC informations are written into these logs.
<SERVER_LOG_ROOT>/
<SERVER_LOG_ROOT>/
IBM Service Logs.
——————–
This is a binary log and it need Log Analyzer tool to analyze. There will be only one activity log for a single node ( for all JVMs and nodeagents).
IBM Service Log contains the information written to System.out by the Application Server run time as well as special messages that contain extended service information. These logs are mainly used by IBM service team for solving complex issues.
<LOG_ROOT>/activity.log
Recent Comments