Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Adapter Logging and Exception Handling | Adapter Message Logging
 
Adapter Message Logging
Integration Server maintains several types of logs; however, Adapter for Enterprise Javabeans only logs messages to the Audit, Error and Server logs, as described in the table below:
Log
Description
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 Adapter for Enterprise Javabeans service template on the Audit tab.
Error Log
Adapter for Enterprise Javabeans automatically posts critical-level and error-level log messages to the server's Error log. These log messages will appear as Adapter Runtime messages.
Server Log
Adapter for Enterprise Javabeans posts messages to the Server log, depending on how the server log is configured. Critical-level through debug-level log messages appear as Adapter Runtime log messages. V1-Verbose1 or V4-Verbose4 log messages appear as Adapter for Enterprise Javabeans log messages.
Note that Adapter for Enterprise Javabeans does not log debug messages at the Debug level. Rather, it logs all of its debug output at the Verbose3 or Verbose4 level. Verbose3 is used for general debug logging and Verbose4 is used to log problems encountered while traversing entries on the JNDI server.
Adapter for Enterprise Javabeans log messages appear in the following format: ADA.0640.nnnnc, where:
*ADA is the facility code that indicates the message is from an adapter.
*0640 (or 640) is the major error code for Adapter for Enterprise Javabeans, which indicates that the message is generated by Adapter for Enterprise Javabeans.
*nnnn represents the error's minor code. For detailed descriptions of the minor codes for Adapter for Enterprise Javabeans, see Adapter for Enterprise Javabeans Error Messages.
*c represents the message's severity level (optional).
Because Adapter for Enterprise Javabeans works in conjunction with the WmART package, exceptions generated within the adapter frequently will appear within log messages for the WmART package.
To monitor Adapter for Enterprise Javabeans 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)