Real Time Information Director User Documentation

RTID Security and Auditing
Hewlett-Packard Company 10 529618 - 002
• The date and time when the request was processed by the Director
• The name of the document type received or retrieved
The Director also records audit details: the inbound document received by the Director,
the outbound document sent by the Director, or both. In the case of an insertion or
update, the inbound document consists of data to be written to the data store, and the
outbound document is the Director’s response, including an XML request that the client
could later use to retrieve the data (a document of type DOCUMENTNAME_R) and any
applicable error messages. In the case of a query, the inbound document is the query
itself (an XML document of type DOCUMENTNAME_R), and the outbound document is
the query response. Other types of audit details are envisioned for the future. Audit
details are recorded in XML.
Auditing Data Model
The audit header is recorded in the SQL/MX data store, in a table called AuditHeader.
Details are stored in a table called AuditDetail.
Each AuditHeader record has a unique ID, called the Audit ID. This ID is the primary
key of the AuditHeader table and also appears in the related AuditDetail records. In fact,
whenever an audited record is inserted or updated, the Audit ID can be included as part of
the user’s database record. This allows an easy cross-reference from any record to
information about who last updated that record and when. (Compared to the common
practice of recording, in multiple tables, the date and time and the ID of the agent who
last updated a record, including the Audit ID saves space and provides access to more
information about the latest update.)
The AuditHeader also has an index allowing efficient lookup by date and
consumer, as illustrated in “Querying Audit Records,” below.
The AuditDetail table has a primary key consisting of the Audit ID, the type of detail—
Inbound or Outbound—and a sequence number. The document definition for an audited
document prescribes whether to audit inbound data, outbound data, or both; inbound and
outbound data are stored in different AuditDetail records. Sequence numbers allow the
Audit system to store XML documents larger than 4K in multiple records, each with its
own sequence number.
The Director supports partitioning of audit tables across disks or processors. If you want
partitioning, you must specify partitioning parameters
• In the KEYS table, as described in the document entitled RTID Metadata
Language
• In the properties file, as described in the document entitled RTID Deployment