---
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


---

# Identifying Windows WebLogic application servers

# Identifying Windows WebLogic application servers {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

If you are not using the Weblogic pattern, Discovery follows this process when it uses
the Windows - Active Processes or Linux - Active Processes probes.
This process describes the use of probes, which are active on your instance if you upgrade.
For new instances, Discovery uses the Weblogic pattern.  
1. The Windows - Active Processes probe or Linux - Active Processes detects a running process that matches one of the follow criteria:
   * The parameters of the process contain weblogic.Server.
   * The parameters of the process contain -Dweblogic.name.
   {#r_WeblogicProbesAndSensorsWindows__ul_hfx_2mj_p5}
2. If there is a match on one of the criteria:
   * A record is created in the BEA Weblogic \[cmdb_ci_app_server_weblogic\] table. The record is populated with the server name and TCP port, which is gathered from the running process.
   * The Windows - Weblogic - Find config.xml probe or the Linux - Weblogic - Find config.xml probe triggers. The sensor of this probe populates additional information in the BEA Weblogic \[cmdb_ci_app_server_weblogic\] record and the Web Application \[cmdb_ci_web_application\] record if applicable.
   {#r_WeblogicProbesAndSensorsWindows__ul_a2b_jmj_p5}
3. The Windows - Weblogic - Find config.xml probe or the Linux - Weblogic - Find config.xml probe attempts to find the related config.xml file for the server by:
   * Using the -Dweblogic.RootDirectory=\<path\> parameter defined in the running process.
   * \[Windows\] Searching for config.xml files under the --Dplatform.home=\<path\> parameter defined in the running process (not as efficient using the parameters of the process).
   * \[Linux\] Searching for the parent process that started the WebLogic server (only viable if the weblogic jvm was started via the startWeblogic.sh or related custom script and not the init process).
   {#r_WeblogicProbesAndSensorsWindows__ul_hd5_smj_p5}
4. If there are associated web applications found in the WebLogic config.xml file, the Windows -- Weblogic find web.xml probe triggers for each application. This probe reads the WebLogic web.xml file for each web application and the sensor, and then populates additional information.
{#r_WeblogicProbesAndSensorsWindows__ol_npp_hq5_45}