This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Setting Up Multiple Instance of WebHelpDesk Version 12.2 and up

WHD Lovers!!! Sorry I was just very excited to give a short note on how you can successfully setup a Multiple Instance of WebHelpDesk Version 12.2.

Since version 12.2, the multiple instance setup has changed which was due to the licensing scheme update that is one license per machine/cluster only.

Below is how I made my test environment work. For example, you have 5 machines, one is going to be a "dedicated" daemon instance and the other 4 will be your front-end then below is how to accomplish this:

1. Node 1 - will be the first WHD instance to be setup. Activate the license here at first start-up (off course after all that initial install has been done).

2. Nodes 2, 3, 4 & 5 - Install WHD and just stop the service.

     2.1. Copy the files below from Node 1's conf folder to the <WebHelpDesk>/conf folder of each Node (2, 3, 4 & 5):

          - whd.conf

          - keystore.jks (if you have HTTPS)

          - .whd.properties (this contains the DB connection info)

     2.2. Modify the file <WebHelpDesk>/conf/tomcat_web_template.xml and set the Daemon Mode to "none" (should be the on the last 4 lines):

          From:

                <env-entry-name>WHDDaemonMode</env-entry-name>

                <env-entry-type>java.lang.String</env-entry-type>

                <env-entry-value>background</env-entry-value>

          To:

                <env-entry-name>WHDDaemonMode</env-entry-name>

                <env-entry-type>java.lang.String</env-entry-type>

                <env-entry-value>none</env-entry-value>

     2.3. Add the JVM Argument "-DClusterSecondaryNode=true" to the configuration.

          For Windows:

               2.3.A.1. Edit the conf file <WebHelpDesk>/bin/wrapper/conf/wrapper_template.conf

               2.3.A.2. Add the following line in the "# Java Additional Parameters" section of that file setting the next sequential number in the list:

                         wrapper.java.additional.<NUMBER>=-DClusterSecondaryNode=true

                         where <NUMBER> is the next proceeding number.

          For Mac or Linux:

               2.3.B.1. Edit <WebHelpDesk>/conf/whd.conf

               2.3.B.2. Add the following line at the end of the config file:

                         JAVA_OPTS="-DClusterSecondaryNode=true"

3. Back to Node 1: I would suggest that you make this node the "dedicated" daemon instance that way, all it needs to do is run the daemon for WHD specially for heavy emails and database interactions. To do that:

     3.1. Edit the file <WebHelpDesk>/conf/tomcat_web_template.xml and set the Daemon Mode to "dedicated" (should be the on the last 4 lines):

          From:

                <env-entry-name>WHDDaemonMode</env-entry-name>

                <env-entry-type>java.lang.String</env-entry-type>

                <env-entry-value>background</env-entry-value>

          To:

                <env-entry-name>WHDDaemonMode</env-entry-name>

                <env-entry-type>java.lang.String</env-entry-type>

                <env-entry-value>dedicated</env-entry-value>

     3.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 that for tracking sessions.

5. Restart all WHD instance.

Hope I have helped you...

  • Thanks for the post.

    This helped me a lot, as I have 1 app server, 1 daemon server, and 1 DB server configuration.  Approval emails were not sending, and automated tasks were not firing off.

    I did have an issue after changing the wrapper_template.conf file, when logged in as the admin account I could not access the Settings tab, removing this change fixed this issue...

    2.3.A.1. Edit the conf file <WebHelpDesk>/bin/wrapper/conf/wrapper_template.conf

    2.3.A.2. Add the following line in the "# Java Additional Parameters" section of that file setting the next sequential number in the list:

                             wrapper.java.additional.<NUMBER>=-DClusterSecondaryNode=true

                             where <NUMBER> is the next proceeding number.