Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloud
or on-prem performance issues
|
||
|
How to Monitor JBoss Application Server Using eG Enterprise?
A JBoss application server (version 4.0 and 4.2.3) can be monitored in an agent-based or an agentless manner using eG Enterprise. Before attempting JBoss monitoring, the JBoss application server should be configured to work with the eG agent. The following sections describe how to configure a JBoss application server to work with eG agent.
Configuring the JBoss server to work with the eG Agent
To monitor the JBoss server, eG requires administrators to deploy two specialized components on the target server. These components are, the eG MBean Service component, and the eG Web Component. In order to enable the eG agents to extract statistics from the JBoss server, the above-mentioned components need to be deployed on the JBoss server. To achieve this, do the following:
Next, proceed to restart the server. Prior to this, ensure that the server can be accessed using its IP address. This is because, by default, Jboss is bound to the local host. This implies that, by default, you will not be able to pull out metrics from the JBoss server or access the resources of the server using its IP address. This default setting could cause the eG tests to fail. In order to avoid this, you will have to ensure that the JBoss server is accessible via the IP address. For that, to start/restart the server, run the following command at the command prompt of the server:
run.bat -b ip
Note:
To be effectively monitored by the eG agent, the JBoss server should be of version 4.0 or 4.2.3, and should be executing on JDK 1.5 or higher.
Configuring the eG Agent to Collect JVM-related Metrics from the JBoss server Ver. 4.0
The jvm layer of the JBoss monitoring model is associated with tests that report critical statistics related to the JBoss server’s JVM. These statistics typically reveal the following:
These tests connect to the JRE used by the JBoss application server to pull out the above-mentioned metrics. To enable the tests to collect metrics from the JRE, the eG agent executing these tests should be configured to use one of the following methodologies:
Since both JMX and SNMP support are available for JRE 1.5 and above only, these tests will work only if the JBoss server being monitored runs JRE 1.5 and above.
If the target JBoss server indeed uses JRE 1.5 (or above), then, you can proceed to use either JMX or SNMP for connecting to the JRE of the target and pulling out the desired metrics.
If you choose to use JMX for metrics, then the following broad steps need to be followed:
If JMX does not require authentication, follow the steps below:
Note:
To know how to enable SNMP support for the JRE, refer to the Monitoring Java Applications document.
If the JMX requires authentication (but no security), follow the steps below:
Edit the management.properties file that is used by the JRE of the target JBoss server, and configure the following in it:
Add the following line in it:
set JAVA_OPTS=-Dcom.sun.management.config.file=<<Path to management.properties file used by the JRE of the target JBoss server>
Then, proceed to enable the JVM-related tests, and configure them using the instructions provided in the Monitoring Java Application Servers document. To enable one/more tests, go to the ENABLE / DISABLE TESTS page using the menu sequence : Agents -> Tests -> Enable/Disable, pick JBoss as the Component type, Performance as the Test type, choose the tests from the DISABLED TESTS list, and click on the >> button to move the tests to the ENABLED TESTS list. Finally, click the Update button.
Once you have configured the JBoss application server to work with the eG agent, manage the JBoss application server component using eG administrative interface. The procedure for achieving this has been explained in Managing the JBoss Application server.