Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

MID Server system requirements

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

MID Server system requirements

Use these minimum system requirements to allocate resources for computers hosting MID Servers.

Links to each of the MID Server sectionsEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server securityEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server security

MID Server supported systems

Windows server
To discover Windows-based servers, run Service Mapping patterns, or execute Orchestration commands on Windows devices, the MID Server must be installed on a Windows server. The MID Server supports these Windows operating systems, including virtual machines and 64-bit systems:
  • Windows Server 2008
  • Windows Server 2012
  • Windows Server 2016
Note: .NET Framework version 3.5, 4.0, 4.5, 4.6, or 4.7 is required for Service Mapping support and for Windows pattern-based discovery.
Linux
The MID Server is supported on these Linux versions for virtual machines and 64-bit systems:
  • Linux Red Hat 6 and above
  • Ubuntu 1404 (Ubuntu 14) and above
  • CentOS 6 and above
Note: On 64-bit Linux systems, you must install the 32-bit GNU C library (glibc). The installation command for CentOS is: yum install glibc.i686.

Java version support

OpenJDK version 1.8.0_181 is bundled with the MID Server installer package and is installed on the host for all new MID Servers. The installer automatically configures OpenJDK to run in your environment. No additional configuration is required. This version supports both 32-bit and 64-bit MID Servers. For the best performance, install the 64-bit MID Server for your operating system. The MID Server requires a minimum JRE version 1.8.0_161, and recommended version 1.8.0_181. If you are using a lower version than 1.8.0_161, you may see encryption related issues.
Note: ServiceNow will discontinue support for 32-bit MID Servers in a future release.
Upgraded MID Servers might use different Java versions depending on their release level.
  • MID Servers upgraded from Kingston and earlier use the OpenJDK provided with the MID Server installer. This version of the OpenJDK was tested and certified for use with these MID Servers.
  • MID Servers upgraded from London continue to use the same JRE you configured for London. The MID Server supports JRE 1.8.

MID Server supports Java 8 and Java 11 on any supported operating system. However, CPU monitoring is disabled by default on Windows with Java 11 because an outdated SIGAR library causes the MID Server to crash. If you decide to patch the SIGAR library, you can re-enable CPU monitoring. See CPU and maximum memory usage for more information on how to enable CPU monitoring.

Java Service Wrapper

The MID Server installer includes the Tanuki Java Service Wrapper, version 3.5.36.

Setting the JVM Memory size

The MID Server installs with 1 GB of JVM memory. If the suggested memory size for your product is greater than 1 GB, see Set the MID Server JVM memory size for the procedure to override the default setting.

Deployment types

System requirements for your instance are determined by the needs of the individual products you use that require a MID Server.

Standard deployments
The following products are considered "standard" because their MID Servers share the same minimum disk space and memory requirements:
  • Discovery
  • Event Management
  • Integrations
  • Orchestration
  • Service Mapping

The minimum standard requirements pertain to both a single product and a combined product deployment. You can deploy a single MID Server for multiple standard products without significantly increasing the disk or memory requirements.

High resource deployments

Cloud Management Platform (CMP), alert aggregation and RCA, and Operational Intelligence are processing intensive and require more resources for each MID Server than the standard products. Install MID Servers for these products on dedicated hosts that do not support MID Servers for other products.

Recommended MID Server minimum requirements

All configurations listed here require a quad core processor with a speed of 2 GHz or greater and were calculated for a Windows Server 2012 R2 host.
Note: The MID Server minimum system requirements for 25 concurrent threads includes resource overhead that is independent of the number of threads. As a result, the system requirements for 200 threads do not require a linear increase in resources. You can set the MID Server to use as few as 5 threads without issue. To increase the speed of the MID Server if the host is powerful enough or lightly loaded with other programs, you can increase the threads setting. The threads setting depends on the limitation of the CPU speed, memory, and operating system of the host machine. You might have to experiment to find the optimal threads count that works best when the MID Server is busy so it does not exhaust the host machine’s hardware limitations. This means you may have to refine the thread count to best meet your situation. Important: You can set threads.max as high as 200, however, this setting may need to be changed depending on the OS. For example, Windows-based MID Servers running Discovery uses Powershell which is resource intensive. In this case, you may exhaust the CPU power of the host machine with just 50 threads count.
Table 1. MID Server minimum system requirements for 25 concurrent threads (base system)
Product Disk space (GB) Memory (GB)
OS MID Server + product Total OS memory JVM memory Total
Alert aggregation and RCA 36 GB 10 GB 46 GB 4 GB 8 GB 12 GB
Cloud Management Platform (CMP) 36 GB 4 GB 40 GB 4 GB 4 GB 8 GB
Operational Intelligence 36 GB 16 GB 52 GB 4 GB 8 GB 12 GB
Standard 36 GB 4 GB 40 GB 4 GB 1 GB 5 GB
Table 2. MID Server minimum system requirements for 200 concurrent threads (customer configured)
Product Disk space (GB) Memory (GB)
OS MID Server + product Total OS memory JVM memory Total
Alert aggregation and RCA 36 GB 10 GB 46 GB 4 GB 8 GB 12 GB
Cloud Management Platform (CMP) 36 GB 4 GB 40 GB 4 GB 4 GB 8 GB
Operational Intelligence 36 GB 16 GB 52 GB 4 GB 8 GB 12 GB
Standard 36 GB 4 GB 40 GB 4 GB 4 GB 8 GB

Example: Use case 1: Single MID Server deployed for multiple standard products

In this example, Service Mapping, Discovery, and Orchestration share a MID Server with 25 threads that is installed on a dedicated host. The disk space and memory requirements specified here satisfy the minimum recommended requirements for the combined product deployment.

Table 3. One MID Server for multiple standard products
Product Disk space (GB) Memory (GB)
OS MID Server + product Total OS memory JVM memory Total
Service Mapping + Discovery + Orchestration 36 GB 4 GB 40 GB 4 GB 1 GB 5 GB

Example: Use case 2: Multiple MID Servers deployed to a single host

In this example, three MID Servers (not clustered) are assigned to different standard products. All three MID Servers are deployed to a single host, where each MID Server has 25 threads. The required resources are calculated as follows:
  • Total disk space required: Add the recommended disk space for the operating system from the OS column to the sum of the values in the MID Server + product column for all products mapped.
  • Total memory required: Add the recommended memory for the operating system from the OS memory column to the sum of the values in the JVM memory column for all products mapped.

Table 4. Calculating resources for multiple MID Servers on a single host
Product Disk space (GB) Memory (GB)
OS MID Server + product Total OS memory JVM memory Total
MID Server 1 36 GB 4 GB 4 GB 1 GB
MID Server 2 4 GB 1 GB
MID Server 3 4 GB 1 GB
Recommended minimum 36 GB 12 GB 48 GB 4 GB 3 GB 7 GB

Monitoring performance

To ensure that the MID Server resource allocations are sufficient for your environment, monitor performance during peak periods of product execution from the MID Server dashboard.

MID Server supports Java 8 and Java 11 on any supported operating system. However, CPU monitoring is disabled by default on Windows with Java 11 because an outdated SIGAR library causes the MID Server to crash. If you decide to patch the SIGAR library, you can re-enable CPU monitoring. See CPU and maximum memory usage for more information on how to enable CPU monitoring.

Feedback