Chapter 5. Troubleshooting and error handling
This chapter describes how the i2 connector for i2. handles errors. The connector generates logging and tracing messages. The chapter contains the following sections:
v“Logging error messages” on page 27
v“Tracing messages” on page 30
v“Tips for troubleshooting” on page 31
Logging error messages
The connector logs an error message whenever it encounters an abnormal condition during processing, regardless of the trace level. When such an error occurs, the connector also prints a textual representation of the failed business object as it was received. It writes the text to the i2 Adapter log file, whose file name corresponds to the connector property LogFileName.
The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging, such as business object dumps or stack traces (for exceptions).
Error types: Error messages are of two types:
v
vFatal
Structure of error messages
All the error messages that the connector generates are stored in a message file named i2Adapter.txt. Each error message typically has a message ID, the error message, and an explanation section for a detailed description and tips to rectify the problem.
Message ID
Message
[EXPL]
The message IDs for the i2 connector range from 90000 to 92000, with 90000 to 91000 set aside for
Example: The following exemplifies the message structure, where nnnnn represents the message ID.
nnnnn
Not able to get a connection for this instance {1}. [EXPL]
Please ensure that the instance specified is up.
© Copyright IBM Corp. 2002, 2003 | 27 |