Setting Up Electronic Updates

An initial full Electronic Update is run automatically after your initial startup of Code Insight. It provides the basis of a local data library used by Code Insight to identify OSS and third-party code in your codebase. After this initial update, Code Insight provides a means for you to schedule additional Electronic Updates to keep the library up to date, helping to ensure that the latest component, version, license, and vulnerability information is available for your product. You can schedule these updates to execute automatically at a regular frequency or manually through the Administration interface.

At a basic level, an Electronic Update is executed as either a server or a local update, depending on the method used to retrieve the Electronic Update files from Revenera. You configure the type of update to run based on your site requirements.

By default, scheduled Electronic Updates are incremental—that is, each update applies only changes that have occurred since the previous update. However, when necessary, you can force a full update, which overwrites all data from the previous update. Full updates should be run manually only and with the understanding that they require considerable overhead.

Refer to the following for more information:

• Server vs Local Electronic Updates

• Running Server Electronic Updates

• Running Local Electronic Updates

• Configuring the Use of SFTP for Obtaining Update Files

• Configuring the Electronic Update to Skip the Post-Update Phase

• Tracking the Progress of an Electronic Update