WebLogic application server discovery

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 WebLogic application server discovery

    This discovery process creates or updates Configuration Management Database (CMDB) records when it detects Oracle or BEA WebLogic application servers running on Windows or Linux systems. It enables ServiceNow customers to maintain accurate and current records of WebLogic servers and associated web applications in their CMDB, facilitating better asset and service management.

    Show full answer Show less

    Requirements

    • Windows: PowerShell must be enabled on the MID Server. WebLogic Administration Server instances started via WebLogic NodeManager require the -Dweblogic.RootDirectory=<path> parameter at startup. Windows credentials need read permissions on the config.xml file.
    • Linux: Discovery uses Bourne shell commands (find, cat, dirname). AdminServer instances must also start with the -Dweblogic.RootDirectory=<path> parameter visible via the Linux ps command. The SSH user requires specific sudo privileges configured in the sudoers file to run required scripts without a password.

    Credentials

    Appropriate credentials must be configured depending on the operating system:

    • Applicative credentials
    • Windows credentials
    • SSH credentials

    Discovery Components

    The discovery uses classifiers, trigger probes, and patterns:

    • Classifier and Trigger Probes: Detect WebLogic servers and initiate discovery.
    • Patterns: Windows and Linux patterns locate and extract WebLogic configuration files (config.xml, web.xml) and running process details to populate CMDB records.

    For new instances, some probes are inactive on the classifier by default. Customers must ensure the horizontal pattern probe is correctly specified on the classifier to enable pattern-based discovery.

    Data Collected

    The discovery populates the CMDB with detailed information from configuration files and running processes, including:

    • Application Server Data: Name, version, WebLogic domain, TCP ports
    • Web Application Data: Name, document base, description, servlet class/name, context path, associated app server, TCP ports

    The collected data varies slightly between Windows and Linux due to platform-specific sources.

    Relationships

    Discovery establishes key relationships in the CMDB:

    • Application servers run on Windows or Linux servers.
    • Application servers contain web applications.
    • AdminServer instances depend on managed servers they encapsulate.

    Additional Configuration

    • For Linux, sudo access must be configured for the Weblogic - Find config.xml probe if not using patterns.
    • When not using patterns, discovery employs active process probes on Windows and Linux to identify WebLogic servers.

    Practical Impact for ServiceNow Customers

    Implementing this discovery enables accurate detection and detailed mapping of WebLogic application servers and web applications in the CMDB. This supports improved visibility, impact analysis, and management of WebLogic environments across Windows and Linux platforms. Proper credential and configuration setup are essential to ensure successful discovery and data accuracy.

    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

    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 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
    Note:
    For information on Probe to Pattern migration see the knowledge article KB0694477.

    Credentials

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

    Relationship

    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