You use logging to log the processing steps of XML messages in the Integration Engine . You use tracing to analyze these processing steps.
You configure both functions during configuration of the Integration Engine , or predefine them externally (in the message header). You can also set logging in the troubleshooting settings .
Logging logs the status of XML messages to be processed prior to the first processing step (inbound message) and after each pipeline service call. The entire message, including information regarding the processing status, is saved (persisted). Persisted XML messages can then be used for evaluation purposes in monitoring .
Tracing documents all or individual steps of a pipeline (depending on the trace level). Valid values for the trace level are 0 to 3. Level 0 means that no trace is activated; level 3 means that all processing steps are documented.
You can activate Integration Engine logging at various locations. The following variants are possible:
Use the configuration parameter LOGGING_PROPAGATION (category RUNTIME) to activate logging globally. This means that message processing is logged until it is complete on all involved Integration Engines.
If you activate logging for the entire Integration Engine at a later point, the settings at the pipeline service level have no effect.
<SAP:Logging>1</SAP:Logging>
Activates logging explicitly.
<SAP:Logging>0</SAP:Logging>
Deactivates logging explicitly.
You can also activate Integration Engine tracing at various locations. The following variants are possible:
Use the configuration parameter TRACE_LEVEL_PROPAGATION (category RUNTIME) to activate tracing globally. This means that message processing is traced until it is complete on all involved Integration Engines.