Configure monitoring with the webtierMonitorConfig.xml file

Procedure Open the webtierMonitorConfig.xml file stored in the WAR file, application sever startup directory, or on the application server classpath (allowing settings to be tailored to a machine if required). By default, the webtierMonitorConfig.xml file is stored in the .war file in the lib\mldcfg.jar file. On the ApplicationConfig tag, set the mode to one of the following: Normal Enables monitoring of all the metrics listed in the file. Disable_Alerts Enables monitoring of all the metrics listed in the file, but disables all notifications of critical events, regardless of individual notification settings on any metric. Off Disables monitoring of all the metrics listed in the file. (Optional) To be notified when criteria reaches the specified threshold, specify from whom, to whom, and how frequently email notification of critical events are sent by setting the following EmailResponder values. You can specify more than one EmailResponder id. All EmailResponder id values in all subsequent monitoring metrics in this file must match one of the EmailResponder id values set here. EmailResponder id Specify an identification for this email responder. Multiple email responders can be configured, in which case the identifiers must be unique. protocol Specify the email protocol by which notifications are sent. SMTP is the only supported protocol. hostAddress Specify the server host from which the email notifications are sent. In a large deployment (with multiple server managers, or the web tier running on different hosts) the host address identifies the location of the critical events. fromAddress Specify the address from which the notification emails are sent. toAddress Specify the address to which the notification emails are sent. You can specify multiple email addresses, separated by semicolons. suppressionPeriod Specify the amount of time (in seconds) to suppress email notification of critical events. emailFormat Specify the format in which the email is delivered. Valid values are html and text. (Optional) To be notified when criteria reaches the specified threshold, specify to which file critical events are logged by setting the following LoggerResponder values. All LoggerResponder values in all subsequent monitoring metrics in this file must match the LoggerResponder id value set here. LoggerResponder id Specify an identification for this logger responder. Multiple logger responders can be configured, in which case the identifiers must be unique. logFileName Specify the name of the file to which critical events are logged. suppressionPeriod Specify the amount of time (in seconds) to suppress logging of critical events to the log file. Configure the criteria for a critical event for any of the metrics in the file by: Specifying a particular EmailResponder. Specifying a particular LoggerResponder. Setting the metric monitoring mode to one of the following: Collect Collect metric data and display results in the server manager administrative interfaces for this metric. This is the default setting. Alert When critical events exceed the specified threshold, collect metric data, send email notifications (set up with EmailResponder values), write messages to log files (set up with LoggerResponder values), and display results in the server manager administrative interfaces for this metric. Log file messages and email notifications are only issued when monitoring mode is set to Alert. Off No metric data is collected. Setting the remaining values to specify criteria that must be met to trigger a critical event for the metric. Save the file. web tier monitoring is enabled for the metrics you configured. Note You can revise the webtierMonitorConfig.xml file and save it in the .war file before deployment by the web application. Or if you prefer, you can place the revised file directly into the root directory of the web application server’s run-time environment, and override the version of the file in the .war file. For example, on WebSphere, place it in the profile directory; or on JBoss, place it into the bin directory.