---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# WebLogic application server

# WebLogic application server discovery {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Discovery creates or updates a CMDB record when it detects an instance of an Oracle or BEA Weblogic application server running on a Windows or Linux system.

## Requirements {#c_DataCollDiscoWebLogicServers__section_zbl_2mn_lbb}

For Windows
:
    * [PowerShell](https://servicenow-prod.fluidtopics.net/RJXf1FeJFcq_O4ssbB016A "Configure MID Servers in your organization to use PowerShell for horizontal and top-down discovery of Windows servers.") must be enabled on the MID Server.
    * The WebLogic Administration Server instances that start via WebLogic NodeManager must have the -Dweblogic.RootDirectory=\<path\> parameter defined upon server startup. The Windows credential must also have read permissions on the config.xml file.
    {#c_DataCollDiscoWebLogicServers__ul_alz_4mn_lbb}

For Linux
:
    * Discovery requires the use of these Bourne shell commands:
      * `find`
      * `cat`
      * `dirname`
      {#c_DataCollDiscoWebLogicServers__ul_e4w_jmn_lbb}
    * WebLogic administration server instances started via NodeManager must have the -Dweblogic.RootDirectory=\<path\> parameter defined and visible through the Linux ps process stat command (for each AdminServer) for the rest of the Linux WebLogic application server and web application information to be populated in the CMDB.
    * The following configuration must be set on the sudorers file:`User ALL=(root)
      NOPASSWD: /bin/sh *`

      `User` is the user name on the SSH
      credential that you create for this discovery.
    * This command must be able to be run:`/bin/sh /tmp/snc-*-findcat.sh *
      *"`

      Do not make any changes to `findcat.sh`.
    * If you are using probes, not patterns, for Weblogic discovery, the Linux - Weblogic - Find config.xml probe must specify this parameter and value: must_sudo `=` true
{#c_DataCollDiscoWebLogicServers__ul_e54_3mn_lbb}  
Hinweis:  
For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477).

## Credentials

* [Applicative credentials](https://www.servicenow.com/docs/access?context=applicative-creds&version=australia&pubname=australia-platform-security&ft:locale=en-US)
* [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US)
* [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US)
{#c_DataCollDiscoWebLogicServers__ul_zqs_nkf_kcb}

## Classifier, pattern, and probes {#c_DataCollDiscoWebLogicServers__section_dfh_vvm_rz}

{#c_DataCollDiscoWebLogicServers__table_fzd_2yv_jz__entry__3}

| Classifier | Trigger probes | Pattern |
|-|-|-|
| Weblogic Server | * Horizontal Pattern: launches patterns * Windows - Weblogic - Get web.xml\* * Windows - Weblogic - Find config.xml\* * Linux - Weblogic - Find config.xml\* {#c_DataCollDiscoWebLogicServers__ul_ixv_myv_jz} | WebLogic |
[ ]

{#c_DataCollDiscoWebLogicServers__table_fzd_2yv_jz}\*For new instances, these probes are inactive on the classifier. Discovery uses patterns for discovery.

To use patterns, verify that the correct pattern is specified in the horizontal pattern probe on the classifier. See [Add the Horizontal Pattern probe to a classifier](https://servicenow-prod.fluidtopics.net/lq7dwcGPzgHCi~AZFOJBIA#t_AddHorizontalPatternProbe "To use a pattern for the identification and exploration phases of horizontal discovery, you must add the Horizontal Pattern probe to the classifiers for the CIs are you trying to discover.") for instructions.

## Data collected on Windows {#c_DataCollDiscoWebLogicServers__section_zjq_qvn_lbb}

{#c_DataCollDiscoWebLogicServers__table_pqt_bwn_lbb__entry__4}

| Label | Table Name | Field Name | Source |
|-|-|-|-|
| Name | cmdb_ci_app_server_weblogic | name | running process |
| Version | cmdb_ci_app_server_weblogic | version | config.xml |
| Weblogic domain | cmdb_ci_app_server_weblogic | weblogic_domain | config.xml |
| TCP port(s) | cmdb_ci_app_server_weblogic | tcp_port | web.xml and running process |
| Name | cmdb_ci_web_application | name | config.xml |
| Document base | cmdb_ci_web_application | document_base | config.xml |
| Description | cmdb_ci_web_application | description | web.xml |
| Servlet class | cmdb_ci_web_application | servlet_class | web.xml |
| Servlet name | cmdb_ci_web_application | servlet_name | web.xml |
| App server | cmdb_ci_web_application | app_server | config.xml |
| TCP port(s) | cmdb_ci_web_application | tcp_port | web.xml |
[ ]

{#c_DataCollDiscoWebLogicServers__table_pqt_bwn_lbb}

## Data collected on Linux {#c_DataCollDiscoWebLogicServers__section_lyf_5wn_lbb}

{#c_DataCollDiscoWebLogicServers__table_fqn_dxn_lbb__entry__3}

| Table | Field | Source |
|-|-|-|
| cmdb_ci_app_server_weblogic | Name (name) | running process |
| cmdb_ci_app_server_weblogic | TCP port (tcp_port) | running process |
| cmdb_ci_app_server_weblogic | Version (version) | config.xml |
| cmdb_ci_app_server_weblogic | Weblogic domain (weblogic_domain) | config.xml |
| cmdb_ci_web_application | Name (name) | config.xml |
| cmdb_ci_web_application | Context path (context_path) | config.xml |
| cmdb_ci_web_application | App server (app_server) | config.xml |
[ ]

{#c_DataCollDiscoWebLogicServers__table_fqn_dxn_lbb}

## Relationship {#c_DataCollDiscoWebLogicServers__section_m31_kxn_lbb}

{#c_DataCollDiscoWebLogicServers__table_wnk_3nw_wtb__entry__3}

| Parent class | Relationship type | Child class |
|-|-|-|
| cmdb_ci_app_server_weblogic | Runs on::Runs | cmdb_ci_windows_server or cmdb_ci_linux_server |
| cmdb_ci_app_server_weblogic | Contains::Contained by | cmdb_ci_web_application |
| cmdb_ci_app_server_weblogic | Depends on::Used by | cmdb_ci_app_server_weblogic This relationship is made between an AdminServer and any managed servers it encapsulates. |
[ ]

{#c_DataCollDiscoWebLogicServers__table_wnk_3nw_wtb}  
Abbildung : 1. Example Weblogic relationships
* **[Add sudo access for the Weblogic - Find config.xml probe](https://servicenow-prod.fluidtopics.net/6Je06AMXjgWN5UiR6RYCKg)**   
  If you are not using the Weblogic pattern, you can add sudo privileges to the Linux, the Weblogic - Find config.xml probe.
* **[Identifying Windows WebLogic application servers](https://servicenow-prod.fluidtopics.net/mH66yNR_RO56JA~wVu39SA)**   
  If you are not using the Weblogic pattern, Discovery follows this process when it uses the Windows - Active Processes or Linux - Active Processes probes.