WebLogic application server discovery

Release version: Australia

Updated March 12, 2026

2 minutes to read

Summarize

Summarized using AI

Summary of WebLogic Application Server Discovery

WebLogic application server discovery enables the creation or updating of Configuration Management Database (CMDB) records for Oracle or BEA WebLogic application servers on Windows or Linux systems. This functionality is essential for maintaining accurate IT asset management within ServiceNow.

Show full answer Show less

Requirements

For successful discovery, specific requirements must be met:

Windows: PowerShell must be enabled on the MID Server. The WebLogic Administration Server must have the -Dweblogic.RootDirectory= parameter defined and the Windows credential must have read permissions on the config.xml file.
Linux: Use Bourne shell commands such as find, cat, and dirname. The -Dweblogic.RootDirectory= parameter must be visible via the ps command. The sudorers file must be configured to allow certain commands to run without a password.

Credentials

Different types of credentials are required for discovery:

Applicative credentials
Windows credentials
SSH credentials

Data Collection

Discovery collects various data points for both Windows and Linux environments. Key data includes:

Windows: Name, version, WebLogic domain, TCP ports, and application details from config.xml and web.xml.
Linux: Similar data points including running processes and context paths.

Key Outcomes

This discovery process establishes relationships between different components, such as:

cmdbciappserverweblogic runs on either cmdbciwindowsserver or cmdbcilinuxserver.
cmdbciappserverweblogic contains cmdbciwebapplication.
Dependencies are defined between managed servers and their AdminServer.

By ensuring these relationships and data points are accurately recorded, ServiceNow customers can maintain a comprehensive view of their WebLogic application server environment, leading to improved management and operational efficiency.

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.