|Home > Documentation > Configuring and administering > Monitoring the health of the Apache Geronimo server > Monitoring components on Geronimo Server > Configuring your own Monitoring Plugin DataSource|
The basic information of the server can be captured and stored in a database that is supported by Geronimo. The Geronimo management node takes advantage of MBeans to collect the server's statistics for a given time, also called snapshots. These snapshots are all JSR-77 compatible. In this way the administrator can monitor the server status.
By default, the datasources are used to connect an Apache Derby database (the reason for this is because the default DB that Geronimo uses is also Derby). However, since the datasources are all packaged into separate plugins, anyone is able to write their own datasource deployment descriptor, package it into a plugin, and use it instead of the one provided by default.
In order to use your own database for the Monitoring Plugin you must ensure the following:
Here is the original deployment descriptor for the datasources used for the Monitoring Plugin in
META-INF/database/derby is the path of
createTables.sql packaged in tha JAR file
<geronimo_home>\repository\org\apache\geronimo\plugins\monitoring\agent-sql\<version>\agent-sql-<version>.jar, which is a dependency of the datasource.
The two gbeans at the end of the deployment descriptor is pointing to an SQL file
createTables.sql in order to create the necessary tables under the condition that they do not exist. The elements of these two tables are described as the following:
In this example, we will replace the default Apache Derby plugin datasource in Geronimo 2.2 with a DB2 Express-C one.
Before we get started to replace the monitoring plugin datasource, we should install DB2 Express-C database and its driver JAR packages on Geronimo, and then configure a DB2 Express-C datasource for Geronimo to connect to that database.
Now that we have a DB2 monitoring plugin datasource, we have to create deployment descriptors for the datasource.
db2-agent-ds.xmlbased on the default
plan.xml. You have to make the following changes to
activedb, and the DatabaseName for jdbc/ArchiveDS is
db2-mconsole-ds.xml. DatabaseName in this file is
var\config\config.xmlfor Geronimo to prevent the following modules from being launched at startup time. This can be done by adding a
Load="false"to each module. This will prevent the configuration changes below from causing conflicts.
var\config\artifact_aliases.propertiesfile to replace default modules. In this way Geronimo will load DB2 datasources at startup time instead of the default ones.
org.apache.geronimo.plugins.monitoring/mconsole-tomcat/2.2/carat startup time. This can be done by removing the
Load="false"for each module.