Fusion Middleware Documentation
Advanced Search


Administering Web Services
Close Window

Table of Contents

Show All | Collapse

6 Monitoring and Auditing Web Services

This chapter describes how to monitor the performance of a Web service using Fusion Middleware Control.

The chapter includes the following sections:

6.1 Overview of Performance Monitoring, Auditing, and Tuning

Note:

Only a subset of the monitoring features described in this chapter apply to Java EE Web services.

From the Web Services home page in Fusion Middleware Control, you can do the following:

  • Monitor Web services faults, including Security, Reliable Messaging, MTOM, Management, and Service faults.

  • Monitor Security failures, including authentication, authorization, message integrity, and message confidentiality failures.

  • Configure your Web services ports, including enabling and disabling the port, attaching policies to Web services, and enabling or disabling policies.

The Application home page also displays select Web service details if the application includes Web services.

6.2 Monitoring Web Services

This section contains the following sections:

In addition to the monitoring features described in this chapter, see "Analyzing Policy Usage" in Securing Web Services and Managing Policies with Oracle Web Services Manager to analyze how policies are used by one or more Web services.

6.2.1 When Are Web Service Statistics Started or Reset?

The statistics described in this chapter are started or reset when any one of the following events occur:

  • When the application is being deployed for the first time.

  • When the application is redeployed.

  • If the application is already deployed, and the hosting server is restarted.

6.2.2 Viewing Web Service Statistics for a Server Instance

The server-side Web services page displays statistics for all of the Web services on that server.

To view the Web service statistics for a server

  1. In the navigation pane, expand WebLogic Domain to show the domain for which you want to see the policies and select the domain.

  2. Expand the domain to show the servers in that domain. Select the server for which you want to view the statistics.

  3. Using Fusion Middleware Control, click WebLogic Server, and then Web Services.

  4. The Web services statistics page for the server is displayed, as shown in Figure 6-1.

    Depending on the types of Web services you have deployed, tabs are available for the following Web service types: Java EE, Oracle Infrastructure Web Services and RESTful Services.

    Figure 6-1 Web Services for a Server

    Description of Figure 6-1 follows
    Description of "Figure 6-1 Web Services for a Server"

6.2.3 Viewing Web Service Statistics for an Application

In Fusion Middleware Control, the Web Services summary page for an application displays the collective Summary and fault/violation information for all Web services in the application, as shown in Figure 6-2.

The Charts section shows a graphical view of all security faults for a Web service.

To navigate to the Web Service Summary page for a Web service

  1. In the navigation pane, expand the Application Deployments folder to expose the applications in the domain, and select the application.

    The Application Deployment home page is displayed.

  2. Using Fusion Middleware Control, click Application Deployment, then click Web Services.

    The Web Services Summary page for this application is displayed.

    The page displays Web service endpoints as well as application-level metrics.

For Oracle Infrastructure Web services, the following Web service-wide statistics are displayed:

  • Web Services (Number of Web services in the application)

  • Web Service Endpoints

  • Web Service Endpoints Disabled

  • Total Policy Violations

  • Total Faults

  • Invocations Completed

Figure 6-2 Web Services Performance Summary and Charts

Description of Figure 6-2 follows
Description of "Figure 6-2 Web Services Performance Summary and Charts"

For Java EE Web services, including SOAP and RESTful Web services, the following Web service-wide statistics are displayed:

  • Server Name (server on which the application is running)

  • Web Services (number of Web services in the application)

  • Web Service Endpoints

  • Number of RESTful Applications

  • Number of RESTful Resources

  • Java EE Web Service Clients (number of run-time client instances in the application)

  • Java EE Web Service Client Ports (number of Web service client ports in the application to which you can attach OWSM policies)

    Figure 6-3 Java EE Web Services Summary

    Description of Figure 6-3 follows
    Description of "Figure 6-3 Java EE Web Services Summary"

6.2.4 Viewing Web Service Statistics for an Individual Web Service

The Web Service Details section of the Web Services Summary page displays statistics on a per-Web service basis, as shown in Figure 6-6. For information about navigating to the Web Services Summary page, see "Viewing Web Service Statistics for an Application".

The following statistics are displayed for Java EE Web Services:

  • Name—Name of the Web service. Expand the Web service to display the Web service endpoint.

  • Invocation Count—Number of invocation requests to this endpoint.

  • Response Error Count—Number of errors encountered during responses.

  • Response Count—Number of responses

  • Average Execution Time (ms)—Average time, in milliseconds, to execute the Web service.

  • Average Response Time (ms)—Average time, in milliseconds, to receive a response from the Web service.

