MID Server system requirements

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

MID Server supported systems

The following systems support the MID Server.
  • 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 all Windows Server 2008, 2012, and 2016 editions, virtual machines, and 64-bit systems.
    Note: .NET Framework version 3.5, 4.0, or 4.5 is required for Service Mapping support and for Windows pattern-based discovery.
  • Linux: The MID Server was tested on Linux Red Hat 6, Ubuntu 12, and CentOS 6. Linux MID Servers support virtual machines and 64-bit systems. 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

The MID Server installs with JRE version 1.8. If you upgrade with a MID Server using JRE 1.6, the system automatically upgrades that MID Server to use version 1.8. Both the 32 bit and 64 bit MID Servers use JRE 1.8.

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

Content Management Platform (CMP), Service Analytics and Operational Metrics are processing intensive and require more resources for each MID Server than the standard products. The best practice is to 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.
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
Service Analytics 36 GB 10 GB 46 GB 4 GB 8 GB 12 GB
Content Management Platform (CMP) 36 GB 4 GB 40 GB 4 GB 4 GB 8 GB
Operational metrics 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
Service Analytics 36 GB 10 GB 46 GB 4 GB 8 GB 12 GB
Content Management Platform (CMP) 36 GB 4 GB 40 GB 4 GB 4 GB 8 GB
Operational metrics 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
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
Use case 2: Multiple MID Servers deployed to a single host
In this example, three MID Servers for standard products 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.