Release 10.1A: OpenEdge Development:
Basic Database Tools

> ## Audit Policies

> The Audit Policies submenu allows you to load audit data as `XML` or text or load application audit event data.

> ##### Load as XML

> When you choose the Load as XML (.xml file) option from the Load Audit Policies submenu, the Load Audit Policies XML dialog box appears, containing the following fields:

> - Input File — The name of the file that contains the data you want to load into your current working database. The default file is `_audit-policies.xml`.

> - Overwrite Duplicate Policies — Select if you want the Data Dictionary to overwrite existing policies with the loaded data. If you do not select this option and the Data Dictionary detects duplicate policies, it will display a list of the duplicates and ask you if you want to overwrite them. If the load is running in Batch Mode, the Data Dictionary creates an error file that lists the duplicate policies.

> Note: The connected user must have Audit Administrator permissions in order to access the Load Audit Policies XML option.

> If the Data Dictionary encounters errors when validating the file or directory name or when verifying that the database is connected, it creates an error file called `_lodsec.e` and places it in the intended load directory. If the load directory doesn’t exist, the Data Dictionary places `_lodsec.e` in the session’s current working directory.

> If the Data Dictionary encounters errors during the load process, it creates an error file named `audit-policies-xml``.e.`

> ##### Load as Text

> When you choose the Load as Text (.ad file) option from the Load Audit Policies submenu, the Load Audit Policies Text dialog box appears, prompting you to enter the name of an Input Directory. The Input Directory is the directory where the `.ad` files are stored.

> Note: The connected user must have Audit Administrator permissions in order to access the Load Audit Policies Text option. If a user without Audit Archiver permissions selects this option, the Data Dictionary creates the `_aud-audit-policy.e` file in the intended load directory.

> If the Data Dictionary encounters errors when validating the file or directory name or when verifying that the database is connected, it creates an error file called `_lodsec.e` and places it in the intended load directory. If the load directory doesn’t exist, the Data Dictionary places `_lodsec.e` in the session’s current working directory.

> If the Data Dictionary encounters errors during the load process, it creates an error file in the intended load directory. The Data Directory names the error file for the table it encountered the error on and gives it a `.e` extension.

> ##### Application Audit Events

> Choose the Application Audit Events option from the Load Audit Policies submenu to load data into the `_aud-event` table. The `_aud-event` table defines supported audit events for the database.

> The Load Application Audit Events dialog box prompts you for an Input File. The default is `_aud-event.ad`.

> Note: The user must have Audit Administrator privileges to access the Load Application Audit Events option. For information about granting Audit permissions, see the "Edit Audit Permissions" section.

> If the Data Dictionary encounters errors during the load process, it creates an error file named for the table with a `.e` extension.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095