About an Import

FlexNet Code Insight 2019 R3

Project data import is available through the FlexNet Code Insight REST interface, as described in Importing Project Data. The following sections provide overview information about the import process.

Input Used in the Import Process

The input to the API is an archived JSON data file containing project data. The archive is first decompressed and the included data file is then applied to the specified target project (that is, the project to which the data is imported).

You can create the JSON data file for input by performing an export from a FlexNet Code Insight v7 project (according to the instructions in Exporting Project Data) or by performing an export from a Code Insight v6 project and then using the Audit Migration Tool to convert the data into the required format. You can also create the JSON file manually from data exported from an external system. In all cases, the input to the API must be a data file of the expected JSON data format.

Target Project Types

Import is typically performed on a target project that was created as a “standard” project and is associated with an already-scanned codebase. A scan of the target project codebase is required prior to the import in order to build the codebase file tree and to prepare the project for storing file information. This type of import creates inventory with file associations and provides access to the codebase files through Analysis Workbench. The inventory is live—that is, ready to be edited and reviewed.

Alternatively, an import can be performed on a project that was created as an “inventory only” project and that does not require a scanned codebase. This type of import creates live inventory without any file associations and does not provide access to the codebase files through Analysis Workbench.

For more information about the import types and the data imported for each, see the next section, Comparison of Standard and Inventory-Only Imports.

Open topic with navigation