Pinning a MID Server to a specific version

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Pinning a MID Server to a Specific Version

    This guide explains how to pin a MID Server to a specific version within your environment, allowing for either global or individual MID Server configuration. However, it is generally recommended to avoid pinning, as it can lead to synchronization issues with the instance.

    Show full answer Show less

    Key Features

    • System Properties: Two main properties control MID Server versions:
      • mid.buildstamp: Identifies the MID Server version based on its build date. The MID Server checks this property hourly and will revert to the default version after a restart or upgrade.
      • mid.version.override: Allows you to pin all MID Servers to a specific version, disabling automatic upgrades. This property must be manually added to the system properties table.
    • Version Control Configuration: For individual MID Servers, use the mid.pinned.version parameter in the config.xml file to set a specific version. This setting is checked every 20 minutes or upon MID Server restart.

    Key Outcomes

    By managing these settings, you can control which MID Server versions are active in your environment. However, be cautious as pinning can disrupt functionality and create version mismatches with your instance. Ensure to monitor any changes, especially during upgrades, as the override values will be cleared at that time.

    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:
    Under most circumstances, do not pin the MID Server to a specific version. Pinning the MID server can make it out of sync with the instance, and lead to broken functionality. Instead, let the instance determine which MID Server version to use.

    Version control properties

    These system 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 the format of mm-dd-yyyy-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. The system appends the release name and patch information to the date and time format.
      Warning:
      This property is not visible by default and should not be configured.
    • 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 system property.
      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.
      Important:
      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. Use the format <version>-mm-dd-yyyy. This setting overrides the property setting for the pinned MID Server version. The MID Server version is checked every 20 minutes or whenever the MID Server restarts, at which point the pinned version is applied. For instructions, see Add a MID Server parameter.
    Note:
    The value set in this parameter is not affected by an upgrade.