BMC Software, Inc., Confidential and Proprietary Information
4-2 PATROL for BEA WebLogic User Guide
Monitoring a WebLogic Environment
PATROL for BEA WebLogic relies on features of the PATROL Console
for much of its ability to help you improve the reliability and
performance of your WebLogic environment. Every user of PATROL for
BEA WebLogic should understand how basic Console features and
commands work together. This chapter explains how to exploit some key
PATROL features to effectively use PATROL for BEA WebLogic. If any
step seems too advanced, see the online Help for your Console by
clicking Help. The Console Help and the PATROL Event Manager Help
explain basic concepts.
Working with Parameters
When you first install PATROL for BEA WebLogic, take some time to
open windows and double-click application class icons to see parameters.
The parameters contain the actual data about your system’s performance
and configuration.
Top Parameters for BEA WebLogic
While all of the parameters in the product will probably be important to
some users at some times, only a small number are of critical importance
to almost every environment.
These parameters are the top parameters to monitor in order to assure the
availability of your WebLogic environment. BMC Software sets alarms
on many of them by default. You may also wish to monitor them through
the Event Manager and set e-mail notifications or recovery actions on
some.
•
PatrolCollectorStatus (SERVER, page B-19):
If PatrolCollectorStatus goes into alarm, PATROL is not receiving
updated data and your monitoring is offline. This and
ConnectionStatus are the two most critical parameters to assure
availability of your WebLogic environment.
