Tools

Point WHD to a new external database

This article describes how to configure WHD to use an external database.

First published date

11/1/2018 8:19 PM

Last published date

11/1/2018 8:19 PM

Overview


Configure Web Help Desk to use an external database.  You would like to point Web Help Desk to a new database location.

Product section

Web Help Desk

Resolution


A. From the Web Help Desk Interface 

 
  1. Go to Setup > General > Database
  2. Choose the database Vendor then provide the necessary credentials such as Host, Username and Password
  3. Click Save
  4. Restart Web Help Desk service Please refer to this KB on how to restart the Web Helpdesk service) Stop and start Web Help Desk

B. By editing the .whd.properties file


Windows
  • Go to *:\Program Files\WebHelpdesk\conf
  • Look for .whd.properties file and open it on a notepad
  • Change the following entries depending on your database used and credentials:
whd.db.subprotocol=[postgresql, mysql or mssql]
whd.db.password=[password]
whd.db.host=[ip address of the database server]
whd.db.name=[name of the database]
whd.db.username=[username]
  • Restart Web Helpdesk service (Please refer to this KB on how to restart the Web Helpdesk service) Stop and start Web Help Desk Save the file
Linux / Virtual Appliance
  • Connect to the Linux server or your Virtual Appliance using an SSH client like PuTTY as an “admin” (default password is “admin”)
  • Change to the user “root” command:
sudo su -
  • Open the .whd.properties file command:
vi /usr/local/webhelpdesk/conf/.whd.properties
  • Press the `A` key to enter into edit mode
  • Change the following entries depending on your database used and credentials:
whd.db.subprotocol=[postgresql, mysql or mssql]
whd.db.password=[password]
whd.db.host=[ip address of the database server]
whd.db.name=[name of the database]
whd.db.username=[username]
  • Once done, Press the `ESC` key and press `SHIFT + ZZ` to save and exit the editor
  • Restart Web Helpdesk service (Please refer to this KB on how to restart the Web Helpdesk service) Stop and start Web Help Desk
MAC OSx
  • Connect to the Linux server or your Virtual Appliance using an SSH client like PuTTY as an “admin” (default password is “admin”)
  • Change to the user “root” command:
sudo su -
  • Open the .whd.properties file command:
vi /Library/WebHelpDesk/conf/.whd.properties
  • Press the `A` key to enter into edit mode
  • Change the following entries depending on your database used and credentials:
whd.db.subprotocol=[postgresql, mysql or mssql]
whd.db.password=[password]
whd.db.host=[ip address of the database server]
whd.db.name=[name of the database]
whd.db.username=[username]
  • Once done, Press the `ESC` key and press `SHIFT + ZZ` to save and exit the editor
  • Restart Web Helpdesk service (Please refer to this KB on how to restart the Web Helpdesk service) Stop and start Web Help Desk

C. Establishing a new database connection
 
  1. Stop the Web Help Desk service
  2. Copy/backup the current Web Help Desk database and restore that database into the new SQL server
  3. Inside the Web Help Desk server, go into C:\Program Files\WebHelpDesk\conf and rename the '.whd.properties' file into 'ORIG.whd.properties' file
  4. Start the Web Help Desk service
  5. Once the Web Help Desk page loads, choose Use Custom SQL database.
  • In the Database Type field, select MSSQL.
  • Complete the remaining fields, and then click Test to test the database connection.
  • When you have established a connection with the database, click Next.

Disclaimer: Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.