Auditor Help:

External Data Integration

To further enhance auditing and compliance documentation within the software, Ecora allows you to report additional custom attributes that you define, such as serial number, manufacturer, department, location, etc.

To collect and report external data:

  1. Choose Tools... External Data Integration... from the main menu.
  2. Select the Unix or Windows tab.
  3. External Data Integration - unixExternal Data Integration - windows

  4. Click the Add button.
  5. Name the attribute you wish to report.
  6. New Attribute

  7. Click OK.
  8. Click the Import CSV button if you wish to include a comma-separated value file and locate that file in the open dialog box that appears.
    Note If you do not import the values with a CSV file, you must define the values for each system during collection (see Unix or Windows System Properties).
  9. Click OK.



CSV Specifications for EDI

  1. Column A, Row 1 must be the System value.
  2. Columns B (and greater), Row 1 must contain optional custom attribute field names.
  3. Column A Row 2 (and greater), can be blank, Domain/System (Windows) or Host Name (UNIX). Windows must be in the form of Domain/System or FQDN, UNIX can be Host Name, IP address, or FQDN.
  4. Column B Row 2 (and greater), must be blank (if column A for the row is blank), or it can contain a value for the specific system listed in column A.

Samples

Example CSV 1Example CSV 2

Notes:

  • All errors are logged to the Auditor log.
  • Only Windows systems can be imported when the Windows tab is active on the "External Data Integration" screen. Only UNIX system can be imported when the "UNIX" tab is active. A CSV file cannot contain a mix of both Windows and UNIX systems.
  • The CSV file will be validated before an attempt is made to import the file. The following cases would cause the generation of an error message and the file would not be imported.
    • If any system name in column A does not exist in the database (possibly misspelled, etc), the name of the system is shown in the Auditor log. Exception is that a "blank" name can exist and be treated as importing custom attributes only and not applying to any system.
    • If the number of "new" custom attributes added would cause the total number of attributes to exceed 100.
    • Duplicate system names exist in the same CSV file.
  • Each name entered in Column B (and greater), Row 1, is validated against the list of current custom attributes. If the name does not exist, it is added to the bottom of the custom attributes list. If it does exist, and values in this column is added to the system listed in column A.
    • If Overwrite is specified, any values for the custom attributes in the CSV file, even blanks, are written to the system records. This means that if a current value exists for a system and a "blank" is imported from the CSV file (with Overwrite selected), the value will be deleted. If Overwrite is NOT specified, "blanks" are not imported from the CSV files.