InfoCenter Home > 8.8.1: Using the Log Analyzer for Advanced EditionThe Log Analyzer takes one or more activity logs, merges all of the data, and displays the entries. Based on its "symptom database," it analyzes and interprets the error conditions in the log entries to help you debug problems. The Advanced Edition Log Analyzer has a special feature enabling it to download the latest symptom database from the IBM Web site. See "About the Log Analyzer" for details.
About the Log AnalyzerA Log Analyzer quite similar to the one available for use with IBM WebSphere Application Server is available with IBM Component Broker, part of the Enterprise Edition of IBM WebSphere Application Server. To learn about the Component Broker Log Analyzer, see the Component Broker problem determination guide (currently, Chapter 11). You can view the document on the IBM Web site without having to obtain Enterprise Edition: ftp://ftp.software.ibm.com/software/websphere/info/appserv/v35/ee/cbprbdet.pdf The main differences between the Log Analyzer available with WebSphere Application Server and the Component Broker Log Analyzer are the following:
Obtaining the Log AnalyzerThe Log Analyzer is available separately from IBM WebSphere Application Server, starting on or shortly after the release of Fix Pack 2 (Version 3.5.2) for IBM WebSphere Application Server. To obtain the Log Analyzer, including its installation instructions, visit the IBM WebSphere Application Server Tools site: http://www.ibm.com/software/webservers/appserv/tools.html About the activity logRecall, the Log Analyzer collects messages from various product components and places them in a shared file. The file is a binary file located at: product_installation_root/logs/activity.log The activity.log cannot be easily viewed using a text editor. The Log Analyzer is the tool for viewing the file. Using the Log AnalyzerTo view the activity.log using the Log Analyzer:
Related tasksIn the course of using the Log Analyzer, you might need to perform the following tasks. Setting the maximum activity.log file sizeThe activity.log file grows to a predetermined size, then wraps. The default size is 1 Megabyte (MB). To change the log size:
The size change will take effect at the next server startup. Syntax example:
Changing the port of the logging serviceThe logging service starts automatically at server startup. It requires the use of a dedicated port. The default port is 1707. To change the port value:
Syntax example:
If the port is in use by another application, the logging service might not be able to start or might not function correctly. The activity.log file will not be created or updated correctly. See the information about how to tell whether a port is currently allocated to another application. To diagnose a port conflict, perform these heuristic checks:
Viewing an activity.log file in the absence of a GUI.The Log Analyzer cannot be used to view remote files. If the operating system on which you are running WebSphere Application Server does not support the use of a graphical interface, then transfer the file in binary to the system on which you are running the WebSphere Java administrative console. Use the Log Analyzer tool there. In cases in which transferring the file is impractical or inconvenient, an alternate tool named "showlog" is provided for viewing the activity.log file:
Syntax examples:
|
| ||||||||||||||||||||||||||||||||||||||||||||||
|