Remedy Adapter 7.1 | webMethods Remedy Adapter Documentation | webMethods Remedy Adapter Installation and User’s Documentation | Adapter Logging and Exception Handling | Adapter Message Logging
 
Adapter Message Logging
Integration Server maintains several types of logs; however, Remedy Adapter logs messages only to the audit, error, and server logs. Because Remedy Adapter works in conjunction with the WmART package, the adapter's messages and exceptions typically appear within log messages for the WmART package.
The following table lists the logging levels when you are running Remedy Adapter on Integration Server 7.1.1 or higher:
Integration Server
Log
Description
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 Integration Server. The audit properties for an adapter service are available in Remedy Adapter service template on the Audit tab.
Error Log
Remedy 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
Remedy 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 Remedy Adapter log messages.
The Remedy Adapter's log messages appear in the format ADA.0760.nnnnc, where:
*ADA is the facility code that indicates the message is from an adapter.
*0760 (or 760) is the Remedy Adapter major error code, which indicates that the message is generated by Remedy Adapter.
* nnnn represents the error's minor code. For detailed descriptions of the Remedy Adapter's minor codes, see Adapter Error Codes.
* c represents the critical level of the error. For Remedy Adapter this will be either V2-Verbose2 or V4-Verbose4. Beginning with Integration Server 7.1.1, all verbose logging levels appear as Trace logging level.
Important:Remedy Adapter logs all messages at Trace logging level.
To monitor the Remedy 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)