The Candidates List

The Candidates List lets you select the Security Gateways, on which to install the CPUSE packages.

The Candidates List is a CSV (comma-separated values) file generated by CDT. This list contains the supported Security Gateways and Cluster Members in the Security Management Server or Domain Management Server database.

How it Works

The CDT generates the Candidates List for the package to install:

  • In Basic Mode - as defined in the configuration file.

  • In Advanced Mode - according to the first package in the Deployment Plan.

The CDT assigns:

  • A batch number to Security Gateways that are eligible for package installation.

  • A value of N/A to Security Gateways that are not eligible for package installation. Do not change this value.

  • A value of Installed to Security Gateways, on which the requested package is already installed. Do not change this value.

To make sure the CDT does not install a package on the specified Security Gateways:

  • You can change the candidates in the Candidates List after you generate this list. Edit the Candidates List file with a text editor. Make sure to save the file as a simple CSV file.

  • In the Candidates List, you can change only the values in the Upgrade Order column.

  • To unmark a Security Gateway from a package installation, replace its batch number with "-" (minus character).

  • Security Gateways that are not eligible for package installation, have a value of N/A. Do not change this value.

  • Security Gateways that already have the requested package installed, have a value of Installed. Do not change this value.

For information about clusters, see Package Installation in Clusters.

Installation Batches

An installation batch is a set of one or more Security Gateways.

CDT installs the packages in parallel on all batch members that have the same batch number.

When the installations on all candidates in a batch completes, the next batch is run.

The installation completes when all the batches are completed.

A new batch does not start, if it is after the date and time defined in the configuration file.

Note - All members of the same cluster must be in the same batch.