MID Server release notes

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read
    • Summarize
    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 release notes Yokohama

    The ServiceNow® MID Server facilitates communication and data exchange between a ServiceNow instance and external applications, data sources, and services. The Yokohama release introduces important enhancements focused on security, compatibility, and installation flexibility.

    Show full answer Show less

    Key Features

    • JRE Version Requirement: MID Server now requires a minimum Java Runtime Environment (JRE) version 17. The release bundles JRE 17.0.12, with a minimum supported version of 17.0.10.
    • Windows Installation Improvements: MID Server can be installed on Windows hosts as either a LocalSystem or a non-admin user with Start and Stop permissions, simplifying installation and management.
    • External Credential Storage Enhancements: Added support for certificate-based authentication when connecting to Azure Key Vault, enhancing security and flexibility for enterprise environments.
    • Security Update: The 3DES encryption algorithm has been permanently removed from MID Server to improve security.

    Upgrade Considerations

    • Ensure MID Server hosts use a supported JRE version (minimum 17.0.10) before upgrading; unsupported versions trigger warnings during upgrade.
    • Only one Windows MID Server service per executable path is allowed; multiple services pointing to the same folder will prevent the MID Server from starting.
    • All MID Server hosts must have access to the ServiceNow download site to enable auto-upgrades.
    • Manual upgrade guidance and pre-upgrade checks are available to help validate readiness and perform upgrades smoothly.

    Activation and Integration

    MID Server is an AI Platform feature that is active by default and is integral to several ServiceNow applications including:

    • Discovery: Launches probes and patterns to populate CMDB data.
    • Orchestration: Executes work on internal and external systems.
    • Service Mapping: Collects information about business services.
    • Event Management: Processes events and collects SNMP traps.
    • Cloud Management: Handles VMware event collection and processing.
    • Operational Intelligence: Captures and analyzes operational metrics for anomalies.
    • Health Log Analytics: Collects log data to assist in root cause analysis.

    Practical Impact for ServiceNow Customers

    This release enhances MID Server security and operational stability by requiring JRE 17 and removing weaker encryption standards. Windows installation flexibility reduces administrative overhead, and improved credential management supports enterprise security policies. Customers should verify JRE compliance and installation configurations before upgrading to ensure uninterrupted MID Server operations and seamless integration with ServiceNow applications.

    The ServiceNow® MID Server application enables communication and data transfers between a ServiceNow instance and external applications, data sources, and services. MID Server was enhanced and updated in the Yokohama release.

    MID Server highlights for the Yokohama release

    • MID Server supports and requires a minimum JRE version 17. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10.
    • The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions.

    See MID Server for more information.

    Important information for upgrading MID Server to Yokohama

    For the latest MID Server system requirements, see MID Server system requirements. The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12.

    If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE:
    • If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version.
    • If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version.

    All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages MID Server upgrades.

    Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can’t start. See MID Server fails to start for more information.

    For more information about MID Server upgrades, see the following topics:

    New in the Yokohama release

    External Credential Storage and Management supports certificate-based authentication for Azure Key Vault
    The External Credential Storage and Management added support for certificate-based authentication when connecting to Azure Key Vault. This provides a more secure and flexible way to authenticate, especially for enterprise environments that prefer certificate credentials over client secrets.

    Changed in this release

    MID Server supports and requires a minimum JRE version 17

    The MID Server is compiled using Java 17 and is incompatible with any Java version below 17 for runtime execution. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. See the MID Server JRE Minimum Version Requirement Update to JRE 17 Starting from Yokohama Release [KB1704368] article in the Now Support Knowledge Base for information about required procedures before upgrading the instance.

    Improvements when manually installing a MID Server on Windows

    The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions.

    Removed in this release

    Activation information

    MID Server is a ServiceNow AI Platform feature that is active by default.

    Related ServiceNow applications and features

    Discovery

    Discovery uses the MID Server to launch probes and patterns that return information to the CMDB about devices and applications running in your environment. Discovery schedules select appropriate MID Servers based on their configured capabilities and assigned IP ranges.

    Orchestration

    Orchestration uses the MID Server to do work on internal and external systems. Orchestration selects MID Servers based on their capabilities and the applications that they’re allowed to use.

    Service Mapping

    Service Mapping uses the MID Server to launch patterns that return information about business services running in your environment.

    Event Management

    Event Management uses the MID Server to receive and process events, collect data for root cause analysis (RCA), and collect SNMP traps.

    Cloud Management

    Cloud Management uses the MID Server to collect and process VMware events.

    Operational Intelligence

    Operational Intelligence uses MID Server clusters to capture operational metrics data from external data sources and analyze them for anomalies.

    Health Log Analytics
    Health Log Analytics uses the MID Server to collect log data streaming into your instance and helps you identify the root cause of issues.