Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Web Help Desk (WHD) > Migrate the WHD virtual appliance VA to Linux or Windows

Migrate the WHD virtual appliance VA to Linux or Windows

Updated June 20, 2017

Overview

This article describes how to migrate your current Web Help Desk (WHD) virtual appliance (VA) to Linux (RedHat Linux/Solaris) or Windows Operating System (OS). 

 

This article provides steps for the following deployment scenarios:

  • Scenario A:  There is an existing Linux box (Red Hat or Solaris) to migrate the WHD VA database (embedded PostgreSQL).
  • Scenario B: There is no existing Linux box but there is an available Windows server to migrate the WHD VA database (embedded PostgreSQL).

Environment

All WHD Virtual Appliance versions

Steps

Scenario A: There is an existing Linux box (RedHat or Solaris) to migrate the WHD VA 

Stop the WHD application to prepare for migration

  1. Connect to the WHD VA via SSH using admin/admin and then go to the WHD installation directory:
    cd /usr/local/webhelpdesk/
  2. Execute the following command:
    sudo ./whd stop
    This also stops the embedded PostgreSQL database service.
  3. Start the PostgreSQL database service to be able to run the DB execute command:
    sudo bin/pgsql/etc/rc.d/init.d/postgresql-9.2 start

Back up the PostgreSQL embedded database from WHD VA (CentOS-Linux)

Execute the following commands:
cd /usr/local/webhelpdesk/
sudo sh -c 'pgsql9/bin/pg_dump -Fc -v -h 127.0.0.1 -p 20293 -U whd whd > whd.pgdump'

Note: If prompted for a DB password, use whd.
A backup file will be created in /usr/local/webhelpdesk/ with the name whd.pgdump.

Set up and prepare your own Linux server

  1. Download the installer for WHD (same version you have in VA) for Red Hat Linux 64-bit from the SolarWinds Customer Portal.
  2. Install WHD (same version you have in VA) in your own Red Hat Linux (64-bit) or other Linux flavors (64-bit).
  3. Copy a backup file of whd.pgdump from your WHD VA to this new server with Red Hat Linux (64-bit) or other Linux flavors (64-bit).
  4. Copy the following files from your WHD VA to the new server with RedHat Linux (64-bit) or other Linux flavors (64-bit):
    • <WebHelpDesk>\conf\whd.conf
    • <WebHelpDesk>\conf\keystore.jks 
    • <WebHelpDesk>\bin\jre\lib\security\cacerts

Note: The keystore.jks file only exists if WHD uses HTTPS with the SSL certificate.

 

Rename or drop the default empty PostgreSQL embedded WHD database in your own Linux (RPM) installation

  1. Run the following command:
    cd /usr/local/webhelpdesk/
  2. Connect to database using the following command:
    sudo pgsql9/bin/psql -h 127.0.0.1 -p 20293 -U whd -d template1
    Note: If prompted for a password, use whd.
  3. Execute the following statements:
    ALTER DATABASE whd rename to whd_old;
    CREATE DATABASE whd;
  4. Enter \q to exit the psql tool.

Restore the  PostgreSQL database backup file "whd.pgdump" taken from WHD VA to your new WHD Linux box (RPM installation)

Run the following commands:

cd /usr/local/webhelpdesk/

sudo pgsql9/bin/pg_restore -Fc -v -h 127.0.0.1 -p 20293 -U postgres -d whd path_to_whd.pgdump
Note: If prompted for a password, use whd.

Deactivate the WHD license in the existing WHD VA

  1. Start the WHD application from the existing WHD VA.
  2. Log in to the WHD web application and go to Setup > General > License > License Settings.
  3. Click the padlock icon.
  4. Copy the Customer Contact details and Activation Key to a text file.
  5. Click Deactivate.

Active the WHD license on the new WHD Linux server

  1. Start the WHD application in the new WHD Linux server.
  2. Log in to the WHD web application and go to Setup > General > License > License Settings.
  3. Click the padlock icon and provide the Customer Contact details and Activation Key from the previous procedure.
    Note: If the Activation Key does not work, log in to the Customer Portal and retrieve your new Activation Key for WHD.
  4. Click Activate.

