8 Audit Facilities

Oracle Utilities Cloud Services' inbuilt, configurable auditing facility provides the capability to register access to data from online and Web Services users. Auditing allows for the configurable tracking of changes to key data and allows authorized users to track changes on individual user. Use of this facility is optional and can be switched on or off at any time.

Note:

This facility does not audit batch processes for performance- related reasons.

Audit Configuration

Note:

This section covers the soft-table implementation of auditing. There is a specialist Audit algorithm support on business and maintenance objects to add information to log entries attached to these objects. Flush the online data cache to enable auditing on Oracle Utilities Cloud Services.

Audit configuration for Oracle Utilities Cloud Services is performed at the table level. Enable auditing on each table by navigating to the Administration menu then the Table menu option, and configuring the following field settings:

  • Audit Table: You need to configure a database table to store the audit information. By default, the CI_AUDIT table can be used to store audit information on the cloud.
  • Audit Program: You must configure a class or program that will record and process the audit information. By default, OUCS provides the following pre- built programs:
    • com.splwg.base.domain.common.audit.DefaultTableAuditor - The default Java-based class that audits changes on any fields configured to track auditing information.
    • com.splwg.base.domain.common.audit.ModifiedTableAuditor - An alternative to the DefaultTableAuditor class. However, this class does not audit inserts or deletions of empty string field data. For example, changes from null values to empty spaces or empty spaces to null values are not logged.
  • Audit Conditions: Switches that indicate the conditions for auditing the field. Activate at least one of these switches for auditing:
    • Audit Delete Switch: Audits delete operations against the field.
    • Audit Insert Switch: Audits insert operations against the field.
    • Audit Update Switch: Audit update operations against the field.

Audit Query by Table, Field, and Key

Once auditing is activated, changes are logged in the configured audit table by the selected audit class or program, and you can query the audit information by using tables, fields, and keys as search filters.

See Audit Query by Table/Field/Key in the online help provided with your service for information about querying audit data based on tables, fields, and keys.

Audit Query by User

Once auditing is activated, changes are logged in the configured audit table by the selected audit class or program, and you can query the audit information by using users as search filters.

See Audit Query by User in the online help provided with your service for information about querying audit data by user.

Read Audit

Oracle Utilities Cloud Services' inbuilt, configurable auditing facility can also be used to register data when accessed for auditing purposes. Read Audit (or read auditing) is different from standard auditing as it focuses on zones and in the current release, read audit is only available for the following zone types:

  • F1-DE
  • F1-DE-QUERY
  • F1-DE-SINGLE
  • F1-MAPDERV
  • F1-MAPEXPL

The zone configuration provides you with the ability to configure an Audit Service script that is called whenever the zone is displayed to determine the criteria and results to display.

The information audited can be determined by using programs and logged based on your requirements. Refer to the online help for descriptions and samples for Read Auditing configuration.

Note:

Services are shipped with sample generic Audit query codes that are specific to Oracle Utilities Cloud Service. You can reuse or alter these codes to fulfill your requirements. Refer to the Oracle Utilities Cloud Service online documentation for more information and samples.