Figure 6-4 Web Service Statistics for Individual Java EE Web Services

Description of Figure 6-4 follows
Description of "Figure 6-4 Web Service Statistics for Individual Java EE Web Services"

The following statistics are displayed for RESTful Web Services:

  • Module Name and RESTful Application Name—Name of the containing application module and the RESTful application.

  • Resource Name—Name of the RESTful resource.

  • Resource Type—Type of the RESTful resource.

  • Resource Path—URI of the RESTful resource.

  • Invocation Count—Number of invocation requests to this endpoint.

  • Average Execution Time (ms)—Average time, in milliseconds, to execute Web services.

Figure 6-5 Web Service Statistics for Individual RESTful Web Services

Description of Figure 6-5 follows
Description of "Figure 6-5 Web Service Statistics for Individual RESTful Web Services"

The following statistics are displayed for Oracle Infrastructure Web Services:

  • Name—Name of the Web service. Expand the Web service to display the Web service endpoint.

  • Endpoint Enabled—Flag that specifies whether the Web service is enabled or disabled. For Oracle Infrastructure Web service providers, this field displays n/a.

  • Start Time—Time the Web service was started.

  • Invocations Completed—Number of completed requests to this endpoint.

  • Average Invocation Time—Average time for all Web service invocations to be processed.

  • Policy Faults—Number of failed requests because a policy was not successfully executed.

  • Total Faults—Total number of failed requests.

Figure 6-6 Web Service Statistics for Individual Oracle Infrastructure Web Services

Description of Figure 6-6 follows
Description of "Figure 6-6 Web Service Statistics for Individual Oracle Infrastructure Web Services"

6.2.5 Viewing Operation Statistics for a Web Service Endpoint

Follow this procedure to view statistics for a Web service endpoint. To view statistics for individual operations, see "Viewing Statistics for a Java EE Web Service Operation".

To display operation statistics for a particular Web service endpoint:

  1. Navigate to the Web Service Summary page as described in "Viewing the Web Services Summary Page for an Application".

  2. In the Web Services Details section of the Web Services summary page, select the Web Service Endpoints tab.

  3. Select the endpoint for which you want to display the statistics.

    The Web Service Endpoint page is displayed.

  4. Select the Operations tab if it is not already selected.

    The following statistics are presented for Oracle Infrastructure Web services:

    Element Description

    Operation Name

    Name of the operation.

    One Way

    Flag that specifies whether the operation returns a value to the calling operation.

    Action

    URI of the action.

    Input Encoding

    Encoding style of the input message.

    Output Encoding

    Encoding style of the output message.

    Invocations Completed

    Number of completed requests to this endpoint.

    Average Invocation Time

    Average time for all Web service invocations to be processed.

    Faults

    Total number of faults for this endpoint.


    The following statistics are presented for Java EE Web services:

    Element Description

    Name

    Name of the operation.

    Invocation Count

    Number of times that the Web service was invoked.

    Average Dispatch Time (ms)

    Average time, in milliseconds, for all Web service invocations to be processed.

    Average Execution Time (ms)

    Average time, in milliseconds, for all Web service executions.

    Average Response Time (ms)

    Average time, in milliseconds, for all responses generated.

    Response Count

    Total number of responses generated from the Web service invocations.

    Response Error Count

    Total number of errors from responses generated from the Web service invocations.


6.2.6 Viewing Statistics for a Java EE Web Service Operation

The individual Web service operations are displayed on the Operations tab of the Web Service Endpoint page. This procedure applies only to Java EE Web service operations.

To view the statistics for an individual Web service operation:

  1. Navigate to the Web Service Operation page: see "Viewing the Details for a Java EE Web Service Operation".

  2. Click the name of an operation to view its statistics.

The Web Service Operation page displays the following statistics:

Element Description

Application Name

The name of the application that this operation is associated with.

Web Service Name

The name of the Web service that this operation is associated with.

Endpoint Name

The name of the endpoint that this operation is associated with.

Operation Name

The name of the Web service operation.

Endpoint URI

The URI of the endpoint that this operation is associated with.


Errors

The Errors section of the Web Service Operation page displays the following error statistics:

Element Description

Error Count

Number of errors sending or receiving a request.

Last Error

Last error that occurred processing a request.

Last Error Time

Time on WebLogic Server of the last error for a request (sending or receiving) was detected expressed as the number of milliseconds since midnight, January 1, 1970 UTC.

