MID Server release notes
-
- UpdatedAug 3, 2023
- 3 minutes to read
- Vancouver
- Release Notes and Upgrades
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 Vancouver release.
MID Server highlights for the Vancouver release
- The MID Server pages and dashboard have been updated with the Next Experience.
- The MID Server caches credentials from external vault solutions and implements a thread-pool.
- The MID Server can insert Root CA Certification in the trust store and validate the code signing certificate before that certification can be used to validate signatures.
See MID Server for more information.
Important information for upgrading MID Server to Vancouver
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 cannot 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 ability 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 Vancouver release
- Cloud Discovery using Azure service principals
- You can set up an Azure service principal on the Discovery credentials [discovery_credentials] table. The discovery schedule can run with a MID Server in Azure to discover Linux and Windows virtual machines using that Azure service principal.
Changed in this release
- Code Signing Certificate Validation on MID Server
- MID Server can insert Root CA Certification in the trust store and validate the code signing certificate before that certification can be used to validate signatures.
- Improved Caching of Credentials with External Credentials Vaults
- The MID Server caches credentials from external vault solutions and implements a thread-pool, which sets a maximum number of threads used when communicating with a CyberArk server. The MID Server resolves this asynchronously to avoid other concurrency issues.
UI changes
- Next Experience UI
- The Next Experience UI Framework is now supported for the following features:
- Service Mapping
- MID Server dashboard.
Activation information
MID Server is a Now Platform feature that is active by default.