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 > Database Performance Analyzer (DPA) > Upgrade DPA on UNIX or Linux

Upgrade DPA on UNIX or Linux

Table of contents
Created by Interspire Import, last modified by Melanie Boyd on Oct 13, 2017

Views: 172 Votes: 0 Revisions: 21

Overview

This article provides steps to upgrade DPA 8.x or 9.0 to 9.1 or later versions. 

Environment

All versions

Steps

NOTE: Due to changes on the licensing side, make sure you are using the correct upgrade instructions below. 

 

Upgrading DPA 8.x or 9.0 to 9.1+

1. Stop DPA

  • On the server that holds the existing installation, shut down DPA (run <install_dir>/shutdown.sh).  Also, if a cron job was set up, make sure it is commented out during the upgrade.
  • Take a backup of your repository.

 

2. Install DPA

  • Install the new version of DPA, which will create a new version-specific directory during the installation.
  • Locate the new installation directory that was created when you ran the installer. For example:

             /home/confio/ignite_9_0_150       <= old home

             /home/solarwinds/dpa_9_2_219      <= new home

 

3. Configure new home (Do NOT copy any hotfix files)

Review /iwc/tomcat/ignite_config/idc files (.properties files) to make sure they are correct.

  • Rename the system.properties file in the new home to system.properties_orig.
  • Copy the system.properties file from the old home into the new home.
  • Edit repo.properties and make sure values are all correct. (If you are keeping the same repo, you can copy over the repo.properties file from the old home.)
  • Edit server.properties file to make sure heap sizes are same/same as old installation.

 

If you are using ssl, LDAPS or have changed the default ports

Check your configuration of new_home/iwc/tomcat/conf/server.xml against the old_home.

  • Notable changes are: we install with our own .keystore using encryption for Orion integration with a new default port of 8124.
  • If you had imported certificates into the old .keystore, you will have to repeat that process.  Helpful KB article: Enabling SSL

 

4. Licenses

If you are upgrading from 8.x or 9.0 to 9.1+,DPA versions 9.0 and earlier used an older licensing model and all licenses can be left behind.  With 9.1+, your new licenses will be available in your customer portal.  If you need assistance with your customer portal, please contact customer service (customerservice@solarwinds.com).

 

5. Completing your upgrade

  • Start the new version by running the startup.sh script in the new home directory.
  • When you launch the UI for the first time, it will ask you to activate a valid key.  Those are available in your customer portal.  If you are doing an offline activation (no internet connectivity from DPA host), there are instructions built into the license manager for offline activation.  Otherwise, this KB article will provide instructions: Gen3 Offline Key Activation
  • The first time you activate a valid key, you will need to click proceed with upgrade.  That will run some DDL against the repository.
  • Update any system startup files or cron job scripts that may already exist for the older version.
  • Ensure the older version of DPA cannot start as it will cause conflicts with your ports, monitored instances, and the repository.
  • For assistance, submit a ticket via your customer portal.

 

 

Upgrading DPA 9.1+ to a later version

1. Stop DPA

  • On the server that holds the existing installation, shut down DPA (run <install_dir>/shutdown.sh).  Also, if a cron job was set up, make sure it is commented out during the upgrade.
  • Take a backup of your repository.

 

2. Install DPA

  • Install the new version of DPA, which will create a new version-specific directory during the installation.
  • Locate the new installation directory that was created when you ran the installer. For example:

             /home/confio/ignite_9_1_185       <= old home

             /home/solarwinds/dpa_9_2_219      <= new home

 

3. Configure new home

Review /iwc/tomcat/ignite_config/idc files (.properties files) to make sure they are correct. 

  • Rename the system.properties file in the new home to system.properties_orig.
  • Copy the system.properties file from the old home into the new home.
  • Edit repo.properties and make sure values are all correct. (If you are keeping the same repo, you can copy over the repo.properties file from the old home.)
  • Edit server.properties file to make sure heap sizes are same/same as old installation.

 

If you are using ssl, LDAPS or have changed the default ports

Check your configuration of new_home/iwc/tomcat/conf/server.xml against the old_home

  • Notable changes with 9.2+ are: we install with our own .keystore using encryption for Orion integration with a new default port of 8124.
  • If upgrading from 9.1 AND you had imported certificates into the old .keystore, you will have to repeat that process.  Helpful KB article: Enabling SSL

 

4. Licenses

If you are retaining the repository database,move (cut and paste, do not copy) the old_home/iwc/tomcat/licensing directory to the new_home/iwc/tomcat/ directory.

If you are creating a new repository database: 

  1. Deactivate all your licenses in the old DPA installation by following this KB article.
  2. Activate the licenses in the new DPA installation after your create the new repository.

 

5. Completing your upgrade

  • Start the new version by running the startup.sh script in the new home directory.
  • When you launch the UI for the first time, it will ask you to activate a valid key.  Those are available in your customer portal.  If you are doing an offline activation (no internet connectivity from DPA host), there are instructions built into the license manager for offline activation.  Otherwise, this KB article will provide instructions: Gen3 Offline Key Activation
  • The first time you activate a valid key, you will need to click proceed with upgrade.  That will run some DDL against the repository.
  • Update any system startup files or cron job scripts that may already exist for the older version.
  • Ensure the older version of DPA cannot start as it will cause conflicts with your ports, monitored instances, and the repository.
  • For assistance, submit a ticket via your customer portal.
Last modified
16:09, 13 Oct 2017

Tags

Classifications

Public