Response Error Count

Total number of errors from responses generated from operation invocations.

Last Response Error

Last response error to arrive for this client/service (or null if no errors have occurred).

Last Response Error Time

Time on WebLogic Server of the last error sending or receiving a response (or 0 if no failures have occurred) expressed as the number of milliseconds since midnight, January 1, 1970 UTC.


Invocation Statistics

The Invocation Statistics section of the Web Service Operation page displays the following invocation statistics:

Element Description

Invocation Count

Total number of operation invocations in the current measurement period.

Last Invocation Time

Time of the last operation request to be sent or received (or 0 if no requests have been sent or received).

Average Dispatch Time (ms)

Average operation dispatch time (in milliseconds) for the current measurement period. Dispatch time refers to the time for WebLogic Server to process the invocation. The measurement period typically starts when WebLogic Server is first started.

Dispatch Time Total (ms)

Total time (in milliseconds) for all operation dispatches in the current measurement period. Dispatch time refers to the time for WebLogic Server to process the invocation. The measurement period typically starts when WebLogic Server is first started.

Dispatch Time High

Longest operation dispatch time for the current measurement period. Dispatch time refers to the time for WebLogic Server to process the invocation. The measurement period typically starts when WebLogic Server is first started.

Dispatch Time Low

Shortest operation dispatch time for the current measurement period. Dispatch time refers to the time for WebLogic Server to process the invocation. The measurement period typically starts when WebLogic Server is first started.

Average Execution Time (ms)

Average operation execution time (in milliseconds).

Execution Time Total (ms)

Total time (in milliseconds) for all operation executions.

Execution Time High

Longest operation execution time.

Execution Time Low

Shortest operation execution time.


Response Statistics

The Response Statistics section of the Web Service Operation page displays the following response statistics:

Elements Description

Response Count

Total number of responses generated from operation invocations.

Last Response Time

Time on WebLogic Server of the last response to arrive for this client/service (or 0 if no responses have been received) expressed as the number of milliseconds since midnight, January 1, 1970 UTC.

Average Response Time (ms)

Average response time (in milliseconds) from the responses generated from operation invocations.

Response Time Total (ms)

Total time (in milliseconds) for all responses generated from operation invocations.

Response Time High

Longest response time from the responses generated from operation invocations.

Response Time Low

Lowest response time from the responses generated from operation invocations.


6.2.7 Viewing Statistics for Java EE Web Service Clients

To display Web Service statistics for the run-time client instances in a Java EE application:

  1. Navigate to the home page for the Java EE Web service, as described in "Viewing the Web Services Summary Page for an Application".

  2. Select the Java EE Web Service Clients tab to view the clients in the application.

    Note:

    This tab is available only if the application contains Java EE Web service clients.

  3. Select the Monitoring tab, if it is not already selected to view the statistics for all run-time client instances in the application.

    Note:

    For JAX-WS Web services, the Web services run time creates system-defined client instances within a Web service endpoint that are used to send protocol-specific messages as required by that endpoint. These client instances are named after the Web service endpoint that they serve with the following suffix: -SystemClient. Monitoring information relevant to the system-defined client instances is provided to assist in evaluating the application.

  4. Select the client in the Client column to display Web service statistics for that client.

    The Java EE Web Service Client page is displayed, as shown in Figure 6-7.

    Figure 6-7 Java EE Web Service Client Statistics

    Description of Figure 6-7 follows
    Description of "Figure 6-7 Java EE Web Service Client Statistics"

    The following summary information is presented for the run-time client instance.

    • Application Name—The name of the application with which the client is associated.

    • Module Name—Name of the Java EE module in which the endpoint is running.

    • Web Service Endpoint—Name of the port which the client invokes.

    • Transport Protocol Type—Transport protocol required by the service.

  5. Select the Invocations tab to view the invocation statistics for the client.

    Table 6-1 lists the invocation statistics displayed for the run-time client instance.

    Table 6-1 Invocation Statistics for Java EE Web Service Client

    Element Description

    Errors

     

    Error Count

    Total number of security faults and violations.

    Response Error Count

    Total number of errors from responses generated from invocations of this client instance

    Invocation Statistics

     

    Invocation Count

    Total number of times that operations on service side have been invoked by the client instance in the current measurement period.

    Average Dispatch Time (ms)

    Average dispatch time for the current measurement period.

    Dispatch Time Total (ms)

    Total time for all dispatches of this operation in the current measurement period.

    Average Execution Time (ms)

    Average execution time of this operation.

    Execution Time Total (ms)

    Total time for all executions of this operation

    Response Statistics

     

    Response Count

    Total number of responses generated from invocations of this operation.

    Average Response Time (ms)

    Average response time from the responses generated from invocations of this operation.

    Response Time Total (ms)

    Total time for all responses generated from invocations of this operation.


  6. Select the WebLogic Policy Violations tab to the statistics for policy violations of this client run-time instance.

    Note:

    This tab appears only if there are WebLogic Web service policies attached to the Java EE Web service client.

    Table 6-2 lists the policy violations for the client run-time instance.

    Table 6-2 WebLogic Policy Violations for Java EE Web Service Client

    Element Description

    Summary

     

    Total Faults

    Total number of failed requests.

    Policy Faults

    Total number of policy faults.

    Total Security Faults

    Total number of security faults and violations.

    Violations

     

    Authentication Violations

    Total number of authentication violations generated for this port. Only incoming message processing can add to the violation count.

    Confidentiality Violations

    Total number of confidentiality violations generated for this port. Both outgoing and incoming message processing can add to the violation count.

    Integrity Violations

    Total number of integrity violations generated for this port. Both outgoing and incoming message processing can add to the violation count.

    Successes

     

    Authentication Successes

    Total number of authentication successes detected for this port. Only incoming message processing can add to the success count.

    Confidentiality Successes

    Total number of confidentiality successes generated for this port. Both outgoing and incoming message processing can add to the success count.

    Integrity Successes

    Total number of integrity successes generated for this port. Both outgoing and incoming message processing can add to the success count.


