MID Server configuration for Service Mapping

Configure Service Mapping and MID Servers to work together.

MID Servers, which are located in the enterprise private network, facilitate communication between servers on the network and some ServiceNow applications, such as Service Mapping, Discovery, and Service Analytics .

The number of MID Servers that you require and where you place them depends on your organization needs. If you want to map devices and applications inside your private network, place the MID Servers inside the private network. If you want to map devices and applications located in the DMZ, place the MID Servers both in the DMZ and inside the private network.

In Service Mapping, devices and applications are referred to as configuration items (CIs).



In deployments where domain separation is enabled and domains are configured to form a hierarchy, MID Servers must be placed in the lowest domain level, a "leaf domain."


For every discovery request, Service Mapping selects a MID Server and assigns the request to it. Service Mapping selects MID Servers as follows:
  • You can narrow the pool of MID Servers that Service Mapping uses. In that case, Service Mapping uses only MID Servers configured to work with it and ignores the rest.
  • By default, Service Mapping selects the MID Server whose IP range matches the IP in the discovery request.
  • If Service Mapping cannot find a MID Server with the matching IP range, it assigns the discovery request to the default MID Server.
  • If there is no default MID Server and none of the MID Servers have IP ranges configured for them, Service Mapping uses a random MID Server.
  • If there is no default MID Server and no IP range matches the IP in the discovery request, Service Mapping cannot start the discovery process.

Once MID Servers are installed, configure them to work with Service Mapping and ensure the best discovery results. Perform the following configurations: