Kbase P123845: How to enable auditing for a Progress 10.1x database ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/10/2008 |
|
Status: Verified
GOAL:
How to enable auditing for a Progress 10.1x database ?
GOAL:
Checklist to enable Auditing in Progress 10.x
GOAL:
How to enable auditing in OpenEdge 10.1A or Later
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
FIX:
Starting with OpenEdge 10.1A , the database has support for Auditing within the core features of the database, to enable auditing follow the next steps :
1) Create an Structure File (st)
The st file for a database that will use Auditing needs to define an specific area where the Auditing data will reside, this has to be a Type II Area
Example of structure file :
d "AuditData Area":13,32;64 . f 1000000
d "AuditData Area":13,32;64 . f 1000000
d "AuditData Area":13,32;64 .
#
d "AuditIndex Area":14,32;64 . f 1000000
d "AuditIndex Area":14,32;64 . f 1000000
d "AuditIndex Area":14,32;64 .
2) Run protruct add to add the Audit areas to your database.
prostrct add <dbname> <.st file created on setp 1>
3) Enable the Auditing
When you enable the Auditing you are required to specify the Auditing area with the "area" parameter, it is not recommended to use the Schema Area, when enabling Auditing you could use a command like :
proutil dbname -C enableauditing area "AuditData Area" indexarea "AuditIndex Area"
If everything works just fine , you will see a message like :
Auditing has been enabled for database dbname. (12479)
Once the Auditing has been enabled for the database you can use the Audit Policy Maintenance Tool via the icon in the progress program group to import the base policy file ( policies.xml) from the DLC\auditing directory and commit it via the Commit Changes, both found under the menu heading "file". At this point you are ready to define your specific audit policies via the same tool.