The Audit Administrator privilege is required to export Audit Policies from an audit enabled database and load the policy.
When the Audit Policy is dumped, the file cannot be modified before it is imported because the seal validation will fail. The purpose of audit policy export/import is in order to not have to manually create policies for every application audited database, not to modify existing policies as xml or .ad files.
Once Policies have been created to audit database and application events, these can be exported then imported to another database which is enabled for Auditing.
A. Audit Policy Maintenance Tool menu (Data Dictionary)
The Audit Policy Maintenance Tool (apmt) is available on the Tools menu of any ADE tool which uses the API. Apart from configuring, updating, deleting policies and custom events it can also be used to export and import policies. APMT is only available on Windows and can be used to connect to remote audit enabled databases on Windows or Linux.
To Export existing policies to a xml file with the APMT:
- Connect to the current audit enabled database
- Select the Policy or Policies to be exported
- File/Export Policy ...
- Supply path/file-name
- Click OK to export Policies which will create an .xml file.
To Import Audit Policies with the APMT:
An Audit policy .xml file can be imported to another database once Auditing is enabled
- Connect to the new audit enabled database
- File/Import Policy ...
- Browse to path and select the policy .xml file-name
- Click OK to import the Policies from the .xml file
- File/Commit Changes
B. Data Administration
Audit Policies can be dumped as either an .xml file or ASCII text .ad files and loaded using the standard Data Administration Load methodology
- _aud-audit-policy.ad;
- _aud-field-policy.ad;
- _aud-event-policy.ad;
- _aud-file-policy.ad
To Dump existing Policies:
- Connect to the current audit enabled database
- Admin/Dump Data and Definitions > Audit Policies/Dump as Text (.ad file) or Dump as XML file (.xml file)
- Select the Policy or Policies to be exported.
- Supply path for .ad export or path and filename for .xml export
- Click OK to create the Audit Policy export
To Load Audit Policies:
The resulting .xml or .ad files can be imported once Auditing is enabled
- Connect to the new audit enabled database
- Admin > Load Data and Definitions > Audit Policies > Load as Text (.ad file) or Load as XML file (.xml file)
- Supply path for .ad export or path and filename for .xml export
- Click OK to import the Audit Policies.
Audit Events
Events created for application specific auditing are typically created using the Audit Policy Maintenance Tool. Event ID's of 32000 or greater are available for Application Events, anything lower than 32000 is reserved for internal events.
As outlined above:
- The Events Maintenance Tool (in APMT) can be used to export then import events (.evt)
- The Data Administration UI can be used to dump and load events:
Admin > Dump > Audit > Audit Events
C. Deploy Audit Policy and Events with scripting
Once required Audit Policies and application specific events have been designed to meet the requirements of the Audit Authority, these can be deployed to customer sites with ABL code provided in the prodict library. The following Article provides examples:
