Oracle9i Application Server Oracle9iAS SOAP Developer's Guide Release 1 (v1.0.2.2) Part Number A90297-01 |
|
The Oracle SOAP audit logging feature monitors and records SOAP usage. Audit logging maintains records for postmortem analysis and accountability. SOAP The SOAP audit logging feature complements the audit logging capabilities available with the transport-specific server, the Apache HTTP listener, which hosts the SOAP Request Handler Servlet (SOAP server).
Oracle SOAP stores audit trails as XML documents. Using XML documents, Oracle SOAP creates portable audit trails and enables the transformation of audit trails or individual audit records to different formats.
By default, Oracle SOAP audit logging uses an audit logger class that implements the Handler
interface (part of the oracle.soap.server
package). The audit logger class is invoked conditionally to monitor events including service requests, service responses, and errors.
This chapter covers the following topics:
Table 4-1 lists the audit logging elements available for each audit log record. Individual audit log records may not contain all these elements. In the log file, each audit log record is stored as a SoapAuditRecord
element.
The XML schema for the generated audit log is provided in the file SoapAuditTrail.xsd
in the directory $SOAP_HOME/schema
on UNIX or %SOAP_HOME%\schema
on Windows NT. Refer to the schema file for complete details on the format of a generated audit record.
The audit logger class is invoked when an auditable event occurs and the SOAP Request Handler Servlet is configured to enable auditing for the event. Auditable events include a service request or a service response.
An audit logging filter can be added to the SOAP configuration file to specify the set of auditable events that are recorded to the audit log. The SOAP server applies event filters to request and response events. Table 4-2 shows the filter attributes that a filter selects for an audit logger event filter specification. When applied, filters limit the number of records generated in the audit log. For example, when a filter is specified for a particular host, only the auditable events that are generated for the specified host are saved to the audit log.
The filter syntax for defining auditable events is derived from RFC 2254. Table 4-3 shows the filter syntax, and Example 4-1 provides several examples.
(ip=138.2.142.154) (!(host=localhost)) (!(host=*.acme.com)) (&(host=*.acme.com)(username=daffy)) (&(ip=138.2.142.*)(|(urn=urn:www-oracle-com:AddressBook)(username=daffy)))
Configure the default SOAP Audit Logger supplied with Oracle SOAP by setting parameters in the SOAP configuration file, soapConfig.xml
. To enable the default audit logger and turn on audit logging, do the following in the configuration file.
oracle.soap.handlers.audit.AuditLogger
. The default audit logger supports several options that you specify in the configuration file. Table 4-4 shows the available audit logger options.
requestHandler
, responseHandler
, or errorHandler
chain (or to all of the handler chains).
Example 4-2 shows a sample segment from a SOAP configuration file including the audit logging configuration options. Example 4-2 shows configuration options set to use all options. However, this configuration would produce an extremely large audit log, and is not recommended.
<osc:handlers> <osc:handler name="auditor" class="oracle.soap.handlers.audit.AuditLogger"> <osc:option name="auditLogDirectory" value="/private1/oracle/app/product/tv02/soap/webapps/soap/WEB-INF"/> <osc:option name="filter" value="(!(host=localhost))"/> <osc:option name="includeRequest" value="true"/> <osc:option name="includeResponse" value="true"/> </osc:handler> </osc:handlers> <osc:requestHandlers names="auditor"/> <osc:responseHandlers names="auditor"/> <osc:errorHandlers names="auditor"/>
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|