JBoss Application Server 7 sensor
The JBoss Application Server 7 sensor discovers JBoss AS configuration for JBoss AS 7.0 and later.
The sensor discovers JBoss servers that are run both as stand-alone servers and in a managed domain. Every host that belongs to a managed domain is discovered independently, so to get a full picture of a JBoss topology, a discovery must be run against each of the hosts. When an environment is discovered for the first time, it is advised to start with the discovery of a host, which acts as a JBoss domain controller, and then run a discovery of domain members.
Sensor name that is used in the GUI and logs
JBoss7Sensor
Prerequisites
An OS user that runs a discovery
must have the read access to JBoss configuration files and deployment
content. The user must also be able to run java,
otherwise the deployment descriptors are not discovered.
Limitations
- Applications and modules that are deployed to a stand-alone server by placing the deployment content in the deployments folder (file system deployments) are not discovered by the sensor. Only applications and modules that are deployed by using the JBoss AS management APIs (the command line or web interface) are supported.
- The deployment type recognition relies on searching for specific descriptor files in the deployment content. If none of these descriptors is found, a general type J2EEDeployedObject is assigned to a model object that is stored by the sensor.
Model objects created
- app.j2ee.jboss.JBossDomain
- app.j2ee.jboss.JBossHost (only for managed domains)
- app.j2ee.jboss.JBossCluster (representing server groups in a JBoss managed domain)
- app.j2ee.jboss.JBossServer
- app.ConfigFile
- app.j2ee.J2EEDeployedObject (and its subtypes)