Tuxedo Adapter 6.0 | webMethods Tuxedo Adapter Documentation | webMethods Tuxedo Adapter Installation and User’s Documentation | Adapter Logging and Exception Handling | Adapter Message Logging
 
Adapter Message Logging
The Integration Server maintains several types of logs; however, the Tuxedo Adapter logs messages only to the audit, error, and server logs. Because the Tuxedo Adapter works in conjunction with the WmART package, the adapter's messages and exceptions typically appear within log messages for the WmART package.
The logging levels are different depending on which version of the 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 the Integration Server. The audit properties for an adapter service are available in the Tuxedo Adapter service template on the Audit tab.
Error Log
The Tuxedo Adapter automatically posts critical-level and error-level log messages to the error log. These log messages appear as adapter run-time messages.
Server Log
The Tuxedo 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. V1-Verbose1 or V4-Verbose4 log messages appear as Tuxedo Adapter log messages.
Integration Server 7.1.1 or higher
Audit Log
You can monitor individual adapter services using the audit log as you would audit any service in the Integration Server. The audit properties for an adapter service are available in the Tuxedo Adapter service template on the Audit tab.
Error Log
The Tuxedo Adapter automatically posts fatal-level and error-level log messages to the error log. These log messages appear as adapter run-time messages.
Server Log
The Tuxedo 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 Tuxedo Adapter log messages.
The Tuxedo Adapter's log messages appear in the format, ADA.740.nnnnc, where:
*ADA is the facility code that indicates the message is from an adapter.
*740 is the Tuxedo Adapter major error code, which indicates that the message is generated by the Tuxedo Adapter.
*nnnn represents the error's minor code. For detailed descriptions of the Tuxedo Adapter's minor codes, see Adapter Error Codes.
*c represents the message's severity level (optional).
To monitor the Tuxedo Adapter's log messages in the 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
*0117 Adapter Runtime (Adapter Service)
*0118 Adapter Runtime (Connection)
*0121 Adapter Runtime (SCC Transaction Manager)
*0126 Adapter Runtime (SCC Connection Manager)