Actions accomplish a particular function in Network Integrity at run time. Actions contain one or more processors.
Processors perform the sub-tasks of an action. See "Working with Network Integrity Processors" for more information.
By grouping processors in an action, the action can achieve a complex function such as discovering a network, importing an inventory system, assimilating discovered data, or detecting and resolving discrepancies.
At run time, actions are implemented as J2EE message driven beans (MDBs).
You can create the following types of actions:
Discovery action: Discover data (typically from a network) and save it in the Results Model. See "About Discovery Actions for Network Integrity" for more information.
Import action: Import data (typically from an inventory system) and save it in the Results Model. See "About Import Actions for Network Integrity" for more information.
Assimilation action: Process data (typically discovered data) and save it in the Results Model. See "About Assimilation Actions for Network Integrity" for more information.
Discrepancy detection action: Find discrepancies between discovered and imported data. See "About Discrepancy Detection Actions for Network Integrity" for more information.
Discrepancy resolution action: Solve discrepancies in an external system or a network. See "About Discrepancy Resolution Actions for Network Integrity" for more information.
When creating actions, you can configure them as abstract actions. See "About Abstract Actions for Network Integrity" for more information.
Creating Network Integrity Actions
Abstract actions are models of actions to be extended by other actions. Abstract actions cannot be deployed.
Abstract actions do not generate many build errors and do not need extensive configuration.
Discovery actions discover data, typically from the network, and to save the discovered data in the Results Model. Discovery actions can access networks using various technologies and protocols.
Network Integrity users trigger discovery actions by running a discovery scan.
Discovery actions are made up of discovery and SNMP processors. See "Working with Network Integrity Processors" for more information.
Discovered data is saved in the Oracle Communications Information Model. Discovered data is flagged as having come from a network system. The Network Integrity UI displays and reports on discovered data.
Discovery actions can be configured with address handlers. If the discovery action is configured with an address handler, Network Integrity can validate the addresses configured in the scope of a discovery scan at run time. Invalid addresses are identified before running a scan that would otherwise end in failure. See "About Address Handlers for Network Integrity" for more information.
A discovery action must be configured with a valid result category. See "About Result Categories for Network Integrity" for more information.
About Network Integrity Actions
Import actions import data, typically from an inventory system, into Network Integrity. The data is stored in the Information Model and is flagged as having come from an inventory system. The Network Integrity UI displays and reports on the imported data.
Network Integrity users trigger import actions by running an import scan.
An import action must be configured with a valid result category. See "About Result Categories for Network Integrity" for more information.
About Network Integrity Actions
Assimilation actions perform additional processing on existing Network Integrity data, typically from the network, to derive or construct additional information, and to save the assimilated data in the Results Model. An assimilation action can use the results from a discovery or import scan or from another assimilation scan as input for additional processing.
Network Integrity users trigger assimilation actions by running an assimilation scan.
For example, an assimilation action might be used to derive connectivity relationships between endpoints discovered by previous scans.
Assimilated data is saved in the Information Model. Assimilated data is flagged as having come from a network system. The Network Integrity UI displays and reports on the assimilated data.
An assimilation action must be configured with a valid result category. See "About Result Categories for Network Integrity" for more information.
About Network Integrity Actions
Discrepancy detection actions compare network data with inventory data and report differences.
Network Integrity users trigger discrepancy detection actions by running a discovery, import, or assimilation scan with the Detect Discrepancy option enabled.
You can also create a discrepancy detection action that automatically resolves some types of discrepancies. See the Network Integrity Developer's Guide for more information.
Discrepancy detection actions must be configured with a valid result source. See "Adding Result Sources to Network Integrity Actions" for more information.
About Network Integrity Actions
Discrepancy resolution actions act on an external system to resolve a discrepancy. Discrepancy resolution actions can update a mismatch in an inventory system using information gathered from the network or can generate a trouble ticket to begin a network configuration change process.
Network Integrity users trigger discrepancy resolution actions by selecting detected discrepancies and selecting a resolution command.
About Network Integrity Actions