About an Import
FlexNet Code Insight 2020 R2
The FlexNet Code Insight project-data import feature is available through these interfaces:
| • | FlexNet Code Insight Web UI, as described in Importing Project Data Using the Web UI |
| • | FlexNet Code Insight REST interface, as described in Importing Project Data Using the REST API |
The following sections provide overview information about the import process.
Input Used in the Import Process
The input for a project data import is an archived JSON data file containing project data. During the import process, this JSON data file (called the import data file in this documentation) is extracted from the archive and imported to a specific FlexNet Code Insight project, called the target project.
You can create this input archive in a couple of ways:
| • | Use the FlexNet Code Insight project-data export feature (see Exporting Project Data) to export data from a Code Insight v7 project. |
| • | Export data from a FlexNet Code Insight v6 project (see the FlexNet Code Insight 6.14.x documentation for instructions). Then use the Audit Migration Tool to convert the exported data into the format required for importing in a v7 project. |
| • | Manually create the import data file using data exported from an external system and formatting it as JSON code. Then compress the data file as a .zip archive. |
In all cases, the input for the import process must be a data file whose contents are in the expected JSON format and that has been archived as a .zip file.
The project data import is typically performed on a target project that is created as a “standard” project—that is, a project whose associated codebase is uploaded to Code Insight for scanning. An import to a standard project, called a standard import, requires a scan of the target project codebase prior to the import in order to build the codebase file tree and to prepare the project for storing file information. The import process creates inventory with file associations and provides access to the codebase files through the Analysis Workbench in the target project. The imported inventory is live—that is, ready to be edited and reviewed.
Alternatively, an import can be performed on a target project that was created as an “inventory only” project—that is, a project whose codebase is not uploaded to Code Insight but is scanned remotely. An import to an inventory-only project, called an inventory-only import, creates live inventory without any file associations in the target project and does not provide access to the codebase files since none are imported. (The Analysis Workbench is not available in the target project.)
For more information about the import types and the data imported for each, see the next section, Comparison of Standard and Inventory-Only Imports.