MSMQ Adapter 6.0 | webMethods MSMQ Adapter Documentation | webMethods MSMQ Adapter Installation and User’s Guide Documentation | Logging and Exception Handling | MSMQ Adapter Message Logging
 
MSMQ Adapter Message Logging
Integration Server maintains several types of logs; however, MSMQ Adapter logs messages only to the audit, error, and server logs. Because MSMQ Adapter works in conjunction with the WmART package, the adapter's messages and exceptions typically appear within log messages for the WmART package, although that is not necessarily true for verbose-level messages.
The logging levels are different depending on which version of Integration Server you are running the adapter on, as shown in the following table.
Integration Server
Log
Description
Integration Server 6.5
Audit Log
You can monitor individual adapter services using the audit log as you would audit any service in Integration Server. The audit properties for an adapter service are available in each MSMQ Adapter service template on the Audit tab.
Error Log
MSMQ Adapter automatically posts critical-level and error-level log messages to the server's error log. These log messages will appear as adapter run-time messages.
Server Log
MSMQ Adapter posts messages to the Server log, depending on how the server log is configured. Critical-level through debug-level log messages appear as Adapter run-time log messages. Verbose Logging Levels log messages appear as MSMQ Adapter log messages. The Verbose Logging Levels range from Level 5 (V1-Verbose1) through Level 8 (V4-Versbose4).
Integration Server 7.1 and higher
Audit Log
You can monitor individual adapter services using the audit log as you would audit any service in Integration Server. The audit properties for an adapter service are available in each MSMQ Adapter service template on the Audit tab.
Error Log
MSMQ Adapter automatically posts fatal-level and error-level log messages to the server's error log. These log messages will appear as adapter run-time messages.
Server Log
MSMQ Adapter posts messages to the server log, depending on how the server log is configured. Fatal-level through debug-level log messages appear as adapter run-time log messages. Trace-level log messages appear as MSMQ Adapter log messages.
MSMQ Adapter log messages appear in the format ADA.0660.nnnn, where:
*ADA is the facility code that indicates that the message is from an adapter.
*0660 (or 660) is the MSMQ Adapter major code, which indicates that MSMQ Adapter generated the error.
*nnnn represents the error's minor code. For detailed descriptions of minor codes that MSMQ Adapter uses, see MSMQ Adapter Error Codes.
To monitor MSMQ Adapter log messages in Integration Server log, ensure that your server log's logging settings are configured to monitor the following facilities:
*0113 Adapter Runtime (Managed Object)
*0114 Adapter Runtime
*0115 Adapter Runtime (Listener)
*0116 Adapter Runtime (Notification)
*0117 Adapter Runtime (Adapter Service)
*0118 Adapter Runtime (Connection)
*0121 Adapter Runtime (SCC Transaction Manager)
*0126 Adapter Runtime (SCC Connection Manager)