Does Oracle Access Manager Use Audit Configuration Maximum Directory Size
(Doc ID 2636358.1)
Last updated on FEBRUARY 06, 2020
Applies to:Oracle Access Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
- Upgraded from OAM 11g to OAM 12c
- Audit logs are not rotating as they did in OAM 11
- Confirmed that the Audit settings in the OAM console and the jps-config.xml from both a working 11g and 12c environment are the same
- Following Middleware, Identity Management (IdM), Access ManagerRelease 188.8.131.52, Administering Oracle Access Management,Chapter 8 Auditing Administrative and Run-time Events, 8.5 Setting Up Auditing for Oracle Access Management, 8.5.3 Using the Oracle Access Management Console for Audit Configuration
- OAM 12c Audit Configuration Maximum Directory Size navigation path:
- Configuration => Settings => View => Common Settings => Audit Configuration ... Maximum Directory Size (MB)
The maximum size, in MBs, of the directory that contains audit output files. For example, assuming that the maximum file size is 10, a value of 100 for this parameter implies that the directory allows a maximum of 10 files. Once the maximum directory size is reached, the audit logging stops.
For example, a value of 100 specifies a maximum of 10 files if the file size is 10 MB. If the size exceeds this, the creation of audit logs stops.
This is configured using the max.DirSize property described in the configuration filejps-config.xml. This property controls the maximum size of a bus-stop directory for Java components as described in the Securing Applications with Oracle Platform Security Services.
Does Oracle Access Manager use Audit configuration "Maximum Directory Size"?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document