6.2.8 Viewing Statistics for RESTful Resources

To display Web Service statistics for the resources in a RESTful Web service:

  1. Navigate to the Web Services Summary page for the application, as described in "Viewing the Web Services Summary Page for an Application".

  2. Select the RESTful Services tab to view the RESTful applications.

    Note:

    This tab is available only if the application contains RESTful Web services.

  3. Click the RESTful application for which you want to view RESTful resources.

  4. In the RESTful Resources tab, click the resource for which you want to view statistics.

    Table 6-3 lists the summary information that is provided.

    Table 6-3 Summary of RESTful Resource

    Field Description

    Application Name

    The name of the application with which the RESTful service is associated.

    Module Name

    Name of the module in which the RESTful application is running.

    RESTful Application Name

    Name of the RESTful application.

    Resource Name

    URI of the RESTful resource.

    Resource Type

    Type of the resource.

    Resource Path

    Path of the resource.

    Number of Methods

    Number of methods.

    Number of Subresource locators

    Number of subresource locators.

    Invocation Count

    Number of invocations of the RESTful service.

    Average Execution Time (ms)

    Average execution time, in milliseconds, of this method.


  5. In the RESTful Methods tab, view the statistics for the methods.

    Table 6-4 lists the statistics for each RESTful method.

    Table 6-4 Statistics for RESTful Resources

    Field Description

    Method Name

    Name of the method.

    Return Type

    Return type of the method.

    Path

    Path of the method.

    HTTP Method

    HTTP method to which the method is mapped.

    Producing Media Type

    Total time for all dispatches of this operation in the current measurement period.

    Invocation Count

    Number of invocations of the RESTful method.

    Average Execution Time (ms)

    Average execution time, in milliseconds, of this operation.

    Execution Time Total (ms)

    Total time for all executions of the method.


6.2.9 Viewing the Security Violations for a Web Service

Follow the procedure below to view security violations for a Web service.

To view the security violations for an Oracle Infrastructure Web service:

  1. Navigate to the Web Services Summary page as described in "Viewing the Web Services Summary Page for an Application".

  2. In the Charts section of the page, select the Security Violations tab.

    A graphical representation of the authentication, authorization, confidentiality, and integrity faults for all Web services in the application is displayed in the pie chart.

  3. In the Web Service Details section of the page, expand the Web service to display the Web service endpoints if they are not already displayed.

  4. Click the name of the endpoint to navigate to the Web Service Endpoint page.

  5. Click the Charts tab to see a graphical representation of all faults and all security violations for the endpoint.

  6. Click the OWSM Policies tab.

    Two tables are displayed.

    The Globally Attached Policies table displays the name of the policy and the policy set that references it.

    The Directly Attached Policies table displays the name of the policy and the policy status (whether the policy is enabled or disabled).

    Both tables list the category to which the policy belongs (security, MTOM attachments, reliable messaging, WS-addressing, and management).

    Table 6-5 lists the violation information provided for each type of policy attachment.

    Table 6-5 Policy Violation Information for an Endpoint

    Violation Type Description

    Total Violations

    Total number of faults for this policy.

    Note: Total violations may not be equal to the sum of the security violations shown below (for example, Authentication, Authorization, Confidentiality, and Integrity). Other security violations that do not fall into these major categories and non-security violations are also captured in the total violations count.

    Security Violations

     

    Authentication

    Number of authentication failures since the server was restarted.

    Authorization

    Number of authorization failures since the server was restarted.

    Confidentiality

    Number of message confidentiality failures since the server was restarted.

    Integrity

    Number of message integrity failures since the server was restarted.


