Logs

If an error is reported by an IBM® Integration Bus component, start your investigations into its causes by looking at the product and systems logs to which information is written during component operation.

The information that is recorded in a log typically consists of a time stamp, which indicates when the error occurred, and a brief description of the error, which can be expanded to provide more details of the error. In some situations, a general error is written and is followed by a group of more specific errors that provide details about the general error.

When an error occurs, check STDOUT, STDERR, and the local error log first. These logs record information about major activities within the system. All components of IBM Integration Bus provide diagnostic information whenever error or warning conditions affect integration node operation. These conditions include:

• Unsuccessful attempts to write a message to a WebSphere® MQ output queue
• Errors interacting with databases
• The inability to parse an input message

Additional logs that are specific to IBM Integration Bus are written to record runtime errors, internal errors that are produced by the operating system or your code, or errors related to the work that you are doing in a particular perspective, all of which you can view using the IBM Integration Toolkit.

Data is written to the following logs:

• Standard system logs
• Local error logs
• IBM Integration Bus logs
• WebSphere MQ logs
• Database logs