This section contains information reated to the Audit trail component.

Audit Trail:

All business level applications or systems must emitt some form of logging information which is usually different from low level debugging information. This type of logging may be structured in levels such as message transport level and business document level.

The audit trail component is a audit trail logger for incomming and outgoing messages of any type, HTTP, SMTP, IIOP etc. The component is built using Microflow parts which means that message logging may be inserted anywhere between receiving incomming message and sending outgoing message(s).

Depending on where the Audit Trail component is inserted it may indicate transport level logging of raw HTTP messages or business level ebXML message logging. Of cource other types of logging architectures may be built.

Currently the first Microflow Action being implemented is using Berkely Database (BDB) as persistent storage. The reason for choosing BDB is that is got transactional logging, good fault tolerance, recovarbility, high performance, access to database through other programming languages such as C, C++, Java, Perl, TCL, Python.
All above properites are needed for generating a reliable AuditTrail.

See also:
Log component
XLIF Component