Upgrading

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.

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.
  • You must manually change the Java Heap size to 4GB (or comment out the current java heap size default of 4GB from the jvm.options file under the path: C:\Program Files\IBM\SCA\wlp\usr\servers \server1) for Upgrade fixlet to upgrade the existing v1.9.x and v1.10.x to 2.0.4.x deployment.
  • Even after the upgrade, it is recommended to change the Java Heap size to 8GB in jvm.options file under the path: C:\Program Files\IBM\SCA\wlp\usr\servers \server1.
  • A fixlet Warning: Low Heap Size Setting - Bigfix Compliance Server is introduced to help you check the heap size before you start using the Upgrade fixlet.
  • Restart the BigFix Compliance from BigFix Services.

About this task

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.