Legacy: JBoss probes and sensors

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Legacy: JBoss probes and sensors

    This content explains how ServiceNow Discovery identifies and collects configuration data from JBoss application servers running on Linux and Windows systems using legacy probes and sensors. These probes are active on upgraded instances, while new instances use the JBoss pattern for discovery.

    Show full answer Show less

    Key Features

    • Process Detection: The UNIX - Active Processes (Linux) and Windows - Active Processes probes detect running JBoss server processes by matching the org.jboss.main entry point parameter. Upon detection, a record is created in the JBoss Application Server [cmdbciappserverjboss] table.
    • Web Application Identification: The JBoss - Find web.xml list probe searches for web.xml files within the JBoss installation directory (server\default\deploy), based on the classpath of the running process. For each web application found, it triggers the JBoss - Get web.xml probe to read the web.xml contents.
    • Service Data Collection: The JBoss - Get web.xml probe’s sensor populates detailed information into the Web Application [cmdbciwebapplication] and Web Service [cmdbciwebservice] tables.
    • Configuration File Parsing: The JBoss - Get jboss-service.xml probe uses the classpath parameter to locate the jboss-service.xml file in the server\default\conf\ directory. If found, its contents are read by the sensor, which then creates further records in the Web Service [cmdbciwebservice] table.

    Practical Implications for ServiceNow Customers

    This discovery process enables ServiceNow customers to automatically identify JBoss application servers running on their Linux or Windows infrastructure and collect detailed configuration data about associated web applications and services. By leveraging these probes and sensors, customers can maintain an accurate and comprehensive CMDB for JBoss environments, facilitating improved asset management and operational insight.

    Discovery identifies a Linux JBoss application server using probes and sensors.

    Linux

    This process describes the use of probes, which are active on your instance if you upgrade. For new instances, Discovery uses the JBoss pattern.

    1. The UNIX - Active Processes probe detects a running process that matches an org.jboss.main entry point parameter.
    2. If there’s a match, a record is created in the JBoss Application Server [cmdb_ci_app_server_jboss] table. The following probes are also triggered:
      • JBoss - Find web.xml list: The sensor of this probe populates information in the Web Application [cmdb_ci_web_application] table if applicable.
      • JBoss - Get jboss-service.xml: The sensor of this probe populates information in the Web Service [cmdb_ci_web_service] table.
    3. The JBoss - Find web.xml list probe searches for the web.xml files of JBoss application server. The probe uses the classpath parameter in the running process, and then searches in the related server\default\deploy directory for the JBoss installation.
    4. If associated web applications reside in the server\default\deploy directory, the JBoss - Get web.xml probe triggers for each application. This probe reads the web.xml file for each web application and the sensor populates additional information to the Web Service [cmdb_ci_web_service] table.
    5. The Boss - Get jboss-service.xml probe uses the classpath parameter in the running process to search for the jboss-service.xml file in the related server\default\conf\ directory for the JBoss installation.
    6. If the probe successfully finds the jboss-service.xml file in the server\default\conf\ directory, the sensor reads the contents of the XML file. It then creates additional records in the Web Service [cmdb_ci_web_service] table as necessary.

    Windows

    This process describes the use of probes, which are active on your instance if you upgrade. For new instances, Discovery uses the JBoss pattern.

    1. The Windows - Active Processes probe detects a running process that matches an org.jboss.main entry point parameter.
    2. If there’s a match, a record is created in the JBoss Application Server [cmdb_ci_app_server_jboss] table. The following probes are also triggered:
      • JBoss - Find web.xml list: The sensor of this probe populates information in the Web Application [cmdb_ci_web_application] table if applicable.
      • JBoss - Get jboss-service.xml: The sensor of this probe populates information in the Web Service [cmdb_ci_web_service] table.
    3. The JBoss - Find web.xml list probe searches for the web.xml files of JBoss application server. The probe uses the classpath parameter in the running process, and then searches in the related server\default\deploy directory for the JBoss installation.
    4. If associated web applications reside in the server\default\deploy directory, the JBoss - Get web.xml probe triggers for each application. This probe reads the web.xml file for each web application and the sensor populates additional information to the Web Service [cmdb_ci_web_service] table.
    5. The Boss - Get jboss-service.xml probe uses the classpath parameter in the running process to search for the jboss-service.xml file in the related server\default\conf\ directory for the JBoss installation.
    6. If the probe successfully finds the jboss-service.xml file in the server\default\conf\ directory, the sensor reads the contents of the XML file. It then creates additional records in the Web Service [cmdb_ci_web_service] table as necessary.