Field Descriptions
The tab contains the following columns and fields:
Category |
Column/Field |
Description |
||||||||
General |
The initial step in running an Electronic Update is to determine whether you are running it as a local or server update. For more information about these two types of updates, see Specifying an Update as Server or Local. |
|||||||||
Electronic Update Type |
Select the type of Electronic Update to run based how the Code Insight server obtains the Update Manifest and Update Data files required to perform the update:
Note:By default, downloading files from Revenera is performed using HTTPS. However, you can configure the download process to use SFTP instead. For more information, see “Configuring an SFTP Connection for Downloading Update Files” in the Code Insight Installation & Configuration Guide. This configuration must be performed prior to running updates. |
|||||||||
Local Electronic Update configuration |
If you intend to run a local Electronic Update, you must specify the location of the two required “update” files that you manually downloaded from Revenera. The location of each file must be locally accessible. To run the update, use the Run Update Now option. |
|||||||||
Update Manifest File |
Click Select File to search for and select the Update Manifest file (update_manifest.txt) to upload to the Code Insight server. The manifest file contains the following:
|
|||||||||
Update Data File |
Click Select File to search for and select the data archive (update.zip) file to upload to the Code Insight server. This archive contains data files that provide the CVSS information used by Code Insight to perform update. Code Insight uses the hash information in the manifest file (see the Update Manifest File field description) to ensure that the data files are the expected ones and have not changed or been tampered with. |
|||||||||
Configuration for automatic Electronic Updates (server update only) |
Code Insight enables you to configure server incremental updates to run automatically at a frequency you define, as described below. Note that you can always manually force an incremental or full update between the scheduled updates, or you can disable scheduled automatic updates altogether and manually run updates as needed. In either case, you would need to use the Run Update Now option to run an Electronic Update. |
|||||||||
Update Frequency |
Select from one of the available frequencies for running an incremental Electronic Update automatically:
You can always manually schedule an incremental or full update as needed using the Run Update Now option.
|
|||||||||
Save Schedule |
Click this button to save the schedule. Your future incremental updates will run automatically according to the frequency you defined. |
|||||||||
Configuration for manually running an Electronic Update |
You can manually run an Electronic Update at any time. The update is run immediately or placed in queue and initiated once all pending scans have completed. Currently, this is the only way to schedule a local update. If automatic server updates are also configured, a manually-run update is in addition to the automatic updates. |
|||||||||
Run Update Now |
Select the scope of the manually-run update:
|
|||||||||
Update |
Click this button to initiate the Electronic Update immediately or once pending scans are completed. |
See Also
“Configuring Code Insight” chapter in the Code Insight Installation & Configuration Guide