---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# IBM WebSphere Application Server

# IBM WebSphere Application Server discovery using patterns {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 IBM WebSphere Application Server discovery using patterns

The Discovery and Service Mapping Patterns application in ServiceNow uses specific patterns---Websphere On Windows and Websphere On Unix---to identify and classify IBM WebSphere Application Servers running on Windows and Linux systems.
Starting with Visibility Content version 6.1.0, pattern-based discovery is the default method, replacing the older probe-based approach.
This discovery populates comprehensive configuration data into the CMDB, enabling better visibility and management of WebSphere environments.
Show full answer Show less  

## Prerequisites and Setup

To successfully discover IBM WebSphere Application Servers, ensure the following:

* **Applications:** Keep the Discovery and Service Mapping Patterns and Visibility Content applications up to date.
* **Windows Discovery:** Enable PowerShell on the MID Server, verify access to key installation and configuration files (such as versionInfo.bat, application.xml, server.xml), and create appropriate Windows credentials.
* **Linux Discovery:** Enable SSH access on the WebSphere server, verify access to critical files (like versionInfo.sh, application.xml, server.xml), create SSH credentials, and ensure elevated rights for executing WebSphere commands.
* **Horizontal Discovery:** Schedule horizontal discovery scans to trigger the identification of WebSphere servers using the respective patterns.

## Data Collected and CMDB Impact

The discovery process collects detailed information about WebSphere components, including:

* **IBM WebSphere Application Server:** Name, version, node grouping, and cell grouping information.
* **Websphere EAR files:** Names and installation directories of enterprise application archives.
* **Web Services:** Names, service IDs, and additional attributes.
* **WebSphere Cells:** Cell names, IDs, types, discovery protocols, and descriptions (Linux only).

## CI Relationships Created

Discovery establishes key relationships within the CMDB to accurately represent the WebSphere environment:

* WebSphere Application Servers are contained by WebSphere Cells.
* WebSphere EAR files are contained by WebSphere Application Servers.
* Web Services run on WebSphere Application Servers.

