Enterprise Security includes an auditing feature that allows you to monitor user actions.
You can configure auditing to:
Send notifications of audited events to a JMS message topic.
Direct the audit output to a file, a JDBC-compliant database, or a custom application.
Use a database connection cache to improve performance and scalability by allowing client connections to share open connections. For information about EAServer connection caches, see “Using Connection Management,” in the EAServer Programmer’s Guide. For information about using a WebLogic connection cache, see your BEA documentation.
Refuse authorization and authentication requests if errors occur when an audit message is logged, such as when the file system is full.
Disable auditing in the case of an auditing system failure, allowing users to continue to log in to the system and perform operations normally while auditing is suspended.
To audit user actions within a specific domain, enable auditing for the domain, and specify which actions to audit. To write audit information to a database, set up the audit database, and enable the connection cache database Service Provider Interface (SPI). When an audited event occurs, the default SPI implementation generates an XML-formatted string, stamps the output with a Greenwich Mean Time (GMT) timestamp, and writes it to an audit log. If you write a custom SPI, neither the XML string nor the timestamp are required.
