Home > Success Center > Web Help Desk (WHD) > Move Web Help Desk from one system to another

Move Web Help Desk from one system to another

Created by Interspire Import, last modified by Steve.Hawkins on Oct 18, 2016

Views: 2,969 Votes: 1 Revisions: 14

Overview

This article explains how to move the Web Help Desk application from one server to another either running the same or a different operating system as the original server.

Environment

All WHD versions

Steps

Original Server and Target Server are in the same Operating System

When using Windows, both servers should be the same bit version.

  1. Stop the WHD application on the original server.
  2. Make a configuration backup by copying the /conf directory to a safe location. 
  3. If the original server is running on Windows, also copy the \bin\wrapper\conf directory to a safe location.
  4. Install the same version of WHD on the target server. 
  5. On the target server, initialize the WHD by using the Getting Started Wizard and choose embedded database (default PostgreSQL).
  6. Stop the WHD application and PostgreSQL service on the target server.
    1. On the target WHD sever, rename the \Program Files\WebHelpDesk\PGSQL9 folder toOLD_PGSQL9.(You can also opt to move that folder to a different location.)
    2. Copy the Program Files\WebHelpDesk\PGSQL9 folder from the old WHD installation to the \Program Files\WebHelpDesk\ location on the target server.
  7. Copy the configuration backup from the original server to the same location on the target server: /conf or \bin\wapper\conf (Windows).
    1. Windows:
      • keystore.jks
      • whd.conf
      • labels\CustomLabels*.properties
      • bin\wrapper\conf\wrapper_template.conf
    2. Linux/Mac OS
      • keystore.jks
      • whd.conf
      • labels/CustomLabels*.properties
  8. Start the WHD application on the target server.
  9. If the Domain host name of the target server is different than the domain host name of original server, navigate to Setup > General > Options and change the Server DNS Name.

Original Server uses Windows and Target Server is UNIX based (Linux or Mac OS)

This method can be used also for systems with the same operating system and bit version.

  1. Stop the WHD application on the original server.
  2. Make a configuration backup by copying the /conf directory and the whd\bin\wrapper\conf directory to a safe location.
  3. Install the same version of WHD on the target server.
  4. Initialize the WHD by using the Getting Started Wizard and choosing the default PostgreSQL embedded database.
  5. Log in using admin/admin credentials. Navigate to Setup > General > Database and point WHD to your original database. If the original server used embedded PostgreSQL, it runs on port 20293.
  6. Stop the WHD application on the target server.
  7. Copy the configuration backup from the original server to the same location as the target server:/conf:
    • keystore.jks
    • whd.conf
    • labels/CustomLabels*.properties
  8. If you have used custom VM arguments in the \bin\wrapper\conf\wrapper_template.conf file, add them to the JAVA_OPTS parameter in the /conf/whd.conf file. For example: JAVA_OPTS="-Darg1=true -Darg2=true"
  9. Start the WHD application on the target server.
  10. If the Domain host name of the target server is different than the domain host name of original server, navigate to Setup > General > Options and change the Server DNS Name.

Original Server is UNIX based (Linux or Mac OS) and Target Server uses Windows

  1. Stop the WHD application on the original server.
  2. Make a configuration backup by copying the /conf directory to a safe location.
  3. Install the same version of WHD on the target server.
  4. Initialize the WHD by using the Getting Started Wizard and choosing the default PostgreSQL embedded databse.
  5. Log in using admin/admin credentials. Navigate to Setup > General > Database and point WHD to your original database. If the original server used embedded PostgreSQL, it runs on port 20293.
  6. Stop the WHD application on the target server.
  7. Copy the configuration backup from the original server to the same location as the target server: /conf:
    • keystone.jks
    • whd.conf
    • labels/CustomLabels*.properties
  8. If you have used custom VM arguments in the JAVA_OPTS parameter in the /conf/whd.conf file, add them to the \bin\wrapper\conf\wrapper_template.conf file. For example: wrapper.java.additional.16=-DWHDconfig=...Helpdesk.woa.properties
  9. Start the WHD application on the target server.
  10. If the Domain host name of the target server is different than the domain host name of original server, navigate to Setup > General > Optionsand change the Server DNS Name.


Library of Referenced Commands

Most of these commands need to be executed in the command line. To access a command line:

  • Windows: Navigate to Start > Run and enter cmd. It should automatically open with administrative privileges.
  • Mac OS X: Navigate to Applications > Utilities and double-click on Terminal.
  • Linux (RPM installation): In the graphical interface, navigate to Applications > System and open the terminal from the tool menu or by right-clicking Desktop and clicking Open in Terminal (varies in different distributions). You can also connect remotely via SSH protocol, as described in the following section for Virtual Appliance.
  • Virtual Appliance (Linux): Needed to connect to the server using SSH protocol. Execute ssh username@server_ip_or_hostname command on Mac OS X/Linux or use PuTTY utility on Windows (credentials admin/admin).

This article uses standard installation directories for a reference. If you installed WHD to a non-standard directory, replace c:\progra~1\WebHelpDesk (Windows), /Library/WebHelpDesk (Mac OS C), /usr/local/webhelpdesk (Linux + VA) with the correct locations in all commands.

Viewing 3 of 3 comments: view all
Interspire author is Io Aceremo
Posted 18:57, 26 Jun 2015
Interspire author is Io Aceremo
Posted 18:44, 14 Aug 2015
Interspire author is Io Aceremo
Posted 19:24, 14 Aug 2015
Viewing 3 of 3 comments: view all
You must to post a comment.
Last modified
15:05, 18 Oct 2016

Tags

Classifications

Public