Audit Module Parts

Introduction    Implementing    Other Uses    Parts

New and changed objects in the AuditControl pattern.

Data

The AuditControl pattern contains four data entities:

• The Log entity stores the log entries for a Session.  A log record can be either System error, Application error or Information log.
• The FieldValue entity contains field-level log information.
• The LogType entity stores control information about the various types of log messages defined by the developer of the application.
• The EventType entity stores log control information about all the Event Handler functions defined in the application.

The relations between the entities can be seen in the Audit module structure diagram.

Abstract

The AuditControl pattern contains two abstract patterns for implementing basic Audit logging:

• The WebShell pattern adds a subroutine facilitating the creation of log records.  All Event Handler and Page Generator functions to implement Audit logging must inherit from this pattern.
• The EventDispatcher pattern implements logging of web requests (events) received by the Websydian application.  The Dispatcher function of the application should inherit from this pattern.  The Abstract.EventDispatcher pattern has the InitializeEventTypes function scoped under it.
• The EventDispatcherSystemError pattern will log a number of System Errors if detected.
• The EventHandler pattern logs that the Event Handler has been called.
• The PageGenerator pattern will log a number of System Errors if detected.

Services

Three different Service function are defined:

• The AuditControlMenu Windows function comprises a small application where Audit Log records can be viewed and dynamic control options can be set for the auditing process.
• The InitializeLogTypes function initializes the LogType table.
• The LogFieldValues meta-function creating values in the FieldValue table.