MID Server release notes

ServiceNow® MID Server enhancements and updates in the Helsinki release.

Helsinki upgrade information

  • To ensure that your MID Servers can upgrade successfully, run a series of manual tests for free disk space, access to the download server, and file permissions on the MID Server host. For details, see Test the MID Server before an upgrade.
    Important: After all MID Servers have been upgraded to Geneva or higher, complete the post-upgrade steps listed in the Workaround section of KB0597396.
  • MID Servers that exist prior to upgrading to Geneva are automatically validated to avoid interrupting automation tasks that such servers may be performing.
  • The MID Server application is downloadable from the ServiceNow service instance. The MID Server is upgraded automatically when you upgrade the instance. However, you can configure the version number to control MID Server upgrades. The MID Server is configured to check with the ServiceNow instance hourly to determine whether it needs to upgrade. This configurable behavior allows the MID Server to upgrade automatically when the instance upgrades.

New in the Helsinki release

MID Server long polling
Instead of querying the ECC Queue every 5 seconds, the MID Server subscribes to messages published by the Asynchronous Message Bus (AMB), which notifies the MID Server that there is work waiting for it in the queue.
MID Server domain separation enhancements:
Sudo support for ServiceNowSSH
ServiceNow SSH supports the use of sudo as root in long-running scripts. When properly configured, SSH can be run with sudo against individual commands within a probe to prevent long running commands from failing when the MID Server disconnects.

Changed in this release

  • The VMware vCenter event collector was expanded to support additional events by default and allow users to subscribe to new events easily. These changes let the CMDB reflect the current state without having to wait for the next full vCenter discovery to run.