--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Legacy: JBoss probes and sensors # Legacy: JBoss probes and sensors {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 gathers configuration data for JBoss application servers on both Linux and Windows platforms using legacy probes and sensors. These probes actively detect running JBoss processes and extract relevant configuration details to populate the CMDB tables for JBoss application servers, web applications, and web services. Show full answer Show less ## Key Features * **Process Detection:** The *UNIX - Active Processes* (Linux) and *Windows - Active Processes* probes detect running JBoss processes by matching the `org.jboss.main` entry point parameter. A matching process results in creating a record in the `cmdbciappserverjboss` table. * **Web Application Discovery:** The *JBoss - Find web.xml list* probe uses the classpath from the running process to locate the `web.xml` files in the `server\default\deploy` directory of the JBoss installation. For each discovered web application, the *JBoss - Get web.xml* probe reads the `web.xml` files and populates additional details in the `cmdbciwebservice` table. * **Web Service Configuration:** The *JBoss - Get jboss-service.xml* probe searches for the `jboss-service.xml` file in the `server\default\conf\` directory using the classpath parameter. When found, its contents are read by the sensor to create or update records in the `cmdbciwebservice` table as necessary. * **Cross-Platform Consistency:** The same set of probes and sensors operate on both Linux and Windows platforms, ensuring consistent discovery and population of JBoss server and related application data. * **Legacy Probe Activation:** These legacy probes are active on upgraded instances, while new ServiceNow instances use the JBoss pattern for discovery. ## Key Outcomes * Accurate identification of JBoss application servers running on Linux and Windows systems. * Comprehensive discovery of deployed web applications and their configurations via `web.xml` files. * Detailed configuration data extraction from `jboss-service.xml` files, enriching the CMDB's web service entries. * Enables ServiceNow customers to maintain an up-to-date CMDB with detailed JBoss server, web application, and web service information for better operational visibility and management. 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. {#r_JBossProbesAndSensorsForLinux__ul_wrg_v25_45} 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. {#r_JBossProbesAndSensorsForLinux__ol_rfm_g25_45} ## Windows {#r_JBossProbesAndSensorsForLinux__section_a14_grf_bcb} 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. {#r_JBossProbesAndSensorsForLinux__d14911e145} 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. {#r_JBossProbesAndSensorsForLinux__ol_rbb_g25_45}