If you use the non-embedded, non-default MySQL as your primary database, install the database and manually populate your time zone system tables with data.īeginning in version 12.5, you can search for tickets using two new qualifiers: (MySQL only) Prepare the time zone tables. Install the database on a dedicated drive with at least 20 GB of space to accommodate the database engine, management tools, help desk tickets, and ticket file attachments. If you use the non-embedded, non-default SQL Server or MySQL as your primary database, install the database engine and management tools according to the instructions included with your software. (SQL Server and MySQL only) Install the database management tools. (Optional) Select a database that supports failover clusters.This directory includes files used to support a FIPS configuration. Navigate to \conf\additional and back up the fips-140-2 directory to a safe location.This directory includes the Network Security Services (NSS) libraries required to enable FIPS. Navigate to \bin and back up the nss-圆4 directory to a safe location.If you do not plan to enable FIPS, go to step 2. Navigate to \conf\ and back up your current tomcat_web_template.xml file to an external directory.If you have an embedded PostgreSQL database, navigate to and back up the pgsql9 directory to a safe location. The upgrade procedure replaces the tomcat_web_template.xml file with an updated file that includes the new version settings.īack up any database server associated with WHD. If required, you can enable FIPS during the upgrade. Perform the following steps to upgrade WHD with FIPS currently disabled in your deployment. See System requirements for a list of supported Microsoft SQL Server, MySQL, and PostgreSQL databases. See Web Help Desk Previous Version Documentation to access installation and administrator guides for WHD 12.5.2 and later. This section describes how to upgrade your WHD FIPS or non-FIPS or FIPS deployment to the latest release. Locate your database credentials before you perform the upgrade. If you are upgrading to WHD 12.7.12, you will be prompted to re-enter your database credentials, including the database name, username, and password. See Upgrade with FIPS enabled for instructions. If you are running WHD 12.7.7, upgrade to the latest release. When you are finished, upgrade to the latest release. If you are running WHD 12.7.6 or earlier, upgrade to WHD 12.7.7 first. During the upgrade, you can enable FIPS, if desired. See Upgrade with FIPS disabled for instructions. If you are running WHD 12.7.7 with a MySQL or Microsoft SQL Server database, upgrade to the latest release. See How to upgrade Web Help Desk to version 12.7.7 using PostreSQL as the database for instructions. If you are running WHD 12.7.7 with an embedded PostgreSQL database, verify that you upgraded the PostgreSQL database to version 13.3. If you are running WHD 12.7.6 or earlier with a MySQL or Microsoft SQL Server database, upgrade to the latest release. If you are located outside the continental United States, contact Technical Support for assistance with upgrading to WHD 12.7.7 with an embedded PostgreSQL database. If you are running WHD 12.7.6 or earlier with an embedded PostgreSQL database, upgrade to WHD 12.7.7 first. Review the instructions below for upgrading a non-FIPS and FIPS deployment. You cannot roll back an installation once it is completed. If you have a test or staging environment, SolarWinds recommends testing the upgrade first. See the upgrade gotchas to troubleshoot errors that may appear during the upgrade. See Database migration options for details. Upgrading WHD may add new database tables, but the procedure does not impact your database and database table data. Be sure to determine your upgrade path before you get started. This section describes how to upgrade WHD from a currently-supported version to the latest version.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |