Chapter 11. Discovering JBoss EAP/AS 5 Servers
Most JBoss EAP/AS servers are configured in a way that allows them and their child resources to be discovered and monitored without any additional configuration. When the agent attempts to discover and then manage resources, it uses certain assumptions based on common configuration to identify and connect to those resources. If for some reason the JBoss EAP/AS server has configuration that differs from those assumptions, then JBoss ON may not be able to manage that system fully.
This section describes configuration settings that are required to discover or manage certain JBoss EAP/AS server resource types.
11.1. Discovering and Managing the JBoss AS/EAP 5 JVM
For the JBoss ON agent to discover the JVM resource and its subsystems (such as memory, threading, and logging) for a JBoss EAP resource, the JBoss EAP instance must be configured to use the platform MBean server as the location where it registers its MBeans.
If necessary, edit the JBoss EAP/AS server start script so that it uses the platform MBean server.
- Open the
run.conffile. For example, on Red Hat Enterprise Linux:[root@server ~]# vim jbossInstallDir/bin/run.conf
- Add the
JAVA_OPTSsettings to use the platform MBean server.On Red Hat Enterprise Linux:JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
On Windows:set JAVA_OPTS=%JAVA_OPTS% -Djboss.platform.mbeanserver
- Restart the JBoss EAP/AS server.
