Messaging Audit Logging
Messaging audit logging provides data about messages sent by Integration Server and/or received and processed by a trigger on Integration Server. The messaging log contains detailed logging that helps with debugging issues in your messaging implementation.
You can use messaging log entries to do the following:
Track when
Integration Server prepares to send and then sends a message to the messaging provider.
Identify when or if published messages are written to the client side queue.
Determine whether a trigger successfully received a message from the messaging provider.
Track failures or successful completion of pre-processing and processing for a message.
Identify message acknowledgements sent to the messaging provider.
The messaging audit log contains log entries written for
Universal Messaging connection aliases and JMS connection aliases for which enhanced logging is configured and the messaging log is identified as the destination for the log entries. For each alias, you specify that the messaging audit logger writes log entries for messages sent and/or received by the alias. You can further refine the logging by indicating that logging occurs for messages sent to particular destinations or received by specific triggers. For information about configuring enhanced logging for messaging, see
the webMethods Integration Server Administrator’s Guide
Using Enhanced Logging for Messaging.