Upgrading

Before you begin

Updating from an earlier version requires updating the data schema as well. The operator must access the BigFix Compliance Analytics web interface from the server hosting BigFix Compliance Analytics. Click Upgrade Schema.
Note:

Before you start the upgrade process, it is strongly recommended that you perform server and database back-up.

About this task

When upgrading from earlier versions of BigFix Compliance Analytics, the installer replaces the previously supplied server certificate and private key pair with a new self-signed certificate and key pair.
Note: BigFix Compliance version 1.5.78 is the minimum version required to upgrade to BigFix Compliance 1.8 and BigFix Compliance 1.9. Refer to the following table for the upgrade steps required for the different BigFix Compliance Analytics version.
Table 1. Upgrade steps for BigFix Compliance Analytics versions
If you're in version Follow these upgrade steps:
1.5.78 or earlier
  1. Upgrade to version 1.5.78
  2. Upgrade to version 1.7 or 1.8
  3. Upgrade to version 1.9
1.6.139 or earlier Upgrade to 1.7 or 1.8, then upgrade to 1.9

BigFix Compliance Analytics 1.6 and later uses HCL WebSphere. Earlier versions use Jetty as an application server.

To upgrade from earlier versions of BigFix Compliance Analytics, you must configure your SSL certificate settings again. To apply the settings again, go to Management > Server Settings when installation is completed.

Procedure

  1. Click Replace in the Certificate section.
  2. Click Browse... and select your server certificate and private key.
  3. Enter the private key password.
  4. Click Save and restart BigFix Compliance Analytics.
    If the original certificate and key pair are difficult to get or are unavailable, follow the steps in Migrating Keystores.