MID Server configuration for Service Mapping in upgraded deployments
Summarize
Summary of MID Server configuration for Service Mapping in upgraded deployments
In ServiceNow deployments upgraded to Istanbul, Service Mapping utilizes a legacy algorithm to select a MID Server for discovery requests. This process is governed by specific criteria that ensure correct MID Server selection based on application type and IP range.
Show less
Key Features
- Application Configuration: MID Servers can be set to work exclusively with Service Mapping or to allow any ServiceNow application. The application parameter is automatically set to ServiceMapping during upgrades for previously configured MID Servers.
- IP Range Limitation: MID Servers can be restricted to specific IP ranges. If a discovery request's endpoint falls outside this range, that MID Server will not be selected.
- Default MID Server: You can configure a default MID Server for Service Mapping. If no matching MID Server is found, the discovery request is assigned to this default server.
Key Outcomes
Service Mapping prioritizes MID Servers based on application criteria and matching IP ranges. If no suitable MID Server is found, a random server may be used unless restrictions prevent the discovery process from starting. Upgraded deployments can also enable a new selection algorithm that incorporates additional criteria, providing flexibility in MID Server selection.
For ServiceNow deployments upgraded from earlier versions to Istanbul, Service Mapping uses the legacy algorithm to choose a MID Server for a discovery request.
- Application — defines what application a MID Server works with. Set it to Service Mapping to reserve this MID Server exclusively to Service Mapping discovery requests. Alternatively, set it to ALL to allow any ServiceNow application to use this MID Server.
In earlier releases, you could configure MID Servers to work only with Service Mapping by using the Capability parameter. If you had MID Servers with this configuration, during the upgrade to Istanbul the application parameter is automatically set to ServiceMapping for them.
- IP range — limits operation of this MID Server to this IP range. Service Mapping does not choose this MID Server for a discovery request whose endpoint is outside this IP range.
In addition to the IP range, you can configure one of the MID Servers as the default server that Service Mapping uses. For operational information, see Configure a default MID Server for Service Mapping for upgraded deployments.
- Service Mapping chooses the MID Server whose application criteria is set to ServiceMapping or to ALL.
- 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 and matching application, 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.
The new algorithm for selecting MID Servers uses an extra selection criteria: capability. It allows Service Mapping to take a network protocol into consideration. For information about updated selection criteria and the new MID Server selection algorithm, see Choose MID Server selection algorithm.
While by default Service Mapping uses the legacy algorithm in upgraded deployments, it can support both new and legacy algorithms for selecting a MID Server. If necessary, you can enable the new MID Server selection algorithm for your upgraded deployment. For more information, see Choose MID Server selection algorithm.