Browse Prior Art Database

Method of monitoring WebLogic Application Server

IP.com Disclosure Number: IPCOM000021207D
Original Publication Date: 2004-Jan-02
Included in the Prior Art Database: 2004-Jan-02
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Abstract

This document will describe the basic functionality of monitoring for the BEA WebLogic Application Server*.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Method of monitoring WebLogic Application Server

A program monitors the BEA WebLogic Application server. What is being monitored is the container itself, not the application deployed to the container. These monitors provide a reliable, flexible and extensible method for monitoring WebLogic.

The set of monitors dependently detect and report basic outages of the WebLogic container. The three alarm conditions were identified as:
* Failure to connect to WebLogic, due to instance being down.
* Failure to connect to WebLogic due to a locked instance.
* Failure to connect to a remote database. Additionally, the monitors are flexible and extensible. Extensible to quickly add functionality as needed. Flexibility allows the monitors to run across different operating systems and multiple versions of WebLogic.

1. Monitors are portable, across applications and operating systems, and across WebLogic versions.
2. Native WebLogic utilities are used where possible.
3. A mechanism to prevent repeated alarms is used.
4. New functionality is to add as required.
5. Conversely, functionality that is not need is easy to turn off.
6. A simple interface to Tivoli** is provided.
7. Ability to send out pages for alerts.

Monitor Design The monitors allow new functionality to be added with a minimal amount of work. Using a modular design, new functionality is added by creating a new module, then registering that module. Once the new plugin is added, the wrapper script is modified to make use of the new methods.

External configuration files control which functionality is active. The configuration file contains all information needed by the monitoring script. The monitor itself is very generic, and is called with the name of the configuration file as an argument.

Basic functionality is provided by using the following native WebLogic utilities:
* weblogic.Admin PING
* utils.t3dbping

Using wrappers around these java utilities, the previously identified three alarm conditions can be reliably tested.

Monitor Process Flow The following will detail how the monitor actually tests the alarm conditions, and sends out notification.
1. Monitor is called with the name of the configuration file to be used.

1

Page 2 of 2...