Troubleshooting the Hierarchical Dynamic Retrieve Module

This section describes problems that you may encounter when starting up or running the Hierarchical Dynamic Retrieve Module. It covers the following areas:

Error handling and logging

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.

Error types

Table 55 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 55. 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
  • Foreign key processing messages that contain such information as when the connector has found or has set a foreign key in a business object
  • Messages that provide information about business object processing. For example, these messages are delivered when the connector finds a match between business objects, finds a business object in an array of child business objects, or removes child business objects during a retrieval.

Level 4
  • Application-specific information messages, for example, messages showing the values returned by the functions that parse the business object's application-specific information properties
  • Messages that identify when the connector enters or exits a Java method, which helps trace the process flow of the connector
  • SQL statements. At this level and above, the connector prints out all SQL statements that it executes.
  • Changes to an attribute value during a retrieve. At this level and above, the connector prints out the name of the attribute and its new value.

Level 5
  • Messages that indicate connector initialization, for example, messages showing the value of each configuration property retrieved from the integration broker
  • Messages that comprise a business object dump
  • Messages that comprise a representation of a business object before the connector begins processing it (displaying its state as the connector receives it from the integration broker) and after the connector has completed its processing (displaying its state as the connector returns it to the integration broker)

Connector message file

Error messages that the connector generates are stored in a message file named Connector.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...
 

Fails to call RFC_READ_TABLE

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:

SQL SELECT fails

If a SELECT statement fails, check whether any simple attribute that is marked as key or is used as a foreign key contains a single quotation mark ('). If so, revise the business object's map to convert the single quotation mark (') to two single quotation marks ('').

Copyright IBM Corp. 1997, 2004