Salesforce

How to enable auditing for an OpenEdge database ?

« Go Back

Information

 
TitleHow to enable auditing for an OpenEdge database ?
URL NameP123845
Article Number000165744
EnvironmentProduct: OpenEdge
Version: 10.1x, 10.2x, 11.x, 12.x
OS: All supported platforms
Question/Problem Description
How to enable auditing for a Progress 10.1x database ?
Checklist to enable OpenEdge Auditing since Progress 10.1A
Steps required to enable OpenEdge Auditing on a database
Quick Guide for enabling an OpenEdge database for auditing
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

Starting with OpenEdge 10.1A , the database has support for Auditing provided with core database features.
If the database is enabled for OpenEdge Replication, this feature needs to be disabled prior to enabling Auditing.  Refer to the following Article:

Steps to enable OpenEdge Auditing

1)  Create a Structure File (.st)

Auditing requires specific database areas added to the structure where the Audited data will reside:

  • The Area must be a Type II Area.
  • Audit index data can be stored in a second area, and it's generally recommended to do so.
  • When adding the new audit areas, like when adding any new area to a database - consider that when enabled for After-imaging, each AI extent will uses an area number. The new audit extents added need to be configured with higher area numbers than the last AI extent.

Example text structure file: add_audit.st :

d "AuditData":20,64;512 . f 2000000
d "AuditData":20,64;512 .
#
d "AuditIndex":21,1;64 . f 1000000
d "AuditIndex":21,1;64 .


2)  Add the Audit areas

$  prostrct add <dbname> <.st file created on step 1>
 

3)  Enable the Auditing Feature

When Auditing is enabled, the name(s) of the audit areas need to be provided:

  • The area where audit data are stored is specified with the "area" parameter,
  • The area where audit index area are stored is specified with the  indexarea parameter, which can be the same area as the audit data are stored if required.

$   proutil <dbname> -C enableauditing area "AuditData" indexarea "AuditIndex"


If the operation is successful, you will see the message: Auditing has been enabled for database dbname. (12479)
This can be confirmed by running a report on database enabled features with: proutil <dbname> -C describe

 
4) Load Audit Policies

Copy to the working directory the default policies file (policies.xml) found in the auditing folder in the OpenEdge installation directory
 
Load the policies.xml file from the Data Administration tool

Example:
[ prowin | pro ] <dbname> -p _admin.p 
 
   a.- Load Data and Definitions 
   b.- Audit Policies
   c.- Load XML (.xml file)
   d.- Select files and select policies.xml 
   e.- Select OK 

 
To modify the default policies use the Audit Policy Maintenance tool  (available only OpenEdge installations on Windows). For further information refer to Article: What is the best way to move audit policies from one database to another?   
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:27 AM

Powered by