This section describes error handling for the OneWorld adapter and the OneWorld ODA.
The adapter throws the following three types of exceptions when it executes a business function in OneWorld:
FatalException class conditions require manual intervention. The adapter catches fatal exception conditions and writes the text of the exception in the ReturnStatusDescriptor string. The returned status is FAIL.
In the case of a recoverable error, the adapter tries to perform the execution of the business function again. If the Recoverable exception is thrown again, the adapter writes the text of the exception in the ReturnStatusDescriptor string. The returned status is FAIL. If the second try is successful, the returned status is VALCHANGED.
In the case of a Reject exception, the return value determines if it is an error or a warning. The possible values are as follows:
For XMLList business object processing, the response XML document contains the error codes and error strings in case of errors. The adapter writes the error codes and error strings in the ReturnStatusDescriptor and returns a status of FAIL.
The OneWorld ODA throws an exception in the following scenarios:
ODK properties define the trace file name and trace level. The ODK wizard manages these two properties. The trace file can be found in the OneWorld folder of the Crossworlds/ODA folder. The default name of the file is OneWorldODAtrace.txt. The message file containing the error and trace messages has the following naming convention:
BIA_<ODAAgentName>Agent.txt
ODAAgentName is the value from the variable of the same name found in the start file for the ODA. If you change the value of the ODAAgentName variable, then you must also change the message file name. The error and trace message file is in the ODA messages folder.
See Tracing Exceptions and Messages in the Business Object Development Guide for more information on the trace file and the message file.