Description of the Electronic Update Phases

The following table provides a description of each Electronic Update phase that is visibly tracked on the Electronic Update Progress pop-up window. (This pop-up window is accessed from the Electronic Update notification message that is displayed on each Code Insight page when an update is in progress, as described in Monitoring the Progress of Electronic Update Phases.)

The phases indicated in the table as “Server update only” do not apply to a local update. All other phases apply to both server and local updates. For a information about the differences between these two types of updates, see Differences in Process Between Server and Local Electronic Updates.

Phase

The Electronic Update is...

Waiting for active scans to finish

Waiting for any active scans to complete before starting.

Note:Normally other jobs are not allowed to run when an Electronic Update is Active. The one exception is that one or more scans can still be running at the point when the Electronic Update is placed in an Active state. Therefore, this phase is included. For more details, see About Electronic Update Jobs.

Downloading update files

(Server update only) Downloading the files containing the latest component and CVSS data from Revenera to the Code Insight server.

Extracting update files

(Server update only) Extracting data files from the downloaded update.zip file.

Updating table <TABLE_NAME> (x/27)

Updating the twenty-seven Code Insight database tables with the latest component, license, and CVSS data. The name of the table currently being updated is listed, along with its position in the table sequence (for example, table number 11 out of 27).

Remapping of data

Remapping of any custom data that was created before the update but that is now recognized and reinstated by the update. (Data is considered custom if it did not originally exist in the Code Insight database but was manually created by users through Code Insight.) License details are also updated during this phase.

Generating alerts and creating remediation tasks

Processes security vulnerability information and does the following:

•

Generates alerts in the user interface for the inventory items associated with the new vulnerabilities.

•

Issues email notifications to the project owners, identifying the specific inventory associated with each new vulnerability.

•

Creates remediation tasks inventory rejected during this phase, as dictated by the project’s policy profile and remediation options (see Updating Inventory Review and Remediation Settings for a Project).

Indexing components and vulnerabilities

Indexes all the current entities in the updated Code Insight database.

Differences in Process Between Server and Local Electronic Updates

Code Insight enables you to configure the Electronic Update to run as either a server or local update, as described in detail in the Code Insight Installation & Configuration Guide. The basic difference between the two methods is the means by which the Code Insight server obtains the files required to run the update. As a result, the phases monitored in the Electronic Update Progress pop-window for these two type of updates are slightly different.

•

A server Electronic Update performs all phases of the update automatically, including the download of the update files from Revenera. Therefore, all phases available on the Electronic Update Progress pop-up window are tracked.

•

For a local (offline) update, a user must manually download the Electronic Update files from Revenera to a local machine accessible to the Code Insight server. The Electronic Update then locates the downloaded files, uploads them to the Code Insight server, and extracts them. These operations must be completed before the local Electronic Update is eligible for Active status. As a result, the initial Downloading upload files and Extracting upload files phases are not monitored in the Electronic Update Progress pop-up window.