The JadeAuditAccess class framework encapsulates the behavior required to access information recorded in database transaction journals. The ability to analyze journals from a different JADE system is supported.
The JadeAuditAccess class provides:
The ability to operate out-of-band; that is, in a separate JADE system
Optional access to all of the embedded properties in created, updated, or deleted objects
Optional access to a JADE dynamic object containing changed property values for updated objects
Access to additional audited control information and events; for example, reorganization discontinuities and user sign-on and sign-off events
To use the functionality provided by the JadeAuditAccess class, set the
The
A description of a JADE system is created at the completion of a reorganization of the JADE system, and by user request. The description is written into the current directory of the audit journal and the event is audited with the description file identification timestamp. This timestamp is also saved in the database control file. When a new audit file is first used, the most‑recent description file timestamp is written in the audit file header record to identify the corresponding description file.
The JadeAuditAccess instance recognizes the description file timestamp in an audit file header record and in any subsequent record announcing the creation of a new description file, and it automatically loads (or reloads) the identified description file if it is available.
The JadeAuditAccess class provides methods that enable you to access the description of the class of the current journal record accessed and the values of properties of that class. You cannot access a JADE object of the user data from the journal record. Access to references yields a string containing the value of the object identifier (oid) or null (""). Access to an embedded blob or slob yields a Binary or String value containing its length and edition.
If no description is available for the class of the user data in the current journal record, the audited buffer, if requested, is available only as a Binary primitive type value.
For details about the constants, properties, and methods defined in the JadeAuditAccess class, see "JadeAuditAccess Class Constants", "JadeAuditAccess Properties", and "JadeAuditAccess Methods", in the following subsections.
For an example of a journal reader method that utilizes functionality of the JadeAuditAccess framework, see "JadeAuditAccess Class Method Example", later in this chapter.
(None)