HP enhances the Open Source and Middleware Stacks (OSMS) by
using HP OpenView Operations Gallery Smart Plug-Ins (OVO SPIs).
HP OpenView Operations (OVO) is a distributed, client/server
software solution designed to provide service-driven event and performance
management of business-critical enterprise systems, applications,
and services.
The SPI for the JBoss Enterprise Application Server is a value-add
software component for HP OVO. This software is provided free to all
customers of HP OVO for use under the terms and conditions documented
on the download Web page. The SPIs provides powerful, centralized
tools to monitor and manage the operation of multiple installations
of JBoss Enterprise Application Server on RHEL5.
The SPI components include the following:
Policies that are designed to allow you to monitor
key health parameters of the JBoss Enterprise Application Server.
Policies that allow you to monitor the overall availability
of the JBoss Enterprise Application Server.
Tools that let you run commands on the managed JBoss
Enterprise Application Server installation.
 |
| |
|
 | NOTE: The HP OVO Management Server runs on either HP-UX or Windows.
For the examples in this blueprint, HP OpenView Operations for Windows
(OVOW) was chosen. |
|
| |
|
Figure 24 displays the SPI
architecture and OVOW components.
Software Prerequisites and Reference Guides |
|
Before attempting to install the JBoss SPI, verify that you
have a functional HP OVOW 7.5 installation, including an HP OVOW Management
Console and the Linux OVO SPI agents for the JBoss Enterprise Application
Server. In addition, the following OVOW patches are required:
Table 2 Required Patches
| Patch Description | Version | Patch Name | Dependencies |
|---|
| Agent Linux patch | A.07.33 | OVOW_00234 | OVOW_00166 |
| Mgmt Server/Console patch | A.07.50 | OVOW_00244 | n/a |
The SPI installation and configuration documents can be found
on the HP OpenView website located at:
http://managementsoftware.hp.com/products/spi/
For information about installing the HP OVOW agent, see the HP OpenView Operations for Windows Installation Guide located at:
http://ovweb.external.hp.com/ovnsmdps/pdf/ovow75_install.pdf
Using the SPIs |
|
The OVOW SPIs support two methodologies to manage the JBoss
Enterprise Application Server:
User-Driven Methods
The user-driven functions are accessed from the Tools menu.
You can start, stop, and monitor JBoss from the OVOW console. The
following table provides an overview of the tools in this group:
Table 3 Application Labels and Descriptions
| Application Label | Description |
| Configure JBoss Instrumentation | Create
the JBoss SPI directory and configurations files and libraries required
by the SPI. |
| Shutddown JBoss Enterprise Application Server | Shutdown the JBoss Enterprise Application Server on a managed
node. |
| Start JBoss Server | Start the JBoss Enterprise
Application Server on a managed node. |
| Start Log Monitoring of JBoss Enterprise Application Server | Start the log file monitoring of the JBoss Enterprise Application
Server. The tool monitors errors, deployment exceptions, and JBoss
resource exceptions from the default JBoss log file (located in $JBOSS-HOME/server/default/log/server.log). The OVOW management
console shows all the log files mentioned in the active message window. |
| Stop Log Monitoring of JBoss Enterprise Application Server | Stop the log file monitoring of the JBoss Enterprise Application
Server. |
Event-Driven Methods
The event-driven methods are used to manage events that are
triggered when certain conditions are met, for example, if the JBoss
Enterprise Application Server process uses a greater percentage of
CPU bandwidth than the threshold defined in the policy. When a threshold
is exceeded, warning messages appear in the management console. Table 4 lists the JBoss
SPI policy details.
Table 4 JBoss SPI Policies
| Policy Name | Policy Type | Description | Default Polling Interval | Default Threshold |
|---|
| CPU - JBoss SPI | Measurement Threshold | Monitors the CPU usage of the JBoss Enterprise Application
Server. By default, if the CPU utilization percentage of any JBoss
process exceeds 90%, a critical message is displayed in an active
message browser of the OVOW console. | 5 minutes | 90% |
| Memory Usage Monitor - JBoss SPI | Measurement
Threshold | Monitors the memory usage of the JBoss Enterprise
Application Server. By default, if the memory utilization percentage
of any JBoss process exceeds 90%, a critical message is displayed
in active message browser of the OVOW console. | 5 minutes | 90% |
| Process Monitor - JBoss SPI | Scheduled Task | Monitors the JBoss processes. If a JBoss process is killed,
then a message is displayed in an active message browser of the OVOW
console. | 1 minute | — |
| Status Message - JBoss SPI | Open Message
Interface | Provides an interface for displaying JBoss
Enterprise Application Server error messages. The Open Message Interface
policies are used by other policies and are not used directly for
monitoring. | 5 minutes | — |
| Internal Message - JBoss SPI | Open Message
Interface | Interface for displaying internal error messages
from the SPI. The Open Message interface policies are used by other
policies and are not used directly for monitoring. | — | — |
| Log Message - JBoss SPI | Open Message Interface | Interface for displaying log messages of the JBoss Enterprise
Application Server. The Open Message interface policies are used by
other policies and are not used directly for monitoring. | — | — |
Printable version
