Action is an entity that represents a particular software function that a deployed cartridge performs at run time. A cartridge project usually contains multiple actions.

A general term for something you can create and define in Design Studio, such as custom actions and processors.

A scan that produces additional scan results from existing scan results. When configuring an assimilation scan, you can choose additional scans to serve as input to the assimilation scan.

Defines a period of time when a specified scan should not run, or be paused if already running. This can be used to avoid running scans during peak network traffic hours, or during a planned network outage.

A collection of actions, specifications, model collections, and scan parameter groups defined in Design Studio. Cartridges are built in Design Studio from projects. They are compiled as JAR files and then deployed into Network Integrity.

A data element that can be added to entity specifications to supplement default data elements. Characteristics on specifications appear in the Network Integrity UI as displayed information.

A scan that discovers your network. This can include network elements, physical resources, and logical resources.

The process where Network Integrity compares discovered network data with imported inventory data and reports on differences between the sets of data. Discrepancy detection is an optional part of a scan run.

The process where Network Integrity resolves discrepancies between discovered network data and imported inventory data.

A scan that imports network data from an inventory system.

Used to add specifications that exist in other cartridge projects into your cartridge project. Specifications from other cartridge projects inherit any changes and configurations you make to them in their original cartridge project.

Each processor is responsible for an atomic function. An action contains one or more processors. When an action is invoked, the processors are run in the sequence they were placed inside the action.

A special type of specification that adds fields to the Network Integrity UI. For example, you can add fields to the Create Scan page, allowing the Network Integrity user to pass scan parameter values to run-time scans.

Information related to outcomes for one or more Network Integrity scans, such as scan name, scan action type associated with the scan (discovery, import, or assimilation), data source assigned to each scan, current status of the scan (in progress, completed, completed with errors), date and duration of the scan run, details of errors in the scan, and a summary of detected discrepancies.

Determines when a scan runs. You can set a scan to run immediately, regularly, or on-demand.

You use specifications to extend the Information Model, which defines a base set of entities and their relationships. Most cartridges must extend the Information Model entities and therefore must make use of specifications. A specification used for model extension is associated with a single Information Model entity type. Multiple specification types can be defined for each Information Model entity type.

Special class that Design Studio generates for specifications.