These relationships support comprehensive service mapping and impact analysis within ServiceNow.  
The Discovery and Service Mapping Patterns application uses the Websphere On Windows and Websphere On Unix patterns to find IBM WebSphere Application Servers. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
The IBM WebSphere Application Server is a software framework with middleware that hosts Java-based web applications. Discovery identifies and classifies information about the IBM WebSphere Application Server on both Windows and Linux computers.  
Note:  
Starting with Visibility Content version 6.1.0, pattern-based discovery is the default method for discovering IBM WebSphere Application Servers. The WebSphere probes are disabled by default. For more information, see [IBM WebSphere server discovery using probes](https://www.servicenow.com/docs/907iyhPPYVyT11lcTiqiPQ "The IBM WebSphere application server is a software framework with middleware that hosts Java-based web applications. Discovery creates or updates a CMDB record when it detects an instance of a WebSphere application server running on a Windows or Linux system.").

## Request apps on the Store {#ibm-websphere-server-pattern__id_z4l_ysx_rcc}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#ibm-websphere-server-pattern__inline-send-to-store}

## Prerequisites for Windows discovery {#ibm-websphere-server-pattern__section_frv_v3w_j2c}

Verify that the following applications are up to date:
:
    * Discovery and Service Mapping Patterns
    * Visibility Content
    {#ibm-websphere-server-pattern__ul_szr_z3w_j2c}

Enable PowerShell on the MID Server
:   For more information, see [Set up MID Servers to use PowerShell](https://www.servicenow.com/docs/_F4TkrXWngCOkYjPgHPWRA "Configure MID Servers in your organization to use PowerShell for horizontal and top-down discovery of Windows servers.").

Verify access to files and directories
:   Verify access to the following files and directories:

    * Installation directory of the product
    * Configuration directory of the product
    * `versionInfo.bat`
    * `WAS.product`
    * `BASE.product`
    * `profile.version`
    * `Express.product`
    * `application.xml`
    * `server.xml`
    * `cell.xml`
    {#ibm-websphere-server-pattern__ul_m3r_gkw_j2c}

Create Windows credentials
:   For more information, see [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US).

Schedule a horizontal discovery
:   For more information, see [Schedule a horizontal discovery](https://www.servicenow.com/docs/VO0owNull6HAfXGFWMKxhg#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").

## Prerequisites for Linux discovery {#ibm-websphere-server-pattern__section_emm_mlw_j2c}

Verify that the following applications are up to date:
:
    * Discovery and Service Mapping Patterns
    * Visibility Content
    {#ibm-websphere-server-pattern__d15684e25950}

Enable SSH on WebSphere Application Server
:   For more information, see the "Setting up SSH on Linux or UNIX servers" article in the "WebSphere Automation" section of the IBM documentation (<https://www.ibm.com/docs/en/products>).

Verify access to files and directories
:   Verify access to the following files and directories:

    * Installation directory of the product
    * Configuration directory of the product
    * `oeconsol`
    * `WAS_HOME`
    * `CONFIG_ROOT`
    * `versionInfo.sh`
    * `WAS.product`
    * `BASE.product`
    * `profile.version`
    * `Express.product`
    * `application.xml`
    * `server.xml`
    * `cell.xml`
    {#ibm-websphere-server-pattern__ul_nhr_tlw_j2c}

Create SSH credentials
:   For more information, see [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US).

Verify elevated rights for IBM WebSphere Application Server commands
:   For more information, see IBM WebSphere Application Server (on UNIX) table in [Service Mapping commands requiring a privileged user](https://www.servicenow.com/docs/fMLKP9ztw9H4ZPck4RnumQ "Service Mapping uses commands requiring elevated rights to discover and map Unix-based hosts in your organization. In addition to configuring necessary credentials, configure servers in your organization to allow Service Mapping to run these commands with elevated rights.").

Schedule a horizontal discovery
:   For more information, see [Schedule a horizontal discovery](https://www.servicenow.com/docs/VO0owNull6HAfXGFWMKxhg#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").

## Data collected by Discovery during horizontal discovery {#ibm-websphere-server-pattern__section_ok1_4mw_j2c}

Discovery populates the data in the CMDB when running the Websphere On Windows and Websphere On Unix patterns.  
{#ibm-websphere-server-pattern__table_g4r_5mw_j2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the WebSphere Application Server. |
| Version \[version\] | Current version of the WebSphere Application Server. |
| Node \[node\] | Name of the Node grouping the WebSphere Application Server or servers. |
| Cell \[cell\] | Name of the cell grouping one or more nodes of the WebSphere Application Server. |
[Table 1. IBM Websphere \[cmdb_ci_app_server_websphere\]]

{#ibm-websphere-server-pattern__table_g4r_5mw_j2c}  
{#ibm-websphere-server-pattern__table_hb5_dnw_j2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the enterprise application archive (EAR) file. |
| Installation directory \[install_directory\] | Installation directory of the EAR file. |
[Table 2. Websphere EAR \[cmdb_ci_app_server_ws_ear\]]

{#ibm-websphere-server-pattern__table_hb5_dnw_j2c}  
{#ibm-websphere-server-pattern__table_b5s_jnw_j2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the web service. |
| Service ID \[service_id\] | ID of the web service. |
| Attributes \[attributes\] | Additional attributes of the web service. |
[Table 3. Web Service \[cmdb_ci_web_service\]]

{#ibm-websphere-server-pattern__table_b5s_jnw_j2c}  
{#ibm-websphere-server-pattern__table_lsj_snw_j2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the WebSphere cell. |
| Cell ID \[cell_id\] | ID of the WebSphere cell. |
| Cell type \[cell_type\] | Type of the WebSphere cell. |
| Cell discovery protocol \[cell_discovery_protocol\] | Cell discovery protocol. |
| Description \[short_description\] | Description of the cell, if one has been provided. This field is populated in Linux discovery only. |
[Table 4. Websphere Cell \[cmdb_ci_websphere_cell\]]

{#ibm-websphere-server-pattern__table_lsj_snw_j2c}

## CI relationships {#ibm-websphere-server-pattern__section_f2r_34w_j2c}

Discovery creates these relationships to support the WebSphere Application Server discovery for both Windows and Linux systems.  
{#ibm-websphere-server-pattern__table_vqk_44w_j2c__entry__3}

| CI | Relationship | CI |
|-|-|-|
| IBM Websphere \[cmdb_ci_app_server_websphere\] | Contains::Contained by | Websphere Cell \[cmdb_ci_websphere_cell\] |
| IBM Websphere \[cmdb_ci_app_server_websphere\] | Contains::Contained by | Websphere EAR \[cmdb_ci_app_server_ws_ear\] |
| Web Service \[cmdb_ci_web_service\] | Runs on::Runs | IBM Websphere \[cmdb_ci_app_server_websphere\] |
[ ]

{#ibm-websphere-server-pattern__table_vqk_44w_j2c}

