Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

MID Server version selection

Log in to subscribe to topics and get notified when content changes.

MID Server version selection

You can pin all the MID Servers in your environment to a specific version by setting a system property, or you can configure specific versions for individual MID Servers.

Note: ServiceNow does not recommend pinning the MID Server to a specific version for a significant amount of time, especially if you upgrade the instance. Under most circumstances, you should let the instance determine which MID Server version to use.

Version control properties

These properties control the version for all MID Servers:
  • mid.buildstamp: Identifies the MID Server version with an identifier based on the date of the build. This property uses a date and time format of yyyy-mm-dd-hhmm. The MID Server checks for version information hourly. If no override version is configured, the MID Server looks at the mid.buildstamp property for the version to use. This property resets itself to the default version (the version that matches your instance version) when the instance is restarted or upgraded, so any user changes are lost at that time.
  • mid.version.override: Sets an override condition for the current version for all MID Servers in your environment. This action pins the MID Servers to a single version and disables the automatic upgrade feature. This property is not visible in the base system and must be added to the System Property [sys_properties] table when it is set. For details, see Add a property using sys_properties.list.
    When the MID Servers check the version each hour, they look at the mid.version.override property first. If this property is empty, the MID Servers get their version information from the mid.buildstamp property. If an override version is configured, the MID Servers use this value and ignore the version information in the mid.buildstamp property. This override value remains when the instance is restarted and is passed to the MID Servers.
    Attention: The value in the mid.version.override property is cleared during an upgrade, which forces the MID Server to reset itself to the version in the mid.buildstamp property.

Version control configuration parameter

To pin specific MID Servers on a desired version, set the mid.pinned.version parameter with the name of that version in the config.xml file of each MID Server. This setting overrides the property setting for the pinned MID Server version. For instructions, see Add a MID Server parameter.
Note: The value set in this parameter is not affected by an upgrade.