Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

MID Server upgrade parameters

MID Server upgrade parameters

These parameters control the upgrade of the MID Server, including a version number that you can pin the MID server to.

Table 1. MID Server upgrade parameters
Label Names Description
Fixed MID Server version mid.pinned.version Name of the version to which this MID Server is pinned.
  • Type: string
  • Default value: build timestamp
Upgrade proxy enable mid.upgrade.use_proxy If your MID Server must go through a web proxy to access the upgrade URL, set this parameter to true to instruct the MID Server to use the proxy. You must also set the proxy server's host and port. If the instance proxy user name and password are set, they are used for the upgrade proxy as well.
  • Type: true | false
  • Default value: false
Upgrade proxy host glide.mid.autoupgrade.proxy_host or glide.glidesoap.proxy_host If your MID Server must go through a web proxy to access the upgrade URL, define the proxy's host here.
  • Type: string (URL)
  • Default value: none
Upgrade proxy port glide.mid.autoupgrade.proxy_port or glide.glidesoap.proxy_port If your MID Server must go through a web proxy to access the upgrade URL, define the proxy's port here.
  • Type: integer (0-65535)
  • Default value: 80
Upgrade proxy user glide.mid.autoupgrade.proxy_user If your MID Server must go through a web proxy to access the upgrade URL, define the proxy's user name here.
  • Type: string (URL)
  • Default value: none
Upgrade proxy password glide.mid.autoupgrade.proxy_password If your MID Server must go through a web proxy to access the upgrade URL, define the proxy's password here.
  • Type: string
  • Default value: none