Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

MID Server integrations

Log in to subscribe to topics and get notified when content changes.

MID Server integrations

Factors determining the number of MID Servers your network will require to support external applications that integrate with ServiceNow include the following:

  • The security constraints in your network
  • The amount of traffic between ServiceNow and the integrations
  • The reliability of the MID Server machines.


Security policies in your network (firewalls between network segments, for example) might make direct communication impossible between your instance and an integration's data source (JDBC, LDAP, etc.). To retrieve data for the instance, you can install a MID Server that has access to both the data source and the instance.

Load balancing

In some cases, a single MID Server can handle all the transactions that occur between an instance and an external integration. However, in a high volume environment, it might be necessary to deploy multiple MID Servers as load balancers for certain transactions. For example, JDBC data transfers can tie up the resources of a MID Server , making it unable to respond to other requests. The following operations between an integration might require separate MID Servers in a busy network:
  • File exports
  • Running scripts
  • JDBC data sources
  • Reading files

High availability model

Avoid installing MID Servers for critical integrations on a machine that might experience any type of planned outage or an outage caused by overloaded processes. If necessary for reliability, consider deploying these types of MID Servers to dedicated machines for high reliability
Note: Do not integrate with an external application on a MID Server provisioned for ServiceNow Discovery or Orchestration.