Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

WebLogic application server discovery

Log in to subscribe to topics and get notified when content changes.

WebLogic application server discovery

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.


For Windows
  • PowerShell 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.
For Linux
  • Discovery requires the use of these Bourne shell commands:
    • find
    • cat
    • dirname
  • 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 comfiguration 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-* * *"

    Do not make any changes to

  • 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
Warning: DO NOT switch from probes to patterns if you are already running Discovery with probes, and your CMDB is already populated. If you do so, it is possible that the pattern Discovery process does not synchronize on the same values that the probe Discovery process does. This could result in duplicate CIs in your CMDB.


Classifier, pattern, and probes

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*
*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 for instructions.

Data collected on Windows

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

Data collected on Linux

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


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.

Figure 1. Example Weblogic relationships
Example weblogic relationships