Show TOC

Logging and TracingLocate this document in the navigation structure

Use

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 .

Features

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.

Activities

You can activate Integration Engine logging at various locations. The following variants are possible:

  • Use the configuration parameter LOGGING or LOGGING_SYNC (category RUNTIME) to activate logging of asynchronous or synchronous messages locally for the whole Integration Engine. This means that all service calls of all pipelines of this Integration Engine are logged.

    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.

  • Activate logging for individual pipeline services. This is useful if you just want to log the individual execution steps of a pipeline.

    If you activate logging for the entire Integration Engine at a later point, the settings at the pipeline service level have no effect.

  • Set logging in the message header. This means that this message is logged even if logging is deactivated explicitly in the configuration. The logging information is part of the message header:
    • <SAP:Logging>1</SAP:Logging>

      Activates logging explicitly.

    • <SAP:Logging>0</SAP:Logging>

      Deactivates logging explicitly.

  • Set logging in the troubleshooting settings. Logging is part of a defined conditioned action and takes place even if logging is deactivated explicitly in the configuration.

You can also activate Integration Engine tracing at various locations. The following variants are possible:

  • Use the configuration parameter TRACE_LEVEL (category RUNTIME) to activate tracing locally for the whole Integration Engine.

    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.

  • Set tracing in the message header. This means that this message is traced even if tracing is deactivated explicitly in the configuration. The runtime uses the highest of the values from the locally configured trace level and the trace level in the message.