Configuring the server after upgrading from version earlier than 9.0.1.2

If you upgraded from versions earlier than application update 9.0.1.2, you might be required to perform additional configuration. The configuration panel opens automatically. You can also complete the configuration later at https://hostname:9081.

Optimizing the volume of scanned file data

You can optimize the volume of data that you monitor and use for creating custom signatures by narrowing down the list of collected file extensions to those that are typically used. This reduces the workload on the application server and improves the performance.

Procedure

  1. On the configuration panel, select the Optimize the volume of scanned file data check box.
  2. Check whether the software catalog that is uploaded to BigFix Inventory is in the canonical format. Click Management > Catalog Upload and check the Catalog Format column.

    Canonical catalog
    If the catalog is in the native format, upload a new catalog. If the catalog is in the canonical format, but a new version is available, upload the new catalog. Otherwise, proceed to the next step.
  3. Run an import.
    During this import, performance might be lower because the software catalog is imported.
    Important: After the import, some software items might not be visible in the reports. This is an expected behavior. Complete the remaining steps for the software inventory to be properly reported.
  4. Wait for the scheduled software scan. Alternatively, if you have infrequent software scans, stop the current scan and start a new one. This allows you to use the optimized list of file extensions in a shorter time.
    1. Log in to the BigFix console and, in the left navigation tree, click Actions.
    2. In the upper-right pane, click Initiate Software Scan and then click Stop.
    3. Initiate a new software scan.
  5. Wait for the scheduled import or run it manually. From now on, the optimized list of file extensions is used.
  6. If you upgraded from Software Use Analysis 9.0, the default Java heap size is not sufficient for the current version. Increase the Java heap size to 1536 megabytes (Xmx1536m).

Configuring without optimizing the volume of the scanned file data

If you do not want to optimize the volume of the scanned file data, clear this option. You can narrow down the list of collected file extensions manually at any later time.

Procedure

  1. Clear the Optimize the volume of scanned file data check box.
  2. Run the import of data to be able to see complete infrastructure information.
  3. If you upgraded from Software Use Analysis 9.0, the default Java heap size is not sufficient for the current version. Increase the Java heap size to 1536 megabytes (Xmx1536m).