Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

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.

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

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

LabelTable NameField NameSource
Namecmdb_ci_app_server_weblogicnamerunning process
Versioncmdb_ci_app_server_weblogicversionconfig.xml
Weblogic domaincmdb_ci_app_server_weblogicweblogic_domainconfig.xml
TCP port(s)cmdb_ci_app_server_weblogictcp_portweb.xml and running process
Namecmdb_ci_web_applicationnameconfig.xml
Document basecmdb_ci_web_applicationdocument_baseconfig.xml
Descriptioncmdb_ci_web_applicationdescriptionweb.xml
Servlet classcmdb_ci_web_applicationservlet_classweb.xml
Servlet namecmdb_ci_web_applicationservlet_nameweb.xml
App servercmdb_ci_web_applicationapp_serverconfig.xml
TCP port(s)cmdb_ci_web_applicationtcp_portweb.xml

Data collected on Linux

TableFieldSource
cmdb_ci_app_server_weblogicName (name)running process
cmdb_ci_app_server_weblogicTCP port (tcp_port)running process
cmdb_ci_app_server_weblogicVersion (version)config.xml
cmdb_ci_app_server_weblogicWeblogic domain (weblogic_domain)config.xml
cmdb_ci_web_applicationName (name)config.xml
cmdb_ci_web_applicationContext path (context_path)config.xml
cmdb_ci_web_applicationApp server (app_server)config.xml

Relationship

Parent classRelationship typeChild class
cmdb\_ci\_app\_server\_weblogicRuns on::Runscmdb\_ci\_windows\_server or cmdb\_ci\_linux\_server
cmdb\_ci\_app\_server\_weblogicContains::Contained bycmdb\_ci\_web\_application
cmdb\_ci\_app\_server\_weblogicDepends on::Used bycmdb\_ci\_app\_server\_weblogicThis relationship is made between an AdminServer and any managed servers it encapsulates.
Image omitted: weblogic-relationships.png
Example weblogic relationships

Parent Topic:Software discovery