MID Server release notes
Summarize
Summary of MID Server Release Notes Washington DC
The ServiceNow® MID Server application facilitates communication and data transfers between a ServiceNow instance and external applications, data sources, and services. The Washington DC release introduces enhancements and updates to improve functionality and security for MID Server users.
Show less
Key Features
- Containerized MID Server Support: MID Servers can now operate in OpenShift on Linux, supporting rootless execution with persistent storage.
- Module Access Policies (MAPs): The default behavior is set to "Reject," preventing unauthorized access unless explicitly permitted.
- Debug Logs and Configuration: Users can enable debug logs at the dist-upgrade wrapper level and modify configurations using upgrade-wrapper-override.conf.
- Unique Logged-in Users: Each MID Server will now utilize unique logged-in users for enhanced security.
Important Information for Upgrading
The upgrade process requires a supported Java Runtime Environment (JRE) version, with minimum version 11.0.9 and recommended version 11.0.16.1. Users should ensure their MID Server host machines can access the download site for auto-upgrades. Note that only one Windows MID Server service is permitted per executable path, and multiple services pointing to the same folder may fail to start.
Deprecations
- Support for containerized Windows MID Servers has been discontinued, and the download link for the Windows MID Server docker recipe has been removed.
- Auto-deployment and auto-deletion through a dedicated deployment MID Server are no longer supported, along with deployment templates.
Key Outcomes
With the Washington DC release, ServiceNow customers can expect improved security through updated access policies, enhanced operational capabilities with containerized support, and better logging and troubleshooting through debug log configurations. These updates are designed to optimize the function and reliability of the MID Server in enterprise environments.
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 Washington DC release.
MID Server highlights for the Washington DC release
- Use OpenShift on Linux for containerized MID Servers.
- Prevent unauthorized access with the new "Reject" default behavior of the module access policies (MAPs).
- Enable the debug logs at the dist-upgrade wrapper level and test the changes by modifying the configuration with upgrade-wrapper-override.conf.
See MID Server for more information.
Important information for upgrading MID Server to Washington DC
For the latest MID Server system requirements, see MID Server system requirements. The minimum JRE version supported is 11.0.9 and the recommended version is 11.0.16.1.
- 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 per 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.
- MID Server pre-upgrade check: Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade.
- Upgrade the MID Server manually: Describes how to upgrade your MID Servers manually.
New in the Washington DC release
- Containerized MID Server support for OpenShift
Use OpenShift on Linux for containerized MID Servers. The corresponding Linux docker recipe has been updated. The containerized MID Server can run rootless by using existing auto-scaling capabilities with persistent storage.
Changed in this release
- MID Server Password2 global policy change
Use the new "Reject" default behavior of the module access policies (MAPs) to help prevent any unauthorized access, unless explicitly declared in MAP records. All required MAPs for internal access are provided. Auto-generated MAPs are provided for external access.
- MID Server unique logged-in users
Use unique logged in users for each MID Server. See (KB1552863) MID Server Unique Logged In User for more information.
- Improved wrapper configuration override
Enable the debug logs at the dist-upgrade wrapper level and test the changes by modifying the configuration with upgrade-wrapper-override.conf. For example, the default timeout may not be long enough for certain JVM level commands. You can increase the timeout with upgrade-wrapper-override.conf for the dist-upgrade wrapper configuration.
Deprecations
Containerized Windows MID Servers are no longer supported. The download link for the Windows MID Server docker recipe is removed. You can still use the old Windows MID Server docker recipe, but there’s no official support. See (KB1559617) Deprecated Containerized MID Server Features in Washington DC for more information.
Auto-deployment and auto-deletion through a dedicated deployment MID Server are no longer supported. Deployment templates are no longer supported and new deployment templates can’t be used or created. However, existing deployment requests with existing templates still work. See (KB1559617) Deprecated Containerized MID Server Features in Washington DC for more information.
Activation information
MID Server is a ServiceNow AI Platform feature that is active by default.