Menu Close

WLhc : WebLogic CLI-based monitoring

WebLogic health checker is a basic CLI monitoring software that provides a quick and easy option to check the health of a WebLogic domain. It’s just a bunch of korn shell scripts which I developed, to wrap around the popular wlshell.


Download WLhc v1.2      Download WLhc v1.2 User Guide         

Earlier Versions:

Download WLhc v1.1      Download WLhc v1.1 User Guide         


Salient Features:

  • Monitors WebLogic Server versions 7.0, 8.1, 9.x and 10.x
  • Interactive and non-interactive modes of execution
  • Unintrusive, external monitoring: No application is required to be deployed on the WebLogic Server being monitored and no server restart required.
  • Interactive execution provides a well-formatted dashboard of current runtime values of monitored parameters
  • Non-interactive execution (e.g. cron) generates data files in csv format, thereby allowing graphing programs to generate graphs from the data. The data files are retained for 30 days by default and can be used for troubleshooting and trend analysis.
  • Quick and easy Re-configuration: An auxiliary script controlled by a template, facilitates rebuilding the configuration file for a monitored server. This script will come in handy when changes are made to a WebLogic Server and/or when you wish to monitor new parameters.
  • Auxiliary scripts obtain data on all runtime MBeans and their attributes for a specified WebLogic Server.
  • Traps can be easily configured using simple rules in configuration files
  • Traps may be enabled/disabled globally for one or more WebLogic Servers or for individual parameters
  • Clear and structured logging for alarms and errors, thereby facilitating the use of log scanners


System Requirements:

  • Korn Shell (/bin/ksh)
  • Perl
  • nawk/gawk or equivalent
  • /usr/ucb/ps (Solaris) or ps (Linux)



(1) Installation



(2) Interactive Execution


VN:F [1.9.22_1171]
Rating: +2 (from 2 votes)
Print Friendly, PDF & Email

Leave a Reply

Your email address will not be published. Required fields are marked *