Setting Up Auditing
To set up auditing, you must load the license for Enhanced Controls and then do the tasks described in the following sections:
Note: When setting up auditing, QAD recommends that you first set up a test environment to test the auditing policy and then export the policy and load it into the production database.
Enabling Auditing for the Database
Before setting up auditing, do the following:
• Be sure that the database has been upgraded to Progress OpenEdge 10.1B03 or above.
• Back up the database.
To use auditing in Progress OpenEdge, you must add type II storage areas for the audit data and audit indexes to ensure optimal performance. The audit data and indexes can be in the same storage area, but QAD recommends that they be in separate areas. The descriptions in this document assume that you are using separate areas.
To add type II storage areas, use the prostrct add statement:
prostrct add <db> addaudit.st
Where addaudit.st contains the following information:
d "Audit_Data";64 . f 40960
d "Audit_Data";64 .
d "Audit_Index";64 . f 5120
d "Audit_Index";64 .
The above sample structure file uses a combination of fixed and variable length extents for maximum speed with a safety valve. You should set the limits to try to avoid hitting the variable length extent. The values used should be modified as appropriate for your system, but those shown represent a reasonable starting point. The sample code includes an example adduadit.st file.
Note: The appropriate values for addaudit.st to use depend on many factors, including the size of your data, how much you expect to audit, the frequency of updates and throughput, and physical configuration.
Once you have added the type II storage areas to your databases, you can then enable auditing for each one as follows:
proutil <db-name> -C enableauditing area "Audit_Data" indexarea "Audit_Index"
Note: Databases can be individually audit-enabled. You are not required to enable all databases in a database set.