Perform an in-place upgrade to WHD 12.5.1

  1. Download WHD 12.5.1 RedHat Linux (64-bit) from the Customer Portal.
  2. Upgrade the existing WHD version to WHD 12.5.1.

Scenario B: No existing Linux box but there is an available Windows server to migrate the WHD VA 

Stop the WHD application - Virtual Appliance (CentOS-Linux)

  1. Connect to the WHD VA via SSH using admin/admin, and then go to the WHD installation directory:
    cd /usr/local/webhelpdesk/
  2. Execute the following command:
    sudo ./whd stop
    This also stops the embedded PostgreSQL database service.
  3. Start the PostgreSQL database service to be able to run the DB:
    execute command: sudo bin/pgsql/etc/rc.d/init.d/postgresql-9.2 start

Back up the PostgreSQL embedded database - Virtual Appliance (CentOS-Linux)

Execute the following commands:

cd /usr/local/webhelpdesk/
sudo sh -c 'pgsql9/bin/pg_dump -Fc -v -h 127.0.0.1 -p 20293 -U whd whd > whd.pgdump'

Note: If prompted for a DB password use whd.
A backup file will be created in /usr/local/webhelpdesk/ with the name whd.pgdump.

Set up your Windows Server

  1. Log in to your Windows Server using a Local Administrator account.
  2. Temporarily disable the Windows Firewall, antivirus program, and User Account Control.
  3. Download the installer for WHD (same version you have in VA) for Windows Server (64-bit).
  4. Install WHD (same version you have in VA) for Windows Server (64-bit).
  5. Copy a backup file for whd.pgdump from your WHD VA to the new Windows Server (64-bit).
  6. Copy the following files from your WHD VA to this new Windows Server (64-bit):
    • <WebHelpDesk>\conf\whd.conf
    • <WebHelpDesk>\conf\keystore.jks 
    • <WebHelpDesk>\bin\jre\lib\security\cacerts

Note: The keystore.jks file only exists if WHD uses HTTPS with the SSL certificate.

Rename or drop the default empty PostgreSQL embedded WHD database in your own WHD Windows Server

  1. Run the following command:
    cd C:\Progra~1\WebHelpDesk
  2. Connect to the database using the following command:
    pgsql9\bin\psql -h 127.0.0.1 -p 20293 -U whd -d template1
    Note: If prompted for a password, use whd.
  3. Execute the following statements:
    ALTER DATABASE whd rename to whd_old;
    CREATE DATABASE whd;
  4. Enter \q to exit the psql tool.

Restore the PostgreSQL database backup

Enter the following commands:

cd C:\Progra~1\WebHelpDesk
pgsql9\bin\pg_restore -Fc -v -h 127.0.0.1 -p 20293 -U whd -d whd path_to_whd.pgdump

Note: If prompted for a password, use whd.

Deactivate the WHD license from the existing WHD VA

  1. Start the WHD application in your existing WHD VA.
  2. Log in to the WHD web application and go to Setup > General > License > License Settings.
  3. Click the padlock icon and copy the Customer Contact details and Activation Key to a text file.
  4. Click Deactivate.

Activate the WHD license on the new WHD Windows Server

  1. Start the WHD application in the new WHD Windows Server.
  2. Log in to the WHD web application and go to Setup > General > License > License Settings.
  3. Click the padlock icon and provide the Customer Contact details and Activation Key from the previous procedure.
    Note: If the Activation Key does not work, log in to the Customer Portal and retrieve your new Activation Key for WHD.
  4. Click Activate.

Perform an in-place upgrade to WHD 12.5.1

  1. Download the WHD 12.5.1 Windows Server (64-bit) from the Customer Portal.
  2. Upgrade the existing WHD version to WHD 12.5.1.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified
23:00, 19 Jun 2017

Tags

Classifications

Public