Configuring transaction audit logging
The transaction audit log (TAIL) module provides services for the storage and retrieval of transaction log information.
- External/business transactions
- Associated internal transactions
- Key elements associated with the external transactions, such as the party ID
- Key elements associated with the internal transactions, such as the party ID
- Successful transactions, failed transactions, or both
The transaction audit logging feature has mainly database-driven configuration options. TAIL may be configured to log any persistent or inquiry-based business transactions, as well as some or all of their associated internal transactions. Both successful and failed transactions can be logged.
Transaction audit information can be logged to the database either synchronously, as part of the transaction, or asynchronously.
An InfoSphere® MDM transaction can consist of a number of internal transactions (or actions) that are executed as a part of the larger external transaction. For example, when the transaction audit feature logs an external transaction (also called a business transaction) it can be configured to also log all, some, or none of its internal transactions. When an audit transaction is retrieved, any of the internal transactions that have been logged are also retrieved.