R
Rob Fitzpatrick
Guest
You didn't mention your Progress version. One way to achieve what you describe (on OE 10.1A+) is with OpenEdge Auditing. There is a bit of a learning curve, and you will want to read through the docs before trying to implement. In other words, as with many things, there are some worst practices to be avoided. OE Auditing does work with both 4GL and SQL clients, and can be extended to include your own application-specific policies, events, and context. You should do your own testing of course, but my guess is that this approach would be more efficient than rolling your own auditing code. It will also be more reliable (given that a lot more people have hammered on PSC's code than on yours) and more secure than using ordinary application tables for storage (given that there are built-in protections in the platform for access to data in the audit tables). Have a look at it. Relevant docs: Database Administration | Protecting Your Data | Auditing Core Business Services | Auditing Also helpful: Mike Furgal and John Harlow (BravePoint) on OE Auditing, from PUG Challenge Americas 2013: slides audio Jean-Pierre Mathieu (Lumec), real-world audit case study, from Progress Exchange 2009: slides (.zip)
Continue reading...
Continue reading...