To view the security violations for a Java EE JAX-WS Web service:

  1. Navigate to the Web Services Summary page as described in "Viewing the Web Services Summary Page for an Application".

  2. In the Web Service Details section of the page, expand the Web service to display the Web service endpoints if they are not already displayed.

  3. Click the name of the endpoint to navigate to the Web Service Endpoint page.

  4. Do one of the following, depending on the type of policies attached to the endpoint:

    • If OWSM policies are attached to the endpoint, click the OWSM Policies tab.

      A list of the policies that are attached to the endpoint is displayed. For each policy, the table displays the name of the policy, the category of the policy (security, MTOM attachments, reliable messaging, WS-addressing, and management), and the policy status (whether the policy is enabled or disabled). Table 6-5 describes the violation information that is displayed for each OWSM policy attached to the endpoint.

    • If WebLogic policies are attached to the endpoint, click the WebLogic Policy Violations tab.

      This tab shows policy violation details about WebLogic policies attached to a JAX-WS endpoint. Table 6-6 describes the information provided on this page.

      Table 6-6 WebLogic Policy Violation Data

      Element Description

      Summary

       

      Total Faults

      Total number of failed requests.

      Policy Faults

      Number of failed requests because a policy was not successfully executed.

      Total Violations

      Total number of faults for this policy.

      Violations

       

      Authentication Violations

      Number of authentication failures since the server was restarted.

      Confidentiality Violations

      Number of message confidentiality failures since the server was restarted.

      Integrity Violations

      Number of message integrity failures since the server was restarted.

      Successes

       

      Authentication Successes

      Number of authentication successes since the server was restarted.

      Confidentiality Successes

      Number of message confidentiality successes since the server was restarted.

      Integrity Successes

      Number of message integrity successes since the server was restarted.


To view the security violations for a Java EE JAX-RPC Web service:

  1. Navigate to the Web Services Summary page for the application.

  2. In the Web Service Details section of the page, expand the Web service to display the Web service endpoints if they are not already displayed.

  3. Click the name of the endpoint to navigate to the Web Service Endpoint page.

  4. Click the WebLogic Policy Violations tab.

    This tab shows policy violation details about WebLogic policies attached to a JAX-RPC endpoint, as shown in Figure 6-8. For a description of the information displayed on this tab, see Table 6-6.

    Figure 6-8 Security Violations for a Java EE JAX-RPC Web Service Endpoint

    Description of Figure 6-8 follows
    Description of "Figure 6-8 Security Violations for a Java EE JAX-RPC Web Service Endpoint"

6.3 Auditing Web Services

Auditing describes the process of collecting and storing information about security events and the outcome of those events. An audit provides an electronic trail of selected system activity.

An audit policy defines the type and scope of events to be captured at run time. Although a very large array of system and user events can occur during an operation, the events that are actually audited depend on the audit policies in effect at run time. You can define component- or application-specific policies, or audit individual users.

You configure auditing for system components, including Web services, and applications at the domain level using the Audit Policy page. You can audit ADF services.

The following table summarizes the events that you can audit for Web services and the relevant component.

Table 6-7 Auditing Events for Web Services

Enable auditing for the following Web service events . . . Using this system component . . .
  • User authentication.

  • User authorization.

  • Policy enforcement, including message confidentiality, message integrity, and security policy.

Oracle Web Services Manager—Agent

For more information, see "OWSM-AGENT Events and their Attributes".

  • Web service requests sent and responses received.

  • SOAP faults incurred.

Note: In this case, events are logged for both security and non-security Web service invocations.

Oracle Web Services

For more information, see "Oracle Web Services Events and their Attributes".

  • OWSM assertion template creation, deletion, or modification.

  • OWSM policy intent creation, deletion, or modification.

  • OWSM policy creation, deletion, or modification.

  • OWSM policy set authoring creation, deletion, or modification.

Oracle Web Services Manager—Policy Manager

Note: The Policy Manager audits both local policy attachments and global policy attachments for policy sets.

For more information, see "OWSM-PM-EJB Events and their Attributes".

  • OWSM policy attachment.

Oracle Web Services Manager—Policy Attachment

Note: The Policy Attachment audits only local policy attachments.

For more information, see "Web Services Policy Attachment Events and their Attributes".


You can also audit the events for a specific user, for example, you can audit all events by an administrator.

For more information about configuring audit policies, see "Configuring and Managing Auditing" in Securing Applications with Oracle Platform Security Services.

The following sections describe how to define audit policies and view audit data:

6.3.1 Configuring Audit Policies

Follow the steps in this section to configure audit policies. For more information, see "Manage Audit Policies for Java Components with Fusion Middleware Control" in Securing Applications with Oracle Platform Security Services.

  1. In the navigation pane, expand WebLogic Domain.

  2. Select the domain for which you want to manage the audit policies.

  3. From the WebLogic Domain menu, select Security > Audit Policy.

    The Audit Policy Settings page is displayed.

    The audit policies table, at the center of the page, displays the audits that are currently in effect.

  4. Select the component that you want to audit from the Audit Component Name menu.

  5. Select an audit level from the Audit Level menu.

    Valid audit levels include:

    • None—Disables auditing.

    • Low—Audits a small scope of events. The subset of events is predefined individually for each component. For example, for a given component, Low may collect authentication and authorization events only.

    • Medium—Audits a medium scope of events (which is a superset of the events collected at the Low level). For example, for a given component, Medium may collect authentication, authorization, and policy authoring events.

    • Custom—Enables you to provide a custom auditing policy.

    You can view the components and applications that are selected for audit at each level in the audit policies list. For all audit levels other than Custom, the information in the audit policies list is greyed out, as you cannot customize other audit level settings.

  6. To customize the audit policy, select the Custom option and perform one of the following steps:

    • Select the information that you want to audit by clicking the associated checkbox in the Select for Audit column.

      You can audit at the following levels of granularity: All events for a component, all events within a component event category, an individual event, or a specific outcome of an individual event (such as, success or failure).

      Click Select All to select all categories, None to deselect all categories, or Audit All Events to audit all events, including specific outcome of individual events (such as, successes and failures).

      At the event outcome level, you can specify an edit filter. Filters are rules-based expressions that you can define to control the events that are returned. For example, you might specify an Initiator as a filter for policy management operations to track when policies were created, modified, or deleted by a specific user. To define a filter for an outcome level, click the Edit Filter icon in the appropriate column, specify the filter attributes, and click OK. The filter definition appears in the Filter column.

      Deselect the checkbox for a component at a higher level to customize auditing for its subcomponents. You can select all components and applications by checking the checkbox adjacent to the column name.

    • At the event outcome level, you can specify an edit filter. Filters are rules-based expressions that you can define to control the events that are returned. For example, you might specify an Initiator as a filter for policy management operations to track when policies were created, modified, or deleted by a specific user. To define a filter for an outcome level, click the Edit Filter icon in the appropriate column, specify the filter attributes, and click OK. The filter definition appears in the Filter column.

    • To audit only success or failures for all system components and applications, select Select Successes Only or Select Failures Only from the Select menu, respectively. To clear all selections, select None.

  7. If required, enter a comma-separated list of users in the Users to Always Audit text box.

    Specified users will always be audited, regardless of whether auditing is enabled or disabled, and at what level auditing is set.

  8. Click Apply.

    To revert all changes made during the current session, click Revert.

6.3.2 Managing Audit Data Collection and Storage

To manage the data collection and storage of audit information, you need to perform the following tasks:

  • Set up and manage an audit data repository.

    You can store records using one of two repository modes: file and database. It is recommended that you use the database repository mode. The Oracle Business Intelligence Publisher-based audit reports only work in the database repository mode.

  • Set up audit event collection.

For more information, see "Managing the Audit Data Store" in Securing Applications with Oracle Platform Security Services.

6.3.3 Viewing Audit Reports

For database repositories, data is exposed through pre-defined reports in Oracle Business Intelligence Publisher.

A number of predefined reports are available, such as: authentication and authorization history, OWSM policy enforcement and management, and so on. For details about generating and viewing audit reports using Oracle Business Intelligence Publisher, see "Using Audit Analysis and Reporting" in Securing Applications with Oracle Platform Security Services.

For file-based repositories, you can view the bus-stop files using a text editor and create your own custom queries.