The connector logs an error message when it encounters a condition that causes the retrieval to fail. When such an error occurs, the connector also prints a textual representation of the failed business object as it was received from the integration broker. It writes the text to the connector log file or the standard output stream, depending on its configuration. You can use the text to find the source of the error.
Table 48 describes the types of tracing messages that the Hierarchical Dynamic Retrieve Module outputs at each trace level. These messages are in addition to any tracing messages output by the WebSphere business integration system's architecture, such as the Java connector execution wrapper and the WebSphere MQSeries message interface.
Table 48. Connector tracing messages
Tracing level | Tracing messages |
---|---|
Level 0 | Message that
identifies the connector version.
No other tracing is done at this level. |
Level 1 | Function module entry and exit messages. These messages are written whenever the connector execution thread enters or exits from a function. The messages help to trace the process flow of the connector. |
Level 2 | Business object handler messages that contain information such as the arrays and child business objects that the connector encounters or retrieves during the processing of a business object |
Level 3 |
|
Level 4 |
|
Level 5 |
|
Error messages that the connector generates are stored in a message file named SAPConnector.txt. Each error has an error number followed by the error message. For example:
1210 SAP Hierarchical Dynamic Retrieve module unable to initialize. 1211 SAP Hierarchical Dynamic Retrieve module failed to locate...
The SAP RFC_READ_TABLE function doesn't handle character-based datatypes. The module may fail while retrieving data if the fields use the following datatypes: