Upgrade DPA on a Linux-based OS
If you are upgrading from DPA 2022.3 and you configured DPA 2022.3 for SAML authentication, be aware that DPA 2022.4 and later include changes to the SAML configuration. After the upgrade, no one will be able to log in with SAML until you update the configuration.
Before you upgrade, make sure you have a local login available.
After the upgrade, log in as a local user and complete the steps under "SAML configuration changes" in the DPA 2022.4 Release Notes to update the SAML configuration.
- Review the upgrade checklist and prepare your environment.
- Download the most recent version of DPA from the SolarWinds Customer Portal.
Log in to the DPA server as a user that owns all of the files in the DPA installation directory.
If the Find SQL indexes were moved to a custom location, the user must also own all of the files in the custom location.
To determine if the Find SQL indexes were moved and where, open the following file in a text editor:
Look for either of the following lines:
com.solarwinds.dpa.findSql.index.location=your_custom_location(if all indexes were moved to the same directory)
com.solarwinds.dpa.findSql.index.location.db_id=your_custom_location(if indexes for a specific database were moved)
If neither of those lines are present, the indexes are in the default location:
- Install the new version in a new directory on your existing server.
./shutdown.shfrom the old installation directory.
Locate the directory that was created when you installed the new version:
/home/dpa_x_x= old installation home
/home/dpa_y_y= new DPA home
Copy or move these directories from the old installation to the new:
Do not copy hotfix files.
mv OLD_home/iwc/tomcat/ignite_config/* NEW_home/iwc/tomcat/ignite_config/
cp -rp OLD_home/iwc/tomcat/ignite_config/* NEW_home/iwc/tomcat/ignite_config/
Copying Find SQL index data might take some time.
If you are upgrading from DPA 2023.2.100 or earlier to DPA 2023.4 or later, complete the following steps:
/iwc/tomcat/conf/context.xmlin a text editor.
Delete the following string:
This string fixed an issue in previous versions of Tomcat. It is no longer needed, and it should be removed for security reasons.
Save the file.
If you encrypted the keystore password for SSL/TLS in the Tomcat server configuration file used by DPA, copy or move the following file from the old installation to the new:
- If you changed the default SolarWinds DPA ports, then you must modify the
server.xmlfile in the new installation to incorporate the port changes from your earlier installation.
./startup.shfrom the new directory.
To complete the upgrade:
Update any system startup files or cron job scripts that were created for the older version.
Ensure the older version of DPA cannot start because this will cause conflicts with your ports, monitored instances, and the repository.
If you have configured DPA to use a custom certificate for SSL/TLS, migrate the custom certificate.
If one or more DPA licenses are expired, you must remove the expired licenses before DPA can complete the repository upgrade. When all licenses are compliant, you can complete the upgrade process by opening DPA and clicking Proceed with upgrade.