Overview of Electronic Update Setup

The following describes the basics for configuring electronic updates:

•

Scheduling Electronic Updates

•

Notification of an In-Progress Electronic Update

Specifying an Update as Server or Local

The Electronic Update Type field (see Field Descriptions below) on the Electronics Update tab enables you to configure the Electronic Update to run as either a server or local update. The difference between the two methods is the means by which the Code Insight server obtains the files required to run the update:

•

During a server Electronic Update, the most recent Electronic Update files are automatically downloaded from Revenera to the Code Insight server prior to processing the update.

•

For a local Electronic Update, you must manually download the Electronic Update files from Revenera to a location that is locally accessible to the Code Insight server, such as a shared drive or a local USB drive. Then, when an update is triggered, the Code Insight server automatically uploads the files and proceeds with the update. This type of Electronic Update is useful when the Code Insight server has no external Internet access or when a specific Electronic Update version is needed for testing or demo purposes.

By default, the file download 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 before running updates.

Scheduling Electronic Updates

The remaining fields (see Field Descriptions below) on the Electronic Updates tab allow you either to schedule an Electronic Update to run automatically at regular intervals or to manually request an update as needed. By default, an update is incremental (that is, the update applies on changes from the previous update). However, you have the option force a full Electronic Update, which replaces all data from the previous update. (A full update might be necessary, for example, if the most recent update did not complete properly.)

In summary, you can schedule the following:

•

An incremental Electronic Update (server type only) that runs automatically at a regular frequency that you define.

•

An incremental Electronic Update (server or local type) that you manually run as needed.

•

A full Electronic Update (server or local type) that you manually run when necessary. Use this option with caution as forcing a full update to run will take several hours to complete, similar to the initial update run when Code Insight was first installed.

Note:Codebase scans cannot be performed during the Electronic Update process, but a scan that is already underway will not be interrupted when an update is scheduled to begin. The Electronic Update will be queued and automatically run based on queue order.

Notification of an In-Progress Electronic Update

Whenever an Electronic Update is in progress, a banner is displayed at the top of the Code Insight UI, indicating that an update is running and that scheduled scans will resume once the update completes. The banner is shown for any Electronic Update—whether server or local, forced or automatically run by schedule—and persists across all Code Insight pages.

The banner is automatically closed once the Electronic Update completes. (Users cannot manually close the banner.)