How to manually restore or upgrade MID server


In some occasions, MID server might fall into following situations:

  1. Unable to startup due to unexpected reason. For example, files corruption
  2. Unable to perform automatic or manual upgrade as per following:
    • Automatic: Allow the instance to automatically upgrade the MID Server. This functionality is available by default. Automatic upgrade occurs:
      • Every hour, the MID Server checks with the instance to see if there is a different version available for upgrade. This time period cannot be modified.
      • When the instance is upgraded and the MID Server for that version is different than the version currently on the MID Server.
      • When the MID Server pre-upgrade test passes without an error. Any errors encountered during this automatic test prevent the upgrade from occurring until the issues are resolved. The pre-upgrade test is enabled by default, but can be disabled by adding and setting a system property.
    • Manual: Manually start the upgrade by clicking a related link on the MID Server record. Use this method when you do not want to wait until the next hourly automatic update or if the upgrade failed, and to force an upgrade.

The following steps can help to overcome point 1 and 2.


  1. Stop mid server service. Make sure the java process corresponding to MID server is shut down. For Windows, check from task manager and verify no java process tie to mid server installed path. 
    For Unix, check via:
    ps -ef | grep mid
    and make sure no process is tied to the mid server.
  2. Download Mid server package by navigating to Mid Server Application on the instance > Downloads module and pick the package need. 
    Unzip and place the package into MID server host. 
  3. Rename the existing installed MID Server agent directory to a different name. For example, old_agent.

  4. Copy the new agent directory which unzip at step 2 and place in the existing MID Server directory.

  5. Copy following files from "old_agent" directory
    - "config.xml" (ie: <OLD_MID_SERVER_INSTALL_PATH/agent>)
    - "wrapper_override.conf" (ie: <OLD_MID_SERVER_INSTALL_PATH/agent/conf>)
    - "keystore" folder (ie: <OLD_MID_SERVER_INSTALL_PATH/agent>)

    Place to the respective directories in the new agent folder.

  6. Start the MID Server.

  7. Validate the mid server from the instance after MID Server startup.


From the London Release, there is a pre-requisite change for MID Server installation. The Java Runtime Environment (JRE) is no longer bundled with the MID Server installer and must be installed separately by the user.

Article Information

Last Updated:2019-08-02 21:20:58