Performing the Diagnostics Server upgrade

Use this procedure to upgrade the BMC Application Diagnostics Server to the latest version, including any feature packs.

• To upgrade to version 2.6.x, you can upgrade from 2.1.x or later, and then apply the POODLE security patch.
• To upgrade to Feature Pack 1 (version 2.7.01), you must first upgrade to 2.6.x. Version 2.7.01 includes a POODLE security patch that is automatically applied.

You can upgrade Diagnostics Server components using the upgrade wizard, or you can upgrade the components using the silent upgrade procedure, and deploy the silent upgrade to several computers.

When you run the installation wizard on a system with a previous version of the product, the wizard automatically switches to upgrade mode for the installed component or components, and enables you to install components that are not on the same computer.

Before you begin

• Download the installation files from the Electronic Product Distribution site to a temporary directory on the Server computer.

• Back up the database.

  Note

  The upgrade process modifies the database schema. You will need the database backup if you want to revert to the previous version.

• Ensure that you have completed all preinstallation tasks.
• Review the Preparing-for-a-BMC-Application-Diagnostics-upgrade-and-checking-compatibility topic.
• You must have administrative privileges on the computer where you perform the upgrade.

To upgrade the BMC Application Diagnostics Server

1. On the computer where you want to upgrade the Diagnostics Server component or components, launch the installation wizard:

   • Windows
     Navigate to ADOPServer\Disk1 and double-click setup.cmd.
      In Windows 2008, the system may require you to right-click the setup.cmd icon to select to Run as administrator.
   • Linux
     
     1. Before running the wizard, ensure that you have a DISPLAY environment variable set.
     2. Navigate to ADOPServer/Disk1 and run setup.sh.

   Note

   If you see an error about the database encryption method, see Upgrading-the-Diagnostics-Server-stops-because-of-database-encryption-method.

2. In the BMC Application Diagnostics Server Installer Welcome page, click Next.
3. On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next. If you do not agree to the terms of the license agreement, the upgrade process will end.
4. If prompted, select the upgrade component.
   • If both the BMC Application Diagnostics Portal and Collector are installed on the computer, the utility skips the Features page and both components are upgraded.
   • If one or more server components are not installed, you can select to install another component on the Features page.
     For instructions about installing the new component, see Performing-the-Diagnostics-Server-installation.
5. Enter the MySQL root password to update the database tables.
   If the root password was not changed since installation, do not change the entered password.
6. If you did not previously upgrade the MySQL to version 5.6.14, select the data management method for the upgrade:
   • Copy. The data directory is copied to the new database.
     If you do not have enough space, this option is disabled.
   • Move. The data directory is moved to the new database. The previous database is deleted at the end of upgrade process.
7. Verify that the information on the Installation Preview page reflects your upgrade correctly. Click Previous to make changes, or click Install.
8. After the upgrade is complete, click View Log to view the log files and confirm that the upgrade process was successful.
9. Click Done to exit the installation wizard.

To patch the Application Diagnostic Server 2.6.x components for POODLE security vulnerability

This patch repairs the POODLE (Padding Oracle On Downgraded Legacy Encryption) security vulnerabilities for communication between Application Diagnostics Agents for Java and Application Diagnostics Server components. Ensure that you select the Patches tab when you download the installation files for BMC Application Diagnostics.

Extract and replace the required file on the Application Diagnostics Portal, Collector, and Proxy servers, and modify the property files as instructed.

If the Portal, Collector, and APM Proxy are installed on the same computer, replace the file once, otherwise, replace it for each installation.

1. Stop the service or services.
2. In the server installation directory, under the common/lib directory, replace common-server.jar with the extracted file from this patch.
   The following file paths show the default installation directory:
   • (Windows) C:\Program Files\BMC Software\BMC Application Diagnostics\common\lib
   • (Linux) /opt/bmc/BMC_Application_Diagnostics/common/lib

3. In the Portal installation directory, under portal/lib directory, replace the portal.jar with the file in this patch.

   The following file paths show the default installation directory:

   (Windows) C:\Program Files\BMC Software\BMC Application Diagnostics\portal\lib

   (Linux) /opt/bmc/BMC_Application_Diagnostics/portal/lib

4. Open the properties file for each component in a text editor:
   • Portal: installationDirectory\portal\properties\portal.properties
   • Collector: installationDirectory\collector\properties\collector.properties
   • APM Proxy: installationDirectory\apm-proxy\properties\apm-proxy.properties

5. For each component properties file, add the following lines for the tomcat.ciphers and the tomcat.ssl.enabled.protocols properties:

   # A comma separated list of encryption ciphers to support for HTTPS connections. Spaces between list items are not allowed.
   tomcat.ciphers=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA
   
   #The comma separated list of SSL protocols to support for HTTPS connections. Spaces between list items are not allowed.
   #Default Value: TLSv1,TLSv1.1,TLSv1.2
   tomcat.ssl.enabled.protocols=SSLv2Hello,TLSv1,TLSv1.1,TLSv1.2
6. Restart the service or services.

Where to go from here

Verifying-the-Diagnostics-Server-upgrade

Upgrading-the-Diagnostics-Agent-for-Java

Upgrading-the-Diagnostics-Agent-for-NET