The Management, Instrumentation, and Discovery (MID) Server is a Java application that
runs as a Windows service or UNIX daemon on a server in your local network. The MID Server
facilitates communication and the movement of data between a ServiceNow instance and external
applications, data sources, and services.
The MID Server initiates all communications with the ServiceNow® instance. This
communication is recorded as records in the ECC Queue, which acts as the
communication log between the instance and the MID Server. The MID Server picks up any work
it has to do from the ECC Queue and returns the results of that work to the queue.
This video gives you an overview of the MID Server:
Setting up the MID server
This documentation provides detailed instructions for setting up a functioning MID Server
for use with ITOM applications. Click the icons to go to each task's portal page. These
procedures help you prepare your system, download and run the installer, and configure MID
Servers to run in your environment. After you get a valid MID Server up and running, you can
add security and encryption to protect your data.
At the bottom of each page is a link to the reference materials you need, such as
system requirements, configuration parameters, and instructions for monitoring your MID
Server. Use the additional link at the bottom to move through the content within a specific
category or return to the MID Server setup to access a different portal.
If you are new to the MID Server or an experienced user who wants to set up a MID Server
quickly, you can use the MID Server
Guided Setup. This wizard walks you through the process of installing and
configuring a MID Server with default settings in just a few steps.
Upgrading the MID Server
The MID Server checks with the instance periodically to see if an upgrade is necessary. If
the MID Server detects that a new version is available for upgrade, it downloads the
installer from install.service-now.com and runs the package
automatically. You can also elect to upgrade the MID Server manually. See MID Server upgrades for details.
Resolving MID Server issues
You can search the HI Knowledge Base for troubleshooting articles or monitor the MID Server
status and track active issues from within the instance. See Resolving MID Server issues for
ServiceNow applications that use the MID Server
External applications that use the MID Server
MID Server version compatibility
The version of the MID Server must be compatible with the version of the instance.
Otherwise, the MID Server cannot process commands or communicate with the instance.
The instance determines which version of the MID Server is allowed. The MID Server version
must at minimum belong to the same major release, such as Madrid. If the MID Server version
belongs to the same major release, it can, but does not have to, belong to the same minor
version, such as Madrid Patch 1. In this case, communication with the instance might still
be possible, but it is always suggested that you upgrade to the latest version.
You can pin
the MID Server
to a specific version, but you should be aware that the version
might become out of date.