Summary
An integration run has the following steps:
- Retrieve devices from Open-AudIT.
- Create a node file suitable for passing into node_admin.pl.
- Create a new node if one does not exist, or update an existing node if it does.
- Update the mapping of Open-AudIT devices to NMIS nodes.
- Update the device on the Open-AudIT server if necessary.
Configuration
The following is a sample configuration file for the integration. The configuration is written in the .nmis format common to other Opmantek products.
%hash = (
'log_path' => 'log/nmisintegration.log',
'node_admin_path' => '/usr/local/nmis/admin/node_admin.pl',
'open_audit_details' => {
'host' => 'https://demo.opmantek.com',
'log_path' => 'log/openauditapi.log',
'password' => 'OA_password',
'user' => 'OA_user'
},
'open_audit_lookup_path' => 'conf/oa_nmis_lookup.nmis',
'open_audit_query_ids' => [60, 77],
);
| Key | Type | Description |
|---|---|---|
| log_path | A string representing either a fully-qualified path, or a path relative to the integration's execution. | The path for the integration log. This log will contain a summary of actions that are taken for each integration, including system calls to node_admin.pl. |
| node_admin_path | A string representing either a fully-qualified path, or a path relative to the integration's execution. | The path to the executable for the node admin tool. All interactions with NMIS are controlled via the node admin tool. |
| open_audit_lookup_path | A string representing either a fully-qualified path, or a path relative to the integration's execution. | The path to the lookup file for the integration. The lookup file stores mappings between Open-AudIT devices and NMIS nodes. It is recommended to give this file a .nmis extension, as it is written in the .nmis format. |
Usage
To run the integration, simply invoke the executable and pass it a configuration file as described in the previous section. You can also invoke the tool by itself, which will look for a configuration file at conf/nmisIntegration.nmis by default.
The rest of the integration is completely driven by the options set in the configuration file.
# Calling the tool with a custom-named configuration file ./bin/oa_nmis_integration.pl conf/my_custom_config.nmis # Calling the tool by itself (uses conf/nmisIntegration.nmis) ./bin/oa_nmis_integration.pl