Skip to main content

Installing Multiple MID Servers on a single Windows system

You can install multiple MID Servers on a single host or on a virtual machine using Windows. This is useful when one MID Server is down so another can take its place. Note that installing multiple MID Servers might involve additional setup steps, depending on your network configuration.

Procedure

To install a MID Server on a single Windows system, complete the following steps.

  1. Download the MID Server archive file.
    1. From the ServiceNow portal, click Mid Server > Downloads.
    2. Select and download the MID Server for the appropriate operating system.

      If the download does not begin immediately, try the download later as the system may be busy.

  2. From the system or virtual machine where you want to install multiple MID Servers, create a directory for each MID Server on the top level of the drive using unique and distinctive names (for example, ServiceNow\MIDServer_SMS_Int or ServiceNow\MIDServer_Disc1).
  3. Extract the downloaded MID Server file into each MID Server directory. When complete, the \agent directory is in under each MID Server directory (for example, \ServiceNow\MIDServer_SMS_Int\agent).
  4. For each Windows MID Server, edit the \agent\config.xml file using a text editor (such as WordPad), as follows:

    1. Locate the <parameter name="url" value="https://YOUR_INSTANCE.service-now.com" /> element, and change the value to the URL of your ServiceNow instance.

    2. If basic authentication is enabled, enter the MID Server user credentials in the mid.instance.username and mid.instance.password parameters.

      Note
      Basic authentication for SOAP messages is enabled by default. The password value is also encrypted authentication.

    3. Locate the <parameter name="name" value="YOUR_MIDSERVER_NAME_GOES_HERE" /> element, and change the value to the name of your MID Server.

    4. Optionally, enter the connection information for a proxy server that is used, and remove the comment tags from the proxy configuration information. For example, you can configure the mid.proxy.use_proxy, mid.proxy.host, mid.proxy.port, mid.proxy.username, and mid.proxy.password.

  5. For each Windows MID Server, edit the \agent\conf\wrapper-override.conf file with a text editor, and enter the following configuration information.
    Attention
    Do not edit the wrapper.conf file, which contains the default configuration for the MID Server. Any future ServiceNow upgrades overwrite the contents of the wrapper.conf file but not the wrapper-override.conf file.

    • wrapper.name. The MID Server process, maps to the Service name, and must be unique. The default value is snc_mid.

    • wrapper.displayname. The display name in the Windows Services console (for example, ServiceNow DevMID01). The default value is ServiceNow MID Server.

    • (Optional) wrapper.java.command. The path to the Java \bin directory, either relative to the agent directory or absolute. The default value is jre/bin/java.

    • (Optional) wrapper.java.initmemory. The initial Java heap size in MB. The default value is 10.

    • (Optional) wrapper.java.maxmemory. The maximum Java heap size in MB. The default is 512.

    Tip
    These values cannot be edited while the MID Server is running.
  6. Confirm that the MID Server is running.
    Tip

    • To start the server, run one of the following commands:

      • (Windows) start.bat

      • (Linux) start.xh

    • To stop the server, run one of the following commands:

      • (Windows) stop.bat

      • (Linux) stop.xh

  7. Optionally, configure MID Server clustering for load balancing or failover as necessary.
  8. After you configure the MID Server, you can view a list of installed MID Server in the Servers table under the MID Server module.