How to Discover JEE JBoss by JMX

This task includes the following steps:

1. Prerequisite - Set up protocol credentials

   This discovery uses the JBoss protocol.

   For credential information, see Supported Protocols.

2. Prerequisites - Set up drivers

   Default JBoss drivers are included by default with the Probe installation. For details on the required *.jar files, see "JBoss" in the Data Flow Management section of the UCMDB Help. The Probe installation includes JBoss drivers for versions 3.x and 4.x, but you can use your own drivers, if you prefer.

   Note (Only for JBoss 7.x versions) Due to different management modes, you need to add two folders 7.0 and 7.1 under the following directory:

   C:\UCMDB\DataFlowProbe\runtime\probeManager
   \discoveryResources\j2ee\jboss

   After upgrading CP version to CP19 or later, replace the folder 7.x with the real JBoss version. For example, if you have 7.0.x JBoss Application Server in your environment, change the folder name 7.x to 7.0. If you have both 7.0.x and 7.1.x in your environment, make sure that there are two folders 7.0 and 7.1 in the preceding directory.

   To update .jar files:

   1. Copy the drivers to the correct version folder in the following location:

      C:\UCMDB\DataFlowProbe\runtime\probeManager
      \discoveryResources\j2ee\jboss\<version_folder>
      

      Note There are errors in the commercial version of the JBoss 5.x client API (EAP). To discover EAP 5.x with authorization enabled, you must take the client drivers from a non-commercial version of 5.x.

   2. Restart the Probe before running the DFM jobs.

      For example:

      To discover JBoss 5.x versions, you need to update the driver folder

      C:\UCMDB\DataFlowProbe\runtime\probeManager
      \discoveryResources\j2ee\jboss\5.x
      

      with the jbossall-client.jar file, including all dependencies declared in it.

      Required jars can be found in the <JBOSS_5_BASE_DIR>/client/ folder.

      The jbossall-client.jar file contains a classpath reference to various client .jar files used by jboss client applications. Each of the .jar files in the following list must be available in the same directory as jbossall-client.jar. Otherwise they will not be found by the classloader.

      The classpath includes the following files:

      • commons-logging.jar

      • concurrent.jar

      • ejb3-persistence.jar

      • hibernate-annotations.jar

      • jboss-aop-client.jar

      • jboss-appclient.jar

      • jboss-aspect-jdk50-client.jar

      • jboss-client.jar

      • jboss-common-core.jar

      • jboss-deployers-client-spi.jar

      • jboss-deployers-client.jar

      • jboss-deployers-core-spi.jar

      • jboss-deployers-core.jar

      • jboss-deployment.jar

      • jboss-ejb3-common-client.jar

      • jboss-ejb3-core-client.jar

      • jboss-ejb3-ext-api.jar

      • jboss-ejb3-proxy-client.jar

      • jboss-ejb3-proxy-clustered-client.jar

      • jboss-ejb3-security-client.jar

      • jboss-ha-client.jar

      • jboss-ha-legacy-client.jar

      • jboss-iiop-client.jar

      • jboss-integration.jar

      • jboss-j2se.jar

      • jboss-javaee.jar

      • jboss-jsr77-client.jar

      • jboss-logging-jdk.jar

      • jboss-logging-log4j.jar

      • jboss-logging-spi.jar

      • jboss-main-client.jar

      • jboss-mdr.jar

      • jboss-messaging-client.jar

      • jboss-remoting.jar

      • jboss-security-spi.jar

      • jboss-serialization.jar

      • jboss-srp-client.jar

      • jboss-system-client.jar

      • jboss-system-jmx-client.jar

      • jbosscx-client.jar

      • jbosssx-as-client.jar

      • jbosssx-client.jar

      • jmx-client.jar

      • jmx-invoker-adaptor-client.jar

      • jnp-client.jar

      • slf4j-api.jar

      • slf4j-jboss-logging.jar

      • xmlsec.jar

3. Run the discovery

   Run the following jobs in the following order:

   For details on running jobs, refer to "Module/Job-Based Discovery" in the Data Flow Management section of the UCMDB Help.

   • Run the Range IPs by ICMP job to discover the target IPs.

   • Run the JEE TCP Ports job to discover service endpoint information. For job details, see JEE TCP Ports Job.

   • Run the JEE JBoss Connections by JMX job to perform a shallow discovery of application servers. For job details, see JEE JBoss Connections by JMX Job.

   • Run the JEE JBoss by JMX job to perform a deep discovery of JBoss application server topology. For job details, see JEE JBoss by JMX Job.