Legacy: JBoss probes and sensors

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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

    ServiceNow Discovery identifies JBoss application servers on both Linux and Windows systems using specialized probes and sensors. These components detect running JBoss processes and gather detailed configuration data to populate relevant Configuration Management Database (CMDB) tables. For upgraded instances, these probes are active by default, while new instances use the updated JBoss pattern.

    Show full answer Show less

    Key Features

    • Process Detection: The UNIX - Active Processes (Linux) and Windows - Active Processes probes identify running JBoss servers by matching the org.jboss.main entry point parameter. When detected, a record is created in the cmdbciappserverjboss table.
    • Web Application Discovery: The JBoss - Find web.xml list probe uses the classpath from the identified process to locate the JBoss installation directory, specifically the server\default\deploy folder. It searches for web.xml files of deployed web applications. For each found application, the JBoss - Get web.xml probe reads the web.xml file and populates detailed information into the cmdbciwebapplication and cmdbciwebservice tables.
    • Web Service Configuration: The JBoss - Get jboss-service.xml probe similarly uses the classpath to locate the jboss-service.xml file in the server\default\conf\ directory. Upon finding this file, the sensor reads its contents to create or update records in the cmdbciwebservice table.

    Practical Benefits for ServiceNow Customers

    This discovery process enables accurate and automated identification of JBoss application servers and their deployed web applications and services within your CMDB. By leveraging these probes and sensors, you can maintain up-to-date, detailed configuration data for JBoss environments on both Linux and Windows platforms. This supports improved asset management, impact analysis, and operational visibility without manual effort.

    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.