Legacy: JBoss probes and sensors

  • Release version: Washingtondc
  • Updated February 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

    This guide details the use of probes and sensors for discovering Linux and Windows JBoss application servers in ServiceNow's ITOM Visibility. This functionality is available if you upgrade your instance or is included in a new instance setup, utilizing the JBoss pattern for discovery.

    Show full answer Show less

    Key Features

    • Probes Activation: The UNIX - Active Processes and Windows - Active Processes probes identify running JBoss processes, creating records in the JBoss Application Server [cmdbciappserverjboss] table upon detection.
    • Web Application Discovery: The JBoss - Find web.xml list probe searches for web.xml files in the JBoss installation's server\default\deploy directory, populating the Web Application [cmdbciwebapplication] table with relevant data.
    • Web Service Discovery: The JBoss - Get jboss-service.xml probe retrieves the jboss-service.xml file from the server\default\conf\ directory, adding necessary records to the Web Service [cmdbciwebservice] table.

    Key Outcomes

    By utilizing these probes, ServiceNow customers can effectively identify and catalog JBoss application servers and their associated web applications and services. This enhances visibility into their IT operations and aids in managing and optimizing application performance within their environments.

    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.