Bootstrap FreeKB - IBM WebSphere - HPEL logs (logViewer command)
IBM WebSphere - HPEL logs (logViewer command)

Updated:   |  IBM WebSphere articles

The High Performance Extensibility Logs (HPEL) can be viewed in the WebSphere admin console or on the command line. To view the HPEL logs in the admin console, navigate to Troubleshooting > Logs and trace > select a server or node agent > View HPEL logs and trace. To view the HPEL logs on the command line, you can use any text editor to view the text.log. The LogViewer command must be used to view the HPEL log and HPEL trace log, because these logs are in binary format.

  • logViewer.bat (Windows) 
  • (Linux WAS)
  • logViewer (Linux Liberty) 


If you attempt to run the logViewer command outside of the profile directory, such as was_home/bin/, the -repositoryDir option must be included.

~]# was_home/bin/ -repositoryDir was_home/profiles/your_profile/logs/your_app_server/


It is usually much easier to run the logViewer command from the profile directory.

~]# was_home/profiles/profile01/bin/
[3/14/18 20:13:23:123 CDT] 0000009f ServletWrappe I init SRV0242EI: [Beta_war] [/beta] [com.main.servlet.Results]: Initialization successful. 


Watch the log in real time

The -monitor option can be used to watch event written to the log in real time.

~]# was_home/profile/your_profile/bin/ -monitor


Redirect to text file

The -outLog option can be used to redirect the output of the logViewer command to a text file. Keep in mind that if you have not disabled the HPEL text log, the text.log should contain the same events as being produced by logViewer, so there are situations where you don't necessarily have to use the -outLog option.

~]# was_home/profile/your_profile/bin/ -outLog /tmp/file1.txt


Filter date and time

The -startDate and -stopDate option can be used to filter the log to only show events in a certain date and time range.

~]# was_home/profile/your_profile/bin/ -startDate "01/01/2018 09:00:00:000 CDT" -stopDate "01/01/2018 10:00:00:000 CDT"


Set log level


The -level option can be used to only display events at a certain log level.

~]# was_home/profile/your_profile/bin/ -level FINE



The -minLevel and -maxLevel options can be used to specify the minimum and maximum log level, so that only events within certain log level are displayed.

~]# was_home/profile/your_profile/bin/ -minLevel WARNING -maxLevel INFO

Did you find this article helpful?

If so, consider buying me a coffee over at Buy Me A Coffee


March 12 2019 by Juan Gabriel
Hey, any ideas on how to combine/merge the log entries from multiple servers in a cluster environment into one consolidated log viewer?

March 16 2019 by Jeremy (moderator)
I don't think LogViewer has a built in option to get/merge logs from different hosts. I guess you could make an SSH connection from server "a" to servers b/c/d et cetera to get the log data and then merge them together on server "a". Probably would want to build out a custom script for this (Perl, Python, or whatever).

Add a Comment

Please enter 3e7790 in the box below so that we can be sure you are a human.