---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Configure MID Server capabilities

# Configure MID Server capabilities {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 Minuten Lesedauer

MID Server capabilities define the specific functions of a MID Server within an IP
address range, allowing an application to select the most appropriate MID Server. Configure
capabilities on MID Servers for applications like Orchestration, Cloud Management, and Service Mapping.

## Vorbereitungen

Role required: admin or sm_admin

|-|
|   |
[ ]

{#t_ConfigureCapabilities__table_u1g_ts4_nhb}

## Warum und wann dieser Vorgang ausgeführt wird

Several applications use capabilities, IP ranges, and [MID Server selection](https://servicenow-prod.fluidtopics.net/mrx4cQ9hAtMgiweuFR2raw "You can configure MID Server selection by application, IP address ranges, network capability, or behavior. Specific MID Servers can be assigned to particular tasks, or the MID Server can be selected automatically. MID Servers can use domain separation to limit the scope of discoveries and event management.") to narrow the pool of MID Servers the applications need.  
Hinweis:  
At least one capability is required for each MID Server used by Orchestration. See [MID Servers for Orchestration](https://servicenow-prod.fluidtopics.net/94oxmXIsVDbrJ7BgasepZA "Orchestration automatically selects an appropriate MID Server based on the capabilities that you configure in activities, the IP addresses of target devices, and the application that the MID Server is allowed to use.") for more information.  
The following capabilities are available by default with Discovery:

|-|-|-|
| All | IBM | Resolve DNS |
| Ansible | JDBC | REST |
| AWS | NetApp | SNMP |
| Azure | Nmap | SOAP |
| Chef | OpenStack | SSH |
| Cloud Management | PowerShell | VMware |
| Google | RCA | WMI |
[ ]

{#t_ConfigureCapabilities__table_mqg_wkg_f3b}

## Prozedur

1. Navigate to AllMID ServerCapabilities.
2. Select an existing capability or select ALL to include all capabilities.  
   Hinweis:  
   Ensure that each IP address range has MID Servers with the necessary capabilities to complete the Orchestration activities on that network segment.
3. Create a new capability:
   1. Select New. {#t_ConfigureCapabilities__cmd_substepa}
   2. Configure the value for a custom capability.  
      An example is a capability for DOMAIN, with a value of service-now. {#t_ConfigureCapabilities__cmd_substepb}
   3. Select Submit. {#t_ConfigureCapabilities__cmd_substepc}
   {#t_ConfigureCapabilities__substeps_tlb_gf1_3v}
4. Select Edit in the MID Servers related list to add MID Servers to the capability. {#t_ConfigureCapabilities__step_step4}
{#t_ConfigureCapabilities__step_step4}
5. Select one or more MID Servers for this capability from the Available list. {#t_ConfigureCapabilities__step_step5}
{#t_ConfigureCapabilities__step_step5}
6. Select Save.  
   The capability defined here also appears in the primary record for this MID Server.
   {#t_ConfigureCapabilities__step_step6}
{#t_ConfigureCapabilities__step_step6}

## MID Server capabilities {#ariaid-title2}

MID Server capabilities define the specific functions of a MID Server within an IP address range.{#r_MIDServerCapabilities__ph_short-desc}

### Nmap capability {#r_MIDServerCapabilities__section_gfp_mwr_t1b}

The Nmap capability is only assigned to MID Servers for which the
Network Mapper (Nmap) scanner has been installed for [credential-less Discovery](https://www.servicenow.com/docs/access?context=nmap-credential-less-discovery&version=australia&pubname=australia-it-operations-management&ft:locale=en-US). This
capability cannot be added to or removed from any MID Server manually. For instructions on
installing or uninstalling Nmap, see [Install and uninstall Nmap on a MID Server](https://servicenow-prod.fluidtopics.net/F53CvqspHzIUkvBbs3xNmA#install-nmap-on-mid-server "If you decide to use credential-less Discovery in your network, you must install Nmap on each Windows MID Server that you want to use for this purpose. Self-hosted customers whose network security does not permit downloads from install.service-now.com must use a specific manual process to install and configure Nmap.")

### MID Server capability values {#r_MIDServerCapabilities__section_xyd_n3v_s1b}

Capabilities provided in the base system do not have a defined value string. The capability
value can be blank, a single value, or a \* (wildcard). A MID Server configured to use a
capability that has no value can locate any device using that capability's protocol. If a
capability has a defined value, the MID Server using that capability finds only those
devices using that protocol that match the value string exactly. The exception to this is
the Resolve DNS capability, which is configured to resolve any DNS name into an IP address
using a partial string match. The \* (wildcard) will match a request capability specifying
any non-blank value.

Starting with the Madrid release, the \[capability name\]:\[value\]
combination appears in the slushbucket when you add a capability to a MID Server. This
combination allows you to see all the capabilities that have different values, even if the
capability name is the same. For example, if you are using the Cloud Management capability,
and you use the value field to specify the us-west logical datacenter on one of the
capability records, you can see the combination in the Collection
list.

### MID Server selection {#r_MIDServerCapabilities__section_jdr_znl_cmb}

The MID Server is selected using an algorithm based on the capabilities available. The selector produces a list of suitable MIDs using filters in the following order: server statusapplicationsIP rangecapabilities. The algorithm searches the capabilities in the following sequence and, if a step finds at least one MID server, the remaining steps are skipped:

1. Exact value match: Find each MID Server containing capabilities with name/value pairs with an exact match to all requested capability name/value pairs. Blank is a valid value. \* (wildcard) values are ignored.
2. Wildcard value match: The same as an exact value match, but also allows a non-blank request value to match MID server capability records containing value \*.
3. Special capability name ALL: Find each MID Server containing the special capability name ALL, ignoring capability's value field.

{#r_MIDServerCapabilities__ol_ykk_b4l_cmb}  
Hinweis:  
If the requested capability name does not exist in the ecc_agent_capability table, BadArgumentException is thrown rather than falling back to the ALL capability.

### Scripted MID Server capability value matching {#r_MIDServerCapabilities__scripted-mid}

You can use value tests to create capabilities that find devices
using values without requiring exact string matching. Action on these values is controlled
by a user-defined script.{#r_MIDServerCapabilities__p_value-test-intro}

The Resolve DNS capability is provided in the base system and
is configured to resolve DNS names into IP addresses for devices whose names end with a
specified domain name. The capability Value entered is automatically
prefaced with a dot during processing to match domain syntax. This value can contain one or
more sub-domains, but must include the end of the domain string. Matching devices must end
with the identical syntax. The script for the Resolve DNS capability determines if a device
name matches the criteria defined by Value. If a match exists, the
platform performs the address resolution automatically. For example, if the value for the
Resolve DNS capability is `service-now.com`, the MID Server with this
capability finds lnxlab01.sandiego.service-now.com and
dbsrv101.sanjose.service-now.com. If the value is changed to
`sandiego.service-now.com`, then the MID Server finds only
lnxlab01.{#r_MIDServerCapabilities__p_resolve-dns-capability}  
Hinweis:  
If Value in the Resolve DNS capability is blank, then all domains match.

To view the script for evaluating this capability, navigate to MID ServerCapability Value Tests and select Resolve DNS from the list.