To capture resource monitoring
data from Apache HTTP Server, you must configure the data source.
Before you begin
The Java™ Management
Extensions must be configured on the server that is running Apache
HTTP Server. After installing Apache HTTP Server on Microsoft Windows, run the Configure Tomcat shortcut.
On Linux, run the configuration
script. Click the Java tab, and then edit the Java Options. The following lines are sample Java options:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8880
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Then, restart
Apache HTTP Server.
Procedure
- On the Location page, specify the
connection and authentication information for the server that runs
Apache HTTP Server. If you have to change the port that is used to
communicate with the server, change the information in Connection. Typically, your Apache HTTP Server system
administrator specifies this information. The port number must match
the port that you specified when configuring Java Management Extensions on the server.
- If administrative security is enabled on the server, select Administrative security enabled.
- Type the user ID and password for Apache HTTP Server
in Authentication.
- Select Save Password to save
your password locally. If you do not save your password, you might
be prompted for it (depending on the host system configuration) when
you edit the configured location or when you run test schedules that
use the location.
- On the Resource page, select the type
of data to capture. The tree view shows the counter groups and counters
that are available from the application server. Be selective; monitoring
all possible resource data requires substantial amounts of memory.
Hold your mouse pointer over a counter to see details about what the
counter measures.
- Configure the options on the Options page.
- Click Reset counters at start of run (client
side reset only) to set the counters to 0 at the start
of a schedule run. This does not change the actual values of the counters
on the application server. Instead, the recorded values of the counters
are corrected to start at 0.
- In Polling Interval, specify
in seconds the interval for collecting resource data. For example,
if you accept the default setting of 5 seconds, counter information
is collected at 5-second intervals from the specified host during
the schedule run.
- In Timeout Interval specify in
seconds the time to wait for a response. If the resource monitoring
host does not respond within this amount of time during a schedule
run, an error is logged.