--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # MID Server for metadata collectors # MID Server for metadata collectors {#ariaid-title1} Release version: Australia Updated April 29, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of MID Server for metadata collectors For ServiceNow customers needing to harvest metadata from on-premises or privately networked data sources, deploying metadata collectors on a MID Server within your network is essential. The MID Server acts as a secure intermediary, facilitating communication and data transfer between your ServiceNow instance and external data sources that are behind firewalls or require on-premises handling. A properly configured and validated MID Server is required to establish this connection. Show full answer Show less ## System Requirements and Configuration Guidelines The host machine running the MID Server must have at least 8 GB of RAM and a 4 GHz processor to meet minimum hardware requirements. Best practices for configuring the MID Server for metadata collection include: * **Dedicated MID Server:** Use a dedicated MID Server for metadata collectors to prevent resource conflicts with other applications. * **Memory Allocation:** Start with a minimum of 8 GB JVM memory; adjust based on data volume and complexity. * **Size-based Planning:** Estimate data volume in advance to appropriately size MID Server resources and memory allocation. If performance issues or out-of-memory errors occur, consult the MID Server system requirements documentation to optimize configuration settings. ## MID Server Routing Models When metadata collectors run on a MID Server, routing models determine which MID Server or cluster handles each collection job. Administrators can change routing models at any time. The models include: * **Auto-select:** The system automatically selects any available MID Server at job execution. Constraints can limit selection to MID Servers with specific capabilities or running certain applications. This is the default model. * **Designated MID Server:** Jobs run on a single, specified MID Server. If that server is unavailable, the job fails with an error. This model suits sources requiring a specific network path, credentials, or capabilities unique to one MID Server. * **Designated MID Cluster:** Jobs run on any available MID Server within a named cluster, enabling load distribution and failover among servers sharing access to the source. When your source is behind a firewall or requires on-premises handling, deploy metadata collectors on a MID Server you host to harvest metadata from on-premises and privately networked data sources. To harvest metadata from on-premises and privately networked data sources, you deploy metadata collectors on a MID Server within your network. This is one of two [deployment models](https://www.servicenow.com/docs/u6Aszd9cS3RfGdjK3i6ljA "Choose how to deploy metadata collectors based on your network accessibility and security needs. Deploy on a MID Server you host, or use ServiceNow-managed cloud infrastructure.") available for metadata collectors.{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-1} The Management, Instrumentation, and Discovery (MID) Server facilitates secure communication and data movement between your ServiceNow instance and external data sources. A configured and validated MID Server is required to connect to the data source. For more information, see the [MID Server documentation](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-2} ## System requirements {#mid-server-for-metadata-collectors-dc__system-requirements} The host running the MID Server must meet the following minimum hardware requirements:{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-3} {#mid-server-for-metadata-collectors-dc__system-requirements__entry__2} | Item | Requirement | |-|-| | RAM | 8 GB | | CPU | 4 GHz processor | [ ] ## MID Server configuration guidelines {#mid-server-for-metadata-collectors-dc__recommended-configuration} The following guidelines apply when sizing and configuring the MID Server for metadata collectors:{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-4} * Dedicated MID Server: Use a dedicated MID Server for metadata collectors that connect to external data sources to avoid resource contention with other applications. * Minimum memory guidance: Start with a minimum of 8 GB JVM memory. Actual requirements vary based on data volume and complexity. * Size-based planning: Estimate data volume in advance and size MID Server resources accordingly. Consider your data volume and processing requirements when configuring your MID Server. Depending on your environment, you can adjust memory allocation to support your workload.{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-5} Note: If you experience out-of-memory errors or performance issues, refer to the [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) documentation for guidance on adjusting your configuration. ## MID Server routing models {#mid-server-for-metadata-collectors-dc__mid-server-selection} When a metadata collector is deployed on a MID Server, a routing model determines which MID Server or cluster executes each collection job. The routing model applies to all runs and can be changed by an administrator at any time.{#mid-server-for-metadata-collectors-dc__mid-server-for-metadata-collectors-dc-para-6} Auto-select : The system selects any available MID Server at job execution time. This is the default routing model. Auto-select supports two optional constraints: selection can be restricted to MID Servers that advertise specific capabilities, or narrowed to MID Servers running a particular application. Designated MID Server : The collection job always runs on a single, named MID Server. If that MID Server is unavailable at job execution time, the job fails with an error identifying it by name. This model is suited for sources that require a specific network path, credential set, or capability that only one MID Server in the environment provides. Designated MID cluster : The collection job runs on any available MID Server within a named cluster. This model supports load distribution and failover across MID Servers that share access to the source.