By Juergenkress-Oracle on Jan 06, 2014
I have heard from a couple of customers recently asking about BPM audit table growth, specifically BPM_AUDIT_QUERY. It led me to investigate the impact of the various audit levels in SOA/BPM on these table and to propose options to them.
It is important to note up-front that BPM is a human-centric workflow application and therefore should be expected to audit often and in detail the reality is that business users probably will want to know who did what and when, and also who did not do what when they were supposed to. BPM auditing is very rich and can provide this kind of information and more. The “downside” of this is that audit tables can grow at a faster rate than expected, and BPM_AUDIT_QUERY is normally the most prominent of these.
Clearly there are well documented strategies for archiving/purging and partitioning which can control/limit the impact of table growth but there may also be simple changes to the BPM audit settings which can prove beneficial in certain business situations.
There are essentially three places where the auditing of BPM applications can be controlled Read the full article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.