The adapter components provide several levels of message logging and tracing.
The integration channel logs information, debugging, and error messages, which are printed to the Ariba Buyer Administrator console and to the log file for the Ariba Buyer node that is originating the messages. Table 11 lists the types of message and the default setting.
Table 11. Logging and tracing message levels for the integration channel
Message type | Description | Default |
---|---|---|
Information |
Logs key initialization and termination steps, message delivery and receipts events. | On |
Debug | Logs method calls and critical points within each call. | Off |
Error | Logs all error conditions within the channel or detected by it. | On |
The connector uses the adapter framework to log error, informational and trace messages. Error and informational messages are recorded in a log file, and the trace messages and trace level (0 to 5) are recorded in a trace file.
Table 12 describes the type of messages logged at each tracing level.
Table 12. Trace file tracing levels
Trace Level | Description |
---|---|
0 |
|
1 | Traces all entering and exiting messages for method |
2 | Traces the ODA's properties and their values |
3 | Traces the names of all business objects |
4 | Traces business object properties and the values received |
5 |
|
You configure both the log and trace files names, as well as the trace level, in Connector Configurator. Refer to Appendix C, "Connector Configurator" for details.
The ODA has no logging capability; error messages are sent directly to the user interface. Trace files and the trace level are configured in Business Object Designer. The process is described in "Configure the agent". The ODA trace levels are the same as the connector trace levels, shown in Table 12 above.
For more details on error handling and troubleshooting, refer to "Troubleshooting and error handling".