Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Web Help Desk (WHD) > Set up multiple instances of Web Help Desk 12.2 and later

Set up multiple instances of Web Help Desk 12.2 and later

Table of contents

Updated March 23, 2017


This article provides steps to set up multiple instances of Web Help Desk with more than a one front-end instance and a load balancer


WHD 12.2 and later


  1. For Node 1 is the first WHD instance to be set up. Activate the license at the first start up.
  2. For Nodes 2, 3 4 and 5, install WHD and stop the service.
    1. Copy the files from step 1's configuration folder to the <WebHelpDesk>/conf folder of each Node (2, 3, 4 and 5):
      • whd.conf
      • keystore.jks (if you have HTTPS)
      • (this contains the DB connection info)
    2. Modify the <WebHelpDesk>/conf/tomcat_web_template.xml file and set the Daemon Mode to none (should be the on the last 4 lines):



    3. Add the JVM Argument -DClusterSecondaryNode=true to the configuration.
      For Windows:
      Edit the conf file <WebHelpDesk>/bin/wrapper/conf/wrapper_template.conf then add the following line in the # Java Additional Parameters section of that file setting the next sequential number in the list:<NUMBER>=-DClusterSecondaryNode=true
      where <NUMBER> is the next proceeding number.

      For Mac or Linux:
      Edit <WebHelpDesk>/conf/whd.conf then add the following line at the end of the config file:
  3. Make Node 1 the dedicated daemon instance, that way, all it does is run the WHD daemons especially for heavy emails and database interactions.
    1. Edit the <WebHelpDesk>/conf/tomcat_web_template.xml file and set the Daemon Mode to dedicated (should be the on the last 4 lines):

    2. Since this machine is no longer offering the Web UI, you will have to take it off the pool for from your load balancer.
  4. In your load balancer, enable Sticky sessions as WHD will require this for tracking sessions.
  5. Restart all WHD instances